Automated Bombora Intent Surge Alerts
Every morning, WebRun opens Bombora, checks your target account list for any account showing a meaningful surge in intent signal on a topic relevant to what you sell, alerts the account team on Telegram with the topic and account, and texts the owning rep directly on Twilio, so a real spike in buying research gets a fast, prioritized follow up instead of getting lost in a weekly report.
How do I get alerted when a target account's buying intent surges?
Every morning, WebRun opens Bombora and checks your target account list for any account showing a meaningful surge in buying intent on a relevant topic. It alerts the account team on Telegram and texts the owning rep directly on Twilio, so a real spike in buying research gets a fast, prioritized follow up instead of getting lost in a weekly report.
- Intent surges reach the owning rep the same morning they appear
- Unowned but surging accounts still get flagged to the team
- Outreach gets prioritized by genuine signal strength, not a guess
Built for ABM teams · enterprise sales · demand generation · revenue operations
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
bombora.comin a real browser with your saved login - no setup, no API keys. -
1
Bombora - detect a surging intent signal on a target account
WebRun opens Bombora to detect a surging intent signal on a target account. - Open Bombora and review intent signal changes for your target account list
- Flag any account showing a meaningful surge on a relevant topic
- Note the topic and the strength of the surge for each
Done when Every target account with a surging intent signal has been identified with its topic.
-
2
Telegram - alert the account team
WebRun opens Telegram to alert the account team. - Post the surging account alert to the account team channel
- Show the account, topic, and surge strength
- Sort so the strongest surges appear first
Done when The account team has today's intent surge alert in Telegram.
-
3
Twilio - text the owning rep
WebRun opens Twilio to text the owning rep. - Text the owning rep for each surging account
- Name the account and the topic driving the surge
- Skip the text for surges below a meaningful strength
Done when The owning rep has been texted about any meaningful intent surge.
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 contact the account itself?
No. WebRun only alerts your team and the owning rep. Any outreach to the account is still started by a person.
How does it decide what counts as a meaningful surge?
It reads the intent signal strength Bombora already calculates for each account and topic, so a surge only gets flagged when it is genuinely notable, not every small fluctuation.
What if the account is not assigned to a rep yet?
It still gets posted to the Telegram alert for the account team, so an unowned but surging account is not missed just because no one is assigned to it yet.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.