Help Scout and this assistant

The same counter, on your own site and your own inbox

This page shows the assistant doing the counter job well: quoting from a published work list, booking a job in as a structured record instead of a paragraph, and reading a signed-in customer's own jobs back. On a real shop's site that record lands in your shared inbox.

1. Point the assistant at your site so your work list, prices and turnarounds become the answers it gives, as published content rather than a re-typed copy. 2. Expose the job book 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 booking tool an action card so a customer describes the bike once, in a form, rather than over six messages. 4. Wire the identity hand-off so a returning customer is recognised and their own jobs answer without them typing an address. 5. Register the page's actions over WebMCP so the assistant can bring the right job type into view while it quotes it.

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 work list, the plans and the jobs 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 job type or open the booking form.
Signing in as the demo customer is a real identity hand-off: the assistant receives a name and an email address it never asked for.

What is seeded rather than connected

There is no Help Scout mailbox behind this page. Nothing booked here becomes a Help Scout conversation, or a record in any other shared inbox.
Blackthorn Cycles is an invented shop. The workshops, prices, mechanics, customers and jobs are fixtures written for this demo.
Jobs booked here live in memory until this demo restarts. No bench space is held and nobody is called.

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