Automated O-Valet Guest Follow Up Texts
The moment a ticketless SMS retrieval completes in O-Valet, WebRun drafts a short, on-brand thank-you text for that guest, queues it in Twilio without sending, and posts the draft to Slack for your team to review, edit if needed, and approve, so every follow-up still gets a human check before it reaches a guest's phone.
How do I follow up with guests after a ticketless valet pickup without texting them automatically?
The moment a ticketless SMS retrieval completes in O-Valet, WebRun drafts a short, on-brand thank-you text for that guest and posts it to Slack for your team to review. Nothing sends until a team member approves it, so every guest still gets a personal follow-up on schedule while a human stays in control of what actually reaches their phone.
- Every completed pickup gets a drafted guest text within minutes
- No text reaches a guest's phone without a human approving it first
- Opted out guests are skipped automatically, every time
Built for hotel valet operations · valet parking companies · guest experience teams · valet general managers
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
o-valet.comin a real browser with your saved login - no setup, no API keys. -
1
O-Valet - detect each completed ticketless retrieval
WebRun opens O-Valet to detect each completed ticketless retrieval. - Open O-Valet and check for ticketless SMS retrievals completed in the last check interval
- Capture the guest's phone number on file and the vehicle's checkout time
- Skip any guest who has opted out of follow-up texts
Done when Every newly completed ticketless retrieval has been captured, opt outs excluded.
-
2
Twilio - draft the guest follow-up text
WebRun opens Twilio to draft the guest follow-up text. - Draft a short, on-brand thank-you text for each guest, referencing their checkout time
- Queue the draft in Twilio without sending it
Done when A draft follow-up text exists for every completed retrieval, unsent.
-
3
Slack - queue the draft for team approval
WebRun opens Slack to queue the draft for team approval. - Post each drafted text to the review channel for your team to read
- Wait for a team member to approve, edit, or discard the draft before anything sends
- Never send a text to a guest without that approval
Done when Every drafted text has been posted for review, and only approved ones are sent.
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 my approval?
No. WebRun only drafts the follow-up text and queues it in Slack. Nothing sends to a guest's phone until a team member reviews and approves it.
Can I edit the draft before it sends?
Yes. The draft is posted in Slack for your team to read, edit, or discard, and only an approved version is sent.
What if a guest has opted out of texts?
It checks O-Valet for an opt out flag first and skips drafting anything for that guest entirely.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.