Zendesk and this assistant

The same desk, on your own site and your own tickets

This page shows the assistant doing the unglamorous half of a passenger desk properly: answering from the published conditions of travel, opening a claim as a structured ticket with the right fields, and reading a signed-in passenger's own tickets back to them. On a real railway that ticket lands in your helpdesk.

1. Point the assistant at your site so your conditions of travel, refund policy and service pages become the answers it gives — as published content, not a re-written copy. 2. Expose your ticket data as a small MCP server: a lookup by reference and email, and a read that only ever answers for the signed-in person. 3. Give the claim tool an action card so the assistant opens a filled-in form instead of interviewing the passenger line by line. 4. Wire the identity hand-off so a signed-in passenger is recognised and their own tickets answer without them typing an address. 5. Register the page's own actions over WebMCP so the assistant can act on the page in front of them.

What runs on this page

The assistant on this page is a live Busymate AI assistant, grounded in this site's own published pages.
The service list, the passes and the tickets come from this demo's own MCP server — real tool calls, not pasted text.
The page registers its own actions over WebMCP, so an agent can highlight a service or open the claim form.
Signing in as the demo passenger is a real identity hand-off: the assistant receives a name and an email it never asked for.

What is seeded rather than connected

There is no Zendesk instance behind this page. No claim you open here becomes a Zendesk ticket, or a ticket anywhere else.
Braidwater Rail is an invented railway. The lines, stations, fares, people and tickets are fixtures written for this demo.
Tickets opened here live in memory until this demo restarts. No money moves and nobody is contacted.

The full guide: https://busymate.ai/docs/guides/connect-mcp-server.