Automated Chaport Callback Request Booking
When a Chaport chat visitor asks to schedule a callback, WebRun captures their requested time and contact details, creates a Google Calendar hold for the assigned rep, and pings that rep on WhatsApp with the visitor's name, number, and reason for the call.
How do I make sure Chaport callback requests get booked immediately?
WebRun watches Chaport for visitors requesting a callback, books a Google Calendar hold at their requested time, and pings the assigned rep on WhatsApp with the visitor's name, number, and reason. This turns a callback request into a booked, actionable slot the moment it's asked for, instead of the rep discovering it later in the chat log.
- Callback requests get booked the moment they're asked for
- Reps get alerted on WhatsApp instead of checking the chat log for requests
- No callback request slips through during a busy shift
Built for small business support teams · sales teams · website live chat operators · solo business owners
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.chaport.comin a real browser with your saved login - no setup, no API keys. -
1
Chaport - find callback requests
chaport.com
WebRun opens Chaport to find callback requests. - Open Chaport and check conversations where a visitor requested a callback
- Capture the visitor's name, number, requested time, and reason
- Note which rep the conversation was assigned to
Done when Every new callback request is listed with its details.
-
2
Google Calendar - book the callback slot
calendar.google.com
WebRun opens Google Calendar to book the callback slot. - Open the assigned rep's Google Calendar
- Create a hold at the visitor's requested time
- Add the visitor's name, number, and reason to the event
Done when A calendar hold exists for every new callback request.
-
3
WhatsApp - alert the assigned rep
whatsapp.com
WebRun opens WhatsApp to alert the assigned rep. - Message the assigned rep with the visitor's details and booked time
- Include their name, number, and reason for the call
- This alert goes to your own rep, not to the visitor
Done when The assigned rep has been alerted for every new callback 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 call the visitor back itself?
No. It only books the calendar hold and alerts your rep. The actual call is always made by a person.
What if the requested time isn't available?
The hold is still created so the request isn't lost, and it's on the rep to reschedule with the visitor if there's a conflict.
Does the visitor's number go anywhere outside the company?
No. It's shared only with the assigned rep on WhatsApp and saved in the calendar event. WebRun never contacts the visitor directly.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.