Automated Tidio Demo Request Handoff
When a Tidio chatbot conversation ends with a visitor asking for a demo, WebRun captures their contact details and question, blocks a follow-up slot on the assigned sales rep's Google Calendar, and posts the lead's details to the sales Microsoft Teams channel.
How do I turn Tidio chatbot demo requests into booked sales follow-ups?
WebRun watches Tidio chatbot conversations for visitors requesting a demo, blocks a follow-up slot on the assigned sales rep's Google Calendar, and posts the lead's details to Microsoft Teams. This turns a chatbot conversation into a booked, actionable follow-up the moment it happens, instead of a lead sitting in a chat log until someone checks it.
- Demo requests get a booked follow-up slot the moment they happen
- Sales reps see the full context in Teams before they even reach out
- No chatbot lead sits unactioned in a chat log overnight
Built for ecommerce sales teams · small business sales · SaaS sales · website chatbot operators
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.tidio.comin a real browser with your saved login - no setup, no API keys. -
1
Tidio - find demo-request conversations
tidio.com
WebRun opens Tidio to find demo-request conversations. - Open Tidio and check conversations where the chatbot logged a demo request
- Capture the visitor's contact details, company, and question
- Note the time zone if the visitor mentioned one
Done when Every new demo request is listed with its contact details and context.
-
2
Google Calendar - block a follow-up slot
calendar.google.com
WebRun opens Google Calendar to block a follow-up slot. - Open the assigned sales rep's Google Calendar
- Block a follow-up call slot within the next business day
- Add the visitor's details to the event description
Done when A follow-up slot is booked on the calendar for every demo request.
-
3
Microsoft Teams - post the lead details
microsoft.com
WebRun opens Microsoft Teams to post the lead details. - Post the lead's details to the sales Microsoft Teams channel
- Include their company, question, and the booked follow-up time
- Leave the actual outreach to the assigned rep
Done when The sales channel has been notified for every new demo request.
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 WebRun message the visitor to confirm the demo?
No. It only books a calendar slot and alerts your sales rep. Confirming the time with the visitor is still done by the rep.
How does WebRun know a conversation is a demo request?
It reads the conversation content in Tidio for an explicit request for a demo, so only genuine requests get a calendar slot and a Teams alert.
What if the rep's calendar is already busy at that time?
The slot is still booked as a placeholder so the lead isn't lost. It's on the rep to move it if a conflict comes up.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.