AI Receptionist
Every missed call is a booking that goes to a competitor who picked up.
$1,800setup, once
$800per month
Client Onboarding Pipeline
A signed contract sits in an inbox for a week before anyone does anything with it.
$2,500 setup, then $700 a month. Fixed price, US dollars. Live in 12 business days from a signed scope and the deposit.
Free audit, no accounts, we change nothing.
Or ask a person: aimarketing@gonzo.co.in +91 7390990227 WhatsApp
Client Onboarding Pipeline is one of Gonzo Digital's nine fixed-price systems. It costs $2,500 to set up and $700 a month, in US dollars, and goes live 12 business days after a signed scope and the deposit. It is for agencies, clinics and consultancies whose onboarding is presently a person's memory. Anything it sends on its own says it is from an AI.
What you get
- Signed-contract trigger starts the pipeline automatically
- Intake form sent, chased, and logged without a human remembering to
- Kickoff scheduling handled end to end
- A living onboarding checklist visible to the client, not just internally
Who it is for
Agencies, clinics and consultancies whose onboarding is presently a person's memory.
How it behaves
- Anything this system sends to a person on its own says it is an AI. There is no setting to turn that off.
- Fixed scope. The deliverables above are the scope, and the price does not move with the hours.
What this page does not show
Client results. This page describes what the system can do, not what it has done for someone. We will publish a result only when a real client has earned it and agreed to be named.
More detail
How it runs
- Starts the moment the contract is signed. The signature on the e-signature webhook is checked first, and a bad one creates nothing.
- Sends the intake form, chases it at one, three and five days, and logs every step. If it is still missing after that, you are told.
- Books the kickoff and keeps a checklist the client can see, republished on every change.
Where it connects
Each row says what exists today and what has to be true before it runs for you. "Tested in the sandbox" means tested against simulated services.
| Connection | Status today | What going live needs |
|---|---|---|
| E-signature provider (webhook) | Built, tested in the sandbox. Checks an HMAC signature over the raw request. | An e-signature account whose webhook hands us the raw body and the signing secret. We have not checked it against any provider's real scheme yet. |
| Intake form | Supplied by you. | A link to the form you already use. The sandbox defaults are placeholders, and a production setup refuses them. |
| Built, tested in the sandbox. | The intake form and each chase go out from your mailbox or domain: sending access over SMTP or Microsoft Graph, not set up on our side yet. | |
| WhatsApp Business API (official) | Built. Used only when a template id is supplied; email is the default. | A WhatsApp Business API account and an approved template, if you want WhatsApp at all. |
| Calendar | Built, tested in the sandbox. The calendar tools have never run live. | A calendar account (Google or Microsoft) connected through an integration router. |
| Your CRM | Writes the deal stage and an insert-only activity log in the sandbox. | A CRM adapter. Which CRMs mirror is checked per CRM before you sign. |
| A durable store for onboarding state | State is held in memory in the sandbox. | A database table for per-contract state. Nobody has built it yet. |
What this does not do
- It does not sign, negotiate or interpret a contract. It only reacts to the signature.
- It does not take payments. A reply that talks money, or a complaint, goes to a person.
- A repeated webhook creates nothing new, because onboarding is idempotent on the contract id. Webhooks carry no timestamp window, so replay protection rests on that id.
- Until the durable store exists, a restart means state is restored from a snapshot. We tell you that before go-live, not after.
- The checklist the client sees shows what is waiting on the client. It is not a project plan.
Doubts people raise about this one
What do I need to provide to get started?
It depends on the product, and the build names what it reads:
- AI Receptionist and Lead Response Engine: your knowledge base and business hours.
- Dormant List Revival: your customer list, with consent records for who may be contacted.
- E-commerce Support Assistant: your order data, your return policy and your product data.
- Connected Operations Layer: you connect each account through its own sign-in, and can revoke it.
The exact checklist for your system is agreed when scope is signed. The full list is not on file, so a person will give it to you.
What does it connect to?
What exists today, by product. Everything below has been built and tested against simulated services only; nothing has run live for a client.
- Lead Response Engine: the official WhatsApp Business API and email are built. The web form and web chat adapters are not built yet. Your CRM: it writes to our own CRM log, and whether it mirrors into yours is checked per CRM.
- AI Receptionist: web chat and a calendar adapter (Google or Microsoft) are built against a sandbox calendar. The phone line and voice gateway are not built. Confirmations go by email.
- Client Onboarding Pipeline: an e-signature webhook, an intake form, email, WhatsApp (when a template is supplied) and a calendar are built in the sandbox. The calendar tools have never run live, and the store for onboarding state is not built.
- Dormant List Revival: email and the official WhatsApp Business API are built in the sandbox. It needs a separate sending domain and a persisted consent store.
- AI Outreach & Lead Qualification Engine: email and official WhatsApp (opted-in contacts only) are built in the sandbox. Apollo enrichment has never run live.
- Quote-to-Invoice Automation: an intake form, email and Stripe payment links (money in only) are built. Stripe has never been run live. Your accounting package is not connected: invoices live in the system's own book.
- E-commerce Support Assistant: an adapter for your storefront is written per platform. Email, WhatsApp and web chat are built in the sandbox.
- Connected Operations Layer: four Microsoft 365 read tools and two Google Drive read tools are built. Gmail or Outlook, Google Calendar, HubSpot and WhatsApp go through an integration router that has never run live, and most write connectors are not built.
Your exact version of a tool, a self-hosted system or a niche CRM is not on file. A person will check it before you sign.
Who owns my data, my accounts and the workflow?
You own the workflow, the account, and the data from day one, not us. Credentials and documentation are handed to you in writing before we mark this live, not after. This is a gate in our own delivery process, not a promise.
That paragraph is in every proposal, for every product.
What we cannot answer yet: the contract wording on data return after you cancel, and the exact export format. A person will confirm both in writing before you sign.
What happens if you disappear?
You own the workflow, the account, and the data from day one, not us. Credentials and documentation are handed to you in writing before we mark this live, not after. This is a gate in our own delivery process, not a promise.
In the delivery pipeline, a deal cannot be marked live until the handover is logged.
What we have not yet written down: whether every part of every system keeps running without us. A person will tell you exactly what keeps running for the product you are looking at.
What if it gets something wrong?
It will sometimes get things wrong. It is not error-free, and we will not say it is.
What happens next: a failed action is retried, then set aside in a queue where you can see it, rather than dropped quietly. A question outside its data or policy is passed to a person instead of guessed at. Each action is written to a tamper-evident log, so you can see what it did and when.
Can you customize it for my business?
The products are fixed scope on purpose: the named deliverables, at the fixed price. The proposal builder accepts no scope overrides, because a scope that changes per client is a quote for custom work, and that is a different, slower and costlier business.
If you need something outside a product, tell us what it is. A person will say whether it can be done, and it will not be quoted from this box.
Related
- Weighing the alternatives: Build it yourself with Zapier, Make or n8n, or buy it done, covering building the same steps yourself in a workflow tool.
- Quote-to-Invoice Automation: the quote and invoice that come before the contract.
- Managed Automation & Infrastructure Retainer: keeps this running after we hand it over.
- Prices in rupees are on the India price page. Your own numbers go in the calculator.
Other systems
See what you get →
Quote-to-Invoice Automation
Quotes go out by hand, invoices go out late, and chasing payment is an afterthought.
$2,000setup, once
$600per month
AI Outreach & Lead Qualification Engine
You have a target list and no consistent way to work it. Leads sit unscored, outreach is inconsistent, and nobody can tell you which ones are actually worth a call.
$3,000setup, once
$1,200per month
Start with the free audit.
Send one web address. In about five business days you get a short written report. If a system fits, a fixed-price scope follows.
Free audit, no accounts, we change nothing.
Or ask a person: aimarketing@gonzo.co.in +91 7390990227 WhatsApp