HubSpot and this assistant

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

This page shows the assistant doing what a lettings agency needs: answering from the published fee list, capturing an enquiry as a structured record rather than a paragraph of prose, and reading back a signed-in landlord's own enquiries. On a real site that record lands in your CRM.

1. Point the assistant at your website so it reads your fee list, your services and your policy pages as published content — no copying, no re-writing. 2. Expose the records you want it to read as a small MCP server: a handful of typed tools over the data you already have. 3. Give each write tool an action card, so the assistant opens a form with the fields filled in rather than interviewing the visitor line by line. 4. Wire the identity hand-off so a signed-in customer is recognised, and their own records answer without them typing an email address. 5. Register your page's own actions over WebMCP, and the assistant can act on the page the visitor is looking at.

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 catalogue, the packages and the enquiries are served by this demo's own MCP server — real tool calls, not pasted text.
The page's own actions are registered over WebMCP, so an agent can highlight a service or open the enquiry form.
Signing in as the demo customer is a real identity hand-off: the assistant is given a name and an email address it did not ask for.

What is seeded rather than connected

There is no HubSpot account behind this page. Nothing you submit is written to HubSpot, or to any other customer-records system.
Salterwick Property is an invented agency. The properties, fees, people and enquiries are fixtures written for this demo.
Submitted enquiries live in memory until this demo restarts. Nobody is paged, emailed or called.

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