A new client in about a day of setup

Step 1: Before the kickoff

We gather what we need, and agree guardrails in writing: what the agent must refuse, the disclosure wording and the call-recording notice.

• Logo and colours
• The site or sites that will host the widget
• Hours and time zone
• Services and prices the agent may quote
• 5 to 10 real customer questions
• Who takes live chats and who owns bookings
• Which CRM you use, and whether you want phone

Step 2: Your own copy

We start a fresh repository for you. One config file holds your brand, colours, agent name and greeting, tone, allowed and blocked topics, booking rules and the sites allowed to show the widget. Shared code is not edited for a client.

Step 3: Infrastructure

A Postgres database, your keys, and a deployment on Vercel or Fly. You create the accounts, so billing and access are yours from day one. A five minute cron keeps the CRM in sync.

Step 4: Knowledge

We load your documents and import your service pages. Then we ask the agent your real questions in the test playground, write notes where an answer is weak, and test again.

Step 5: Agent and voice

Tone, topics, booking rules and disclosure are set. You pick a stock voice. We place one test call and read the transcript.

Step 6: CRM

You create a private app in HubSpot with the scopes we list, we connect it, map each lead field to a property your sales team uses, and choose the pipeline, stage and owners. A test lead goes through the widget and we check the contact, the meeting and the note. With another CRM, this step is built as part of the implementation.

Step 7: Calendar and email

Google Calendar through an OAuth client from your admin. Email through Resend with your verified domain, staff notification addresses and templates in your voice.

Step 8: On your site

We list your allowed origins and paste one script tag before the closing body tag. We check it on staging: the launcher appears, voice asks for the microphone, and a site that is not on the list shows nothing.

Step 9: MCP (optional)

We create a token or connector per person, read-only for most. If you have an order, booking or ticketing system with an MCP server, or we build a thin one in front of your API, we connect it with lookups first.

Step 10: Phone (optional)

Your Twilio account and number, then the Phone page checklist. US outbound calling has a registration lead time that is outside our control.

Step 11: Acceptance, with you

We check that the agent refuses what it should, a lead reaches your CRM, a booking waits for Confirm, a handover works, and a read-only token is refused a write. Then a keyboard pass and a screen reader check. Test data is deleted before launch.

Step 12: Handover and aftercare

We train staff on Live chats, Leads and the Knowledge gaps list. Two weeks after launch we review gaps, cost per lead and failed syncs together. Your keys live in your own password manager, not ours.