Automated Salesloft Cadence Setup Checks
When a new batch of prospects is added to a Salesloft cadence, WebRun opens Salesloft, checks each record for a valid email, phone number, and assigned owner, posts the full setup status to Telegram, and texts the rep on Twilio the moment a blocking gap would stop the cadence from running cleanly.
How do I catch Salesloft cadence setup gaps before they go out?
When a new batch of prospects lands in a Salesloft cadence, WebRun checks each record for a valid email, phone number, and assigned owner before the first touch goes out. It posts the full setup status to Telegram and texts the rep on Twilio only when a blocking gap needs fixing, so a bad address or a missing owner never quietly breaks a cadence.
- Bad data gets caught before the first touch, not after a bounce
- Reps get texted only when something actually needs fixing
- Every new batch has a documented setup status
Built for SDR teams · sales development · revenue operations · inside sales managers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.salesloft.comin a real browser with your saved login - no setup, no API keys. -
1
Salesloft - check new prospects added to a cadence
WebRun opens Salesloft to check new prospects added to a cadence. - Open Salesloft and review the prospects just added to a cadence
- Check each record for a valid email, phone number, and assigned owner
- Flag any prospect missing a field the cadence needs to run
Done when Every newly added prospect has a pass or fail setup status.
-
2
Telegram - report the setup status
WebRun opens Telegram to report the setup status. - Post the setup status for the new batch to the team channel
- List how many prospects are clean and how many are missing a field
- Name the missing field for each flagged prospect
Done when The team has the batch's setup status in Telegram before the cadence starts.
-
3
Twilio - text the rep about a blocking gap
WebRun opens Twilio to text the rep about a blocking gap. - Text the cadence owner only when a blocking gap is found
- Name the prospect and the missing field in the text
- Skip the text entirely when the whole batch is clean
Done when The rep has been texted about any blocking gap ahead of the first send.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does it fix the missing data itself?
No. WebRun only checks and reports. It flags which prospect and which field is missing so a rep can fix it before the cadence sends the first touch.
Why text on Twilio instead of just posting to Telegram?
A blocking gap can stop an entire cadence from running, so it is worth a direct text. Routine, clean batches only get the Telegram summary, not a text.
What counts as a blocking gap?
A missing email or phone number that the cadence's first step needs, or a prospect with no assigned owner. Anything less critical is still noted in the Telegram report.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.