Deal risk radar
By Toolspoke
Every Monday, flags open Salesforce deals that have slipped, stalled or gone quiet in Gong, and posts them to Slack by owner.
Needs a Toolspoke account. You choose which project it installs into.
- Salesforce + Gong + Slack
- Required integrations
- Runs on a schedule
- Mondays at 8am by default
- Post one message
- What its last step does
- Nothing destructive
- 0 of 29 actions in its tools
On this page
The short version
- What it is
- A ready-made Toolspoke agent that finds the open Salesforce deals showing signs of risk and tells the team on Monday.
- What it reads
- Open opportunities with stage, amount, close date, last activity and owner, and Gong calls from the last 30 days.
- Where it posts
- One Slack channel, grouped by deal owner.
- What it flags
- Close dates passed or pushed, deals quiet for 21 days, stages unmoved for 30 days and large deals with no call.
- How often
- Mondays at 8am once you switch it on.
- What it never does
- Create or update a Salesforce record, or call a deal lost.
- What you need
- A Toolspoke account, Salesforce, Gong and a Slack workspace.
What Deal risk radar does
Deal risk radar is an AI agent that reads your open Salesforce opportunities and recent Gong calls every Monday and posts the deals that show signs of slipping to Slack, by owner, with the evidence.
Forecasts rarely go wrong in one week. A close date passes and nobody moves it. A large deal has had no call for a month. A stage has not changed since the quarter began. Each sign is visible in Salesforce or Gong, but nobody looks at all of them for every deal.
Pipeline reviews catch some of it, usually the deals the owner chose to talk about.
Deal risk radar checks every open deal against the same five signals, using Salesforce for dates and stages and Gong for whether anyone actually spoke to the customer. It ranks what it finds by the number of signals and the amount, and posts one list grouped by owner.
In practice, each Monday morning you get:
- Deals whose close date has passed or keeps being pushed
- Deals with no call or activity for 21 days
- Deals stuck in one stage for 30 days
- The evidence for each, so the owner can check it in a minute
How it works
Deal risk radar works in four steps each Monday: it reads open deals, reads the last 30 days of calls, checks each deal against five signals and posts a ranked list. All of it comes from the agent's written instructions, which you can read and edit after you install it.
Step 1: Read open deals
It queries every open opportunity with stage, amount, dates and owner.
Step 2: Read recent calls
It lists the last 30 days of calls and the accounts Gong matched them to.
Step 3: Check five signals
It flags dates passed or pushed, quiet deals, stuck stages and large deals with no call.
Step 4: Post by owner
It posts one ranked list, grouped by owner, with the evidence for each deal.
It reads Salesforce with one query
It uses soql_query to fetch every open opportunity with its stage, amount, close date, last activity date, push count and owner. If your org lacks a field, it checks with describe_object and drops it.
It checks whether anyone spoke to the customer
Logged activity can be an automated email. A Gong call means someone talked to the buyer. It reads calls with list_calls and get_call_details, asking Gong for the Salesforce account each call was matched to.
It uses your thresholds
Quiet means no call or activity in 21 days unless you choose another number. A deal over the amount you choose with no call in 30 days is flagged on its own. Any default it used is named in the post.
It flags and stops
It never moves a close date or changes a stage. The owner decides what the evidence means. The limits are under what it will never do.
What a Monday list looks like
A message from Deal risk radar is one Slack post, grouped by owner, with deals ranked by the number of signals and then by amount.
Calder
Channels
- # sales-pipeline
- # sales
- # revops
- # general
# sales-pipeline
Monday. 64 open deals read, 7 flagged. Quiet means 21 days, the default. Large means over 50,000, set at install.
Erin Walsh (2)
- Calder Health, 120,000, Proposal. Large and unspoken: last call 41 days ago. Stage unchanged for 38 days.
- Harbour Freight, 48,000, Negotiation. Close date 12 October, 11 days ago. Pushed 3 times.
Sam Okoro (1)
- Ostrava Foods, 22,000, Proposal. Quiet: no call or activity for 26 days.
The rest
4 more deals flagged on one signal each, listed at the end of the message. 57 deals showed no signal.
- Several signals
Deals that show two or more signs at once, or a large deal with no call. These are the ones to raise in the pipeline review.
- One signal
Deals that show one sign, with the evidence, so the owner can decide whether it matters.
- The rest
How many deals were read and how many showed no sign, so the list is never mistaken for the whole pipeline.
When nothing is at risk
If no deal is flagged, Deal risk radar posts one line saying so and how many deals it checked. On a Monday that is worth knowing.
A failed run is different. If Salesforce cannot be read, it posts that once. If Gong cannot be read, it flags from Salesforce alone and says the call checks were skipped.
Who uses Deal risk radar
Deal risk radar suits sales teams that run their pipeline in Salesforce and record calls with Gong. The examples use made-up names.
A sales manager before the pipeline review
Erin Walsh runs a Monday review. The list tells her which deals to ask about, not just the ones reps bring up.
A rep with too many deals
Sam Okoro carries forty opportunities. The list shows him which ones he has let go quiet.
A revenue operations lead watching the forecast
Nadia Haddad needs the forecast to be honest. Close dates that passed or keep moving are exactly what she checks.
A founder selling to large accounts
Felix Brandt has a few big deals. The large deal rule makes sure none of them goes a month without a call.
What Deal risk radar connects to
Deal risk radar connects to three tools: it reads Salesforce and Gong and posts to Slack. You connect each one yourself, and Toolspoke stores the connection encrypted, so the agent never sees the credential.
Salesforce
RequiredQuery records with SOQL, read and update any object through the REST API.
Authentication: Sign in with Salesforce
Gong
RequiredRead recorded calls, their transcripts and their participants from Gong's revenue intelligence platform.
Authentication: Access key and secret
Slack
RequiredSearch conversations and send messages to your workspace.
Authentication: Bot token
| Tool | What Deal risk radar does | What it cannot do |
|---|---|---|
| Salesforce | Reads open opportunities with soql_query, and checks fields with describe_object. | Delete a record: the connector has no delete action. It can create and update records, which this agent's instructions forbid. |
| Gong | Reads calls and their matched accounts (list_calls, search_calls, get_call_details). | Change anything in Gong: the connector has only read actions. |
| Slack | Posts one message with send_message, to a channel. | Delete messages: the connector has no delete action. |
The Salesforce connection can create and update records. Deal risk radar is told never to. That is an instruction, not a lock. To enforce it, switch create_record and update_record off in your project, or connect as a Salesforce user with read access to opportunities only. The access control guide explains how.
The Gong connector reads and nothing else, so the agent cannot change a call or a user there. The connector can return call transcripts, and this agent does not ask for them and is told never to quote a call.
What Deal risk radar will never do
Deal risk radar is told never to create or update a Salesforce record, and never to call a deal lost. It shows the evidence and the owner decides.
- Create or update a Salesforce record: no new close date, stage, amount, owner, task or note.
- Call a deal lost or recommend closing it.
- Quote what a customer said on a call, or post call transcripts.
- Post to anyone directly.
Why it does not change deals
A close date or stage in Salesforce feeds the forecast. If an agent moved it, the forecast would show the agent's guess, not the owner's. The agent reads and reports.
Why it gives evidence, not verdicts
A deal quiet for three weeks may be waiting on the buyer's legal team, which the owner knows and the data does not. So every flag shows the fact behind it.
What it keeps out of Slack
It says a call happened, when and who from the customer was on it. It does not quote what anyone said.
If something goes wrong
If Salesforce cannot be read, post that once and stop. If Gong cannot be read, flag from Salesforce alone and say the call checks were skipped. If Gong does not match a call to any account, leave it out rather than guessing which deal it belongs to.
These are written into Deal risk radar's instructions. They guide the agent, but they are not a permission. What it is allowed to touch is set by the access you grant.
Deal risk radar reads your pipeline and shows where it is weak. Every change to a deal stays with its owner.
When Deal risk radar runs
Deal risk radar runs on Mondays at 8am, but only after you switch its schedule on. It arrives switched off, so nothing runs and nothing is charged until you decide.
- Each run reads every open opportunity and the last 30 days of calls.
- When nothing is flagged, it posts one line.
- Any default it used is named in the post.
- If Salesforce cannot be read, it posts that once.
Each run uses model credit from your workspace balance, so it makes one run a week. The Salesforce, Gong and Slack calls themselves are free.
Your copy is an ordinary agent in your project. You can pause its schedule there, run it once on demand, change the day and time and edit its instructions. The agent's page lists recent runs and their cost.
How to set up Deal risk radar
To see deals at risk each Monday, add Deal risk radar to a Toolspoke project, connect Salesforce, Gong and Slack, set your thresholds and switch on the schedule. Nothing runs until the last step.
Step 1: Create a Toolspoke account or sign in
Choose Use this agent. If you are new, you will be asked to sign up first, and you come straight back to this agent afterwards.
Step 2: Add it to a project
Pick the project it should live in. You get your own editable copy, and you can see the three tools it brings before anything connects.
Step 3: Connect Salesforce
Sign in with a Salesforce user that can read opportunities and accounts. A read-only user is the safest choice.
Step 4: Connect Gong
Create an access key and secret in Gong's API settings and paste them. They are stored encrypted and the agent never sees them.
Step 5: Connect Slack
Choose Sign in with Slack and approve the Toolspoke app. For a private channel, add the Toolspoke bot to it first.
Step 6: Set the thresholds
Name the channel, the days that count as quiet and the amount above which a deal with no call is flagged. Leave them out to use 21 days and no amount rule.
Step 7: Switch on the schedule
The schedule arrives switched off. Run it once to see a list, then switch it on.
Make Deal risk radar fit your pipeline
Deal risk radar's instructions are plain English and you can edit them after you install it. Installing copies the agent, so your edits stay with your copy. Open the agent in Toolspoke and tell the builder what to change, and it rewrites the instructions.
Paste any sentence below into the builder chat, or say the same thing in your own words.
Treat a deal as quiet after 14 days without a call or activity.
Flag any deal over 50,000 that has had no call in 30 days.
Only check deals with a close date in the current quarter.
Leave out opportunities with the record type Renewal.
Run on Mondays at 7am.
This changes when the agent wakes up, so the builder edits its schedule, not the instructions.
None of these edits needs more access or touches the Never rules. They change what Deal risk radar is told, not what the connections allow.
How it compares to other options
Deal risk radar beats the alternatives when you want every open deal checked against the same signals, using calls as well as CRM dates. It loses to them when you want risk scored inside Salesforce itself.
| Compared on | Deal risk radar | Gong's deal boards | A Salesforce report | The weekly pipeline review |
|---|---|---|---|---|
| Checks every open deal | Yes | Yes | Yes | The ones raised |
| Uses calls, not only CRM dates | Yes | Yes | No | If the rep says |
| Shows the evidence for each flag | Yes | A score and signals | The fields | Yes |
| Arrives in Slack by owner | Yes | No, in Gong | By email subscription | No |
| Changes Salesforce records | Told not to | Can sync fields | No | Up to the owner |
| Rules you can read and change | Plain English | Gong's model | Report filters | Whatever is asked |
| Setup effort | Connect three accounts | Depends on your Gong plan | Build the report | An hour a week |
Gong's own deal boards are the better choice if your plan includes them and your team lives in Gong. They score risk with more signals than this agent reads.
A Salesforce report is better when you want the list to stay inside Salesforce and update live. It cannot see whether anyone spoke to the customer.
Frequently asked questions
Can Deal risk radar change a deal in Salesforce?
The Salesforce connection can create and update records, and the agent is told never to. To enforce it, switch create_record and update_record off in your project, or connect a read-only user (how access works).
Can it change anything in Gong?
No. The Gong connector has only read actions.
Does it read call transcripts?
No. It reads call details: who was on the call, when and which account Gong matched it to. It does not quote what anyone said.
What if a call is not matched to an account?
It leaves that call out rather than guessing which deal it belongs to.
What if I do not use Gong for every call?
It also uses Salesforce's last activity date, so a logged call or meeting counts too. Gong is what tells it a real conversation took place.
Can it message each owner directly?
Not by default. It posts one message to one channel, grouped by owner. Ask the builder if you want owners mentioned by name.
Is Deal risk radar free?
It has no price of its own, and every Toolspoke plan includes agents. Tool calls cost nothing, but each run draws on your usage balance. Pricing has the details.
Find the slipping deals before the forecast does
Connect Salesforce, Gong and Slack, set your thresholds and switch on the schedule. Your first list lands at 8am on Monday.