Automated Splash Event Registrant Handoff
Every hour, WebRun checks Splash for new registrants across active events, posts each one to the sales team in Slack with their company and role, and sends a Telegram ping for any registrant marked high priority so they get a fast follow-up.
How do I route new Splash event registrants to sales?
WebRun checks Splash every hour for new event registrants, posts each one to the sales team in Slack with their company, role, and event, and sends a Telegram ping for anyone marked high priority, so a promising registrant gets a fast follow-up instead of waiting for the event to wrap up.
- New registrants reach sales within the hour instead of after the event
- High-priority registrants get a same-hour Telegram ping
- Turnout is visible per event, not buried in one long list
Built for event marketing teams · field marketing managers · sales development reps · demand generation teams
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
www.splashthat.comin a real browser with your saved login - no setup, no API keys. -
1
Splash - check events for new registrants
splashthat.com
WebRun opens Splash to check events for new registrants. - Open Splash and review active event registration lists
- Capture new registrants since the last check
- Note the registrant's company, role, and event for each
Done when Every new registrant since the last check has been captured.
-
2
Slack - post registrants to the sales team
slack.com
WebRun opens Slack to post registrants to the sales team. - Post new registrants to the sales channel
- Include the company, role, and which event they registered for
- Group by event so the sales team can see turnout at a glance
Done when The sales team has every new registrant posted to Slack.
-
3
Telegram - ping about high-priority registrants
telegram.org
WebRun opens Telegram to ping about high-priority registrants. - Send a Telegram ping only for registrants marked high priority
- Include the registrant's name, company, and event
- Leave the actual outreach to the sales rep
Done when A ping has gone out for every high-priority registrant.
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
Will it contact a registrant directly?
No. WebRun only posts registrant details internally for the sales team. It never emails or messages a registrant on its own.
How does it decide who's high priority?
It reads whatever priority or lead score Splash shows for the registrant, so only those flagged high priority also get a Telegram ping.
What if two events run at the same time?
Registrants are grouped by event in the Slack post, so the sales team can see turnout for each event separately.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.