Confirm reservations and cut no-shows
Every night, WebRun opens OpenTable, reads the next day's bookings, drafts a personalised confirmation SMS for each guest via Twilio, queues the messages for your approval, and posts a no-response watchlist to Slack so you can follow up before service.
- No credit card
- Under $0.01 per run
- Cancel anytime
How can I automatically confirm reservations and reduce no-shows?
Every night, WebRun opens OpenTable, reads the next day's bookings, drafts a personalised confirmation SMS for each guest via Twilio, queues the messages for your approval, and posts a no-response watchlist to Slack - so you can follow up before service and cut no-shows without chasing guests manually.
- Every guest contacted the night before their reservation, not just high-value bookings
- No-response watchlist in Slack lets staff follow up on at-risk covers before service
- Fewer empty tables caused by guests who forgot to cancel
Built for restaurant managers · hospitality operators · hotel and venue teams · front-of-house coordinators
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
restaurant.opentable.comin a real browser with your saved login - no setup, no API keys. -
1
OpenTable - read tomorrow's reservations
- Open OpenTable and filter the reservation list to tomorrow's date
- Collect guest name, phone number, party size, and booking time for each cover
- Skip any guest who was already confirmed today
Done when All unconfirmed reservations for tomorrow are collected with contact details.
-
2
Twilio - draft confirmation SMS per guest
twilio.com How to Automate Twilio
WebRun opens Twilio to draft confirmation SMS per guest. - Draft a friendly confirmation SMS for each guest, naming their time and party size
- Queue every message as a draft - do not send until you approve the batch
- Log the message body and recipient in the run report
Done when Confirmation SMSes are drafted and awaiting your approval before sending.
-
3
Slack - flag non-responders for follow-up
slack.com How to Automate Slack
WebRun opens Slack to flag non-responders for follow-up. - Post the draft-SMS list to your ops channel so you can review and release them
- After the next run, flag any guest who still hasn't replied so staff can call them
Done when Your team has a clear list of drafts to approve and guests to chase.
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 text guests without me seeing the messages first?
No. Every SMS is drafted and held until you approve the batch in Slack - nothing is sent on its own.
What does the confirmation text say?
A short, warm message with the guest's name, time, and party size. Give WebRun your brand voice or a sample and it will match your tone.
What if a guest has already confirmed?
WebRun checks each guest's confirmation status in OpenTable before drafting, so confirmed covers are skipped automatically.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.