She answers.
Inbound email, texts, calls, chats, and DMs reach the same agent with the same memory of that person.
The onboarding journey
From purchase to armed, in one guided pass.
Every step saves as you go, so you can stop and come back. The last step is the only one that lets her talk to a real person.
- 1
Purchase.
You buy a workspace and get a one-time setup link. The workspace is provisioned in setup mode with the kill switch already on.
What this protects: Nothing can send during setup, even by accident.
- 2
Business details.
Name, timezone, and what the agent should be called when she introduces herself.
What this protects: Quiet hours and dates are computed against real timezones from the start.
- 3
Your AI key.
Your choice of Anthropic, OpenAI or Moonshot, using your own account and your own key. We check it live against the provider, then list the models your key can actually reach so you cannot pin one you do not have access to. The key is encrypted in a vault and never shown again.
What this protects: Your model spend, your rate limits, and your data path stay under your account.
- 4
Agent persona.
Tone, register, message length. Start from our default and edit it into your voice.
What this protects: Personality is yours to change without touching the methodology.
- 5
The interview.
Rachel asks about the business one question at a time and writes your business context and operations from your answers. Resumable, and you review and edit everything before it applies.
What this protects: She never fills a gap by inventing an answer. Gaps are marked.
- 6
Pricing and how she closes.
Packages, add-ons, and the discount floor, which is the lowest number your business will ever accept. Then pick quote and close, quote with approval, or meeting only.
What this protects: The floor moves into the database here, where the agent cannot be talked past it.
- 7
Authority.
May she quote, may she discount, may she close, and by how much. Everything starts closed.
What this protects: A misconfigured workspace fails by escalating too much, not by conceding too much.
- 8
Connections.
Mailbox, Twilio and a number, calendar, chat, social, CRM. All of it is skippable, and you can come back later.
What this protects: You are never blocked from finishing setup by an integration you are not ready for.
- 9
Armed but paused.
Setup ends with everything configured and one switch left unflipped. Nothing goes out until you flip it.
What this protects: Going live is a decision somebody makes on purpose.
After you arm her
What happens next.
She escalates when she should.
Ungrounded claims, refunds, contract terms, legal questions, and unconfirmed dates go to your Handoffs inbox with the draft withheld.
You keep the receipts.
Every reply carries its trace and its cost. The audit log records who changed what. Data export gives you every row you own.
Text messages have one wait in them, and it is deliberate.
Connect your Twilio account, buy a number in the portal, and file your 10DLC registration. The opt-in question on that form is filled in from the consent you actually have on record rather than from a template. Nothing texts until the registration is approved, on purpose: US carriers do not bounce unregistered traffic, they drop it, and the provider still reports it as accepted. A queue that visibly stopped is recoverable. A month of silently discarded messages is not.
See her handle your hardest objection
Book a walkthrough. We will set her up against your pricing, your floor, and your objections, and you can try to talk her into a bad deal.