Automated accesso Guest Complaint Triage
The moment a new complaint lands in Zendesk, WebRun pulls the guest's visit date, tickets, and purchase history from accesso for context, drafts a reply that acknowledges the specific issue, tags the ticket by severity, and pings your guest services lead on Telegram for anything marked severe. Every draft waits in Zendesk for a person to review and send.
How do I triage guest complaints and draft replies automatically?
WebRun triages each new Zendesk complaint using the guest's visit and purchase history from accesso, drafts a reply that references their specific issue, and pings your guest services lead on Telegram for anything tagged severe. Every reply waits as an unsent draft on the ticket, so a person always reviews and sends it before the guest hears back.
- Every complaint reply starts as a draft grounded in the guest's actual visit
- Severe complaints reach a guest services lead within minutes, not hours
- Nothing goes back to a guest without a person reviewing it first
Built for guest services teams · theme park customer support · water park guest relations · zoo and aquarium visitor services
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.accesso.comin a real browser with your saved login - no setup, no API keys. -
1
accesso - pull visit and purchase history
accesso.com
WebRun opens accesso to pull visit and purchase history. - Look up the guest's visit date, tickets, and purchase history in accesso
- Match any relevant incident, such as a downtime event, to the complaint
- Pull the guest's season pass or loyalty status if they have one
Done when The guest's visit context from accesso is attached to the complaint.
-
2
Zendesk - triage and draft the reply
zendesk.com
WebRun opens Zendesk to triage and draft the reply. - Tag the ticket by severity based on the complaint type and history
- Draft a reply that acknowledges the specific issue using the accesso context
- Save the draft on the ticket. Leave it unsent for a person to review
Done when The ticket is tagged and a drafted reply is waiting in Zendesk.
-
3
Telegram - escalate anything severe
telegram.org
WebRun opens Telegram to escalate anything severe. - Message your guest services lead for any ticket tagged severe
- Include the guest's history and why it was flagged severe
- Skip the ping entirely for routine, low severity complaints
Done when Severe complaints have reached a guest services lead directly.
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 it reply to the guest without anyone reading it first?
No. Every reply is saved as a draft on the Zendesk ticket. WebRun never sends a reply to a guest on its own, a person reviews and sends it.
How does it decide what counts as a severe complaint?
By the complaint type and the guest's history in accesso, for example a repeat issue or a complaint tied to a known downtime event. You can adjust which types trigger the Telegram escalation.
Where does the context in the drafted reply come from?
It pulls the guest's visit date, tickets, and purchase history straight from accesso, so the draft references their actual visit instead of reading like a generic template.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.