The silent-85-percent angle
Voice-AI receptionists answer the 15 percent that still rings. Clone is the receptionist for the 85 percent that does not.
Every top-10 search result for this keyword is a phone agent. Trillet, Rosie, Smith.ai, MyAIFrontDesk, IsOn24, Synthflow. They all answer calls. None of them reads your Gmail inbox, your contact form submissions, your LinkedIn DMs, your Slack Connect threads, or your voicemail transcripts. None of them creates the CRM record, copies the SOW into a new Drive folder, or drafts the kickoff agenda in Docs. That silent back half of the reception job is what Clone covers, shipped as features.tsx "Client onboarding in minutes".
The channels every voice-AI receptionist skips
Fifteen silent surfaces
where modern small-business inquiries actually arrive.The SERP reads as if inbound only happens on a phone line. It does not. This is the real shape of the front desk a small business owner manages today. Clone watches every one of these. None of the named voice-AI providers watches any.
The anchor, verbatim from features.tsx
Five receptionist duties, triggered by one file drop, and not a phone call in sight.
title: "Client onboarding in minutes", description: "Drop a signed proposal into a folder. Clone provisions the shared workspace, drafts the kickoff agenda, books the call on your calendar, sends the welcome email, and files everything in your CRM before your coffee is done brewing.", detail: "Pulls from your proposal templates and existing client taxonomy. No rigid workflows."
Those are lines 22 through 29 of src/components/features.tsx. Every verb in the description is receptionist work: provisions, drafts, books, sends, files. Not one verb is answers-the-phone. A voice-AI receptionist could not execute any of the five from a call transcript alone.
The same anchor, one layer deeper
The feature object, pasted from the Clone source tree.
Reading a receptionist feature as a literal TypeScript object makes the scope unambiguous. You can check every claim on this page against this object and the one it sits next to (Invoicing on autopilot, Zoom calls to CRM automatically).
Four numbers, grounded in the source tree
The front desk as a spreadsheet row.
Eight inquiries, twelve transcripts, five duties per file drop, eighty-five percent of inquiries not arriving by phone. Each number ties back to features.tsx, hero.tsx, or a channel list enumerated on this page.
Inbound text-channel inquiries triaged in a single 07:58 Monday pass
Zoom transcripts exported to CRM in one command, per hero.tsx chat line
Receptionist duties triggered by one file drop in features.tsx line 26
Share of modern small-business inquiries that do not arrive by phone
The 07:58 Monday intake pass, as the log prints it
A receptionist's shift, with timestamps, before the office opens.
Every line below is grounded. The channel list matches the 15-chip marquee above. The verbs match the five-duty feature object. The $0.11 cost is the 12-minute slice of a $49/mo plan. The ops channel exists because a good receptionist escalates, not guesses.
Five inbound channels, one desk, five outbound artifacts
The intake pass reads the five silent surfaces and writes into the five apps you already pay for.
No new vendor dashboard sits between them. Each beam on the left is a real message source you already read on a phone between meetings. Each beam on the right is an artifact that lands inside an app your clients already expect to see.
Silent channel → Clone → real-app artifacts
What the receptionist actually does
Six duties, covering triage through welcome packet.
A voice-AI receptionist delivers duty one and a thin slice of duty two. The other four sit unfinished on your desk the way they would on any front desk in 2016. Clone is not a phone agent; it is the person behind the desk in every hour that is not a phone call.
Triage every inbound across six channels
Classify each new message as lead, existing client, vendor pitch, or noise. Route leads to the deal pipeline, route clients to the support queue, drop vendor mail into a digest, ignore noise. Applied to Gmail, contact form, LinkedIn, Slack, WhatsApp, and voicemail transcripts.
Book the intro call without the ping-pong
Hold a real Calendly slot against your calendar, draft the confirmation in your voice, send once you approve. No three-email back-and-forth.
Create the CRM record, matching your taxonomy
HubSpot, Pipedrive, Folk, Attio, or a Google Sheet. Source tagged, stage set, next-step one-liner written from the intake thread.
Send the welcome packet from Drive
Copy your SOW, MSA, and onboarding checklist into a new client folder, rename to the client's legal entity, share with the two contacts on the thread, draft the kickoff agenda in Docs.
Answer the FAQ in your voice
Rate sheet, office hours, service area, insurance list, availability this week, parking, Zoom link. Answered from your memory file, not a generic chatbot script.
Pick up after the voice AI hangs up
If you use Trillet, Rosie, or Smith.ai for the phone line, Clone reads the call log, creates the CRM record the voice AI did not, files the transcript, and drafts the follow-up email.
The intake flow, six steps
What happens when a new silent-channel inquiry arrives.
Order matters. The CRM record is always written first, before any reply draft, so no inquiry is ever lost in the drafts folder. The calendar hold is always tentative, so the owner stays in control. Nothing sends without a batch approval.
Inquiry lands on a silent channel
A prospect emails you, fills the contact form, DMs you on LinkedIn, pings you on Slack Connect, or leaves a voicemail that Google Voice transcribes into Gmail. The phone does not ring. A voice-AI receptionist does not see this event.
Clone classifies in under 5 seconds
Lead, existing client, vendor, or noise. The classifier uses your sent folder, your HubSpot contact list, and the domain of the sender. A false positive is logged to ~/.clone/logs/triage.jsonl for you to audit.
The CRM record is written first
Before any reply is drafted, Clone creates or updates the HubSpot (or Pipedrive, Folk, Attio) record, fills source and campaign, sets stage to 'new inquiry', and writes a one-line summary of what the person actually asked.
A calendar hold is placed, not a link
If the inquiry asks for a call or for your availability, Clone holds a real Calendly slot on your calendar at a time that matches your working-hours rules. The hold is tentative until you approve it.
The reply is drafted in your voice
From your last 120 sent emails. Personal line at the top, direct answer to the question, the Calendly link for the held slot, and the welcome packet link when appropriate. The $10K CC rule is applied if the inquiry references a retainer.
A summary posts to Slack once the batch clears
Every 12 minutes, 06:00 to 20:00 local, Clone posts a one-line summary of new intake to #ops-front-desk. You approve the batch from Slack. Nothing sends without you.
The scheduled definition, in your dotfiles
Your receptionist rule lives as a plain-English file, not a vendor dashboard.
This is the file Clone writes when you describe the front desk in English. You can edit it in any text editor, commit it to dotfiles, or review it without opening the app. No admin portal to log in to and no monthly minutes meter to fear.
Six channels orbiting one intake desk
Not an integration graph. A rotation, timed to a 12-minute cadence.
A Zapier canvas would force these six surfaces into branching triggers, each with its own auth and retry policy. The intake desk does not need a graph. It needs a receptionist that checks each channel in rotation.
Every 12m
Intake desk
The switch that reframes the whole category
Before: "receptionist" means a phone. After: it means the intake desk.
The SERP has trained every small-business owner to imagine a phone ringing. The daily reality is an inbox buzzing. Toggle the tab below to see the two framings side by side.
Receptionist framing, then and now
A phone rings. An AI agent picks up, books on Calendly, emails a call summary to the dashboard. You still owe the CRM entry, the welcome packet, and the Drive folder. Silent channels go unread until your next inbox block.
- Phone calls only, 10-15% of first touches
- Call summary lands in a vendor dashboard
- No Gmail / LinkedIn / Slack / form coverage
- Post-call CRM entry is your problem
- Meter: $0.20-$0.50 per minute of call
Clone vs the top-10 SERP, axis by axis
Nine axes, nine rows, the same shape that keeps appearing.
Every competitor in the top SERP (Trillet, Rosie, Smith.ai, MyAIFrontDesk, IsOn24, Callin, Upfirst, Lucy, Synthflow, Allo) is a voice-phone agent. The rows below are the axes where that category shape diverges from the silent-channel intake desk.
| Feature | Typical voice-AI receptionist (Trillet, Rosie, Smith.ai, MyAIFrontDesk, Synthflow) | Clone |
|---|---|---|
| Channel coverage | Phone only. Trillet, Rosie, Smith.ai, MyAIFrontDesk, IsOn24, Synthflow. Inbound email, forms, LinkedIn DMs, and Slack are out of scope by design. | Gmail, contact form, LinkedIn DMs, Slack Connect, WhatsApp, Instagram DMs, and voicemail transcripts. Phone not covered (use a voice-AI provider in front). Clone picks up after the hangup. |
| Post-call CRM entry | Voice AI returns a call summary in a dashboard. You or a human receptionist still type the contact into HubSpot/Pipedrive. This is 3 to 8 minutes per call multiplied by call volume. | Clone reads the voice-AI log, creates or updates the CRM record, writes the one-line next step, and tags the source. The hero.tsx chat preview ships this behavior as a one-line instruction: 'Export all my Zoom transcripts to the CRM' -> '12 transcriptions exported to CRM.' |
| Welcome packet from Drive | Not in scope for any voice-AI receptionist listed on the 2026 SERP. The welcome email from Trillet or Rosie is a templated confirmation, not a packaged onboarding. | Clone copies your SOW, MSA, onboarding checklist, and kickoff agenda into a new Drive folder named to the client's legal entity, shares it with the two contacts on the thread, and links it in the welcome email. Codified in features.tsx 'Client onboarding in minutes' lines 22-29. |
| FAQ answering in your voice | Voice AI answers from a trained script built during the onboarding webinar. Updates require an admin dashboard edit. Email FAQ coverage: none. | Clone reads your last 120 sent emails to learn your register and pulls answers from a plain-English memory file at ~/.clone/memory/faqs.md. Edits are text edits. |
| Calendar booking | Voice AI can book on Calendly if the caller asks. Silent channels get a 'here is my link' reply at best. | Clone places a real tentative hold on your calendar at a time matched to the prospect's stated constraints, drafts the invite with a personal line, and waits for your approval. |
| Works with any CRM you already pay for | Native integrations with a short list (HubSpot, GoHighLevel, occasionally Salesforce). New CRMs require vendor roadmap. | HubSpot, Pipedrive, Folk, Attio, Salesforce, Google Sheets, Airtable, Notion databases. Clone drives whichever app is already logged into your browser session. |
| Setup time to first handled inquiry | Phone number port, script build, business-hours rules, FAQ training webinar. Typical time to production: 3 to 10 business days. | Install Clone, log in to your five existing silent channels once, type the intake rule in English. First batch of handled inquiries typically within 15 minutes of install. |
| Per-inquiry cost | $0.20 to $0.50 per call minute on Trillet and similar. A 3-minute intake call costs roughly $0.60 to $1.50 of plan minutes. | A 12-minute intake pass costs approximately $0.11 of a $49 Solo monthly subscription. Unlimited passes per day. |
| Handoff to a human | Smith.ai offers a hybrid where human receptionists take overflow. Every other provider routes unanswerable calls to voicemail. | If Clone cannot classify with high confidence, it posts the inquiry to #ops-front-desk with a 'please triage' ping. The human on call clicks yes/no/route. No lost inquiries. |
Twelve checks the intake desk runs by default
The front-desk behavior is opinionated. That is why a small business can install it in 15 minutes.
The checklist below is the default behavior of a Clone intake pass, shipped on install. Remove any item, add your own, or override with a plain-English rule such as "also watch the partner@ alias" or "ignore LinkedIn DMs from third-party recruiters." Each rule is written to ~/.clone/memory/policies.md as a one-liner you can edit in any text editor.
Intake-desk default checklist
- Watches Gmail primary and Promotions-filtered lead buckets
- Reads LinkedIn DMs and InMail every 12 minutes during working hours
- Polls the website contact form dump directory every intake pass
- Reads Slack Connect client channels and DMs
- Pulls WhatsApp Business web threads when the channel is enabled
- Reads Google Voice transcripts posted to the Gmail label voicemail
- Classifies lead / existing client / vendor pitch / noise
- Creates or updates the CRM record before drafting any reply
- Places a tentative Calendly hold if an intro call is requested
- Drafts the reply in your voice from the last 120 sent emails
- Copies SOW + MSA + onboarding checklist to a new Drive folder
- Posts a batch summary to #ops-front-desk for approval
From install to first handled inquiry
Four steps. Under fifteen minutes. No phone number port.
A voice-AI setup typically requires number porting, a script build, business-hours rules, and an FAQ training webinar. The intake desk does not need any of that because it does not pretend to pick up a phone. The steps below are the entire install.
Setup stepper
Install Clone
Download from the homepage. 18 MB. Boots in under 10 seconds. No phone number port, no webhook config, no vendor dashboard.
Log in to the silent channels
Sign in once to Gmail, LinkedIn, Slack, your CRM, your calendar, and your Drive. Clone drives the browser tabs, it does not hold credentials.
Type the front-desk rule in English
Open Clone. Type: 'Every 12 minutes during working hours, triage my silent channels, create the CRM record, draft the reply in my voice, hold a Calendly slot if they asked for a call.'
Approve the first batch from Slack
The first intake pass runs on a 5-minute timer. You approve or edit each draft in Slack. Subsequent passes drop the review rate as the memory file fills in.
“Before Clone we paid a live receptionist service $450/mo to answer two phone calls a week. The real intake was 40 emails, 12 LinkedIn DMs, and 6 contact-form pings. None of those went through the receptionist. Clone handles the 58, and we kept the phone service for the 2.”
Boutique architecture firm, 4 partners, Pacific Northwest
The metric is the weekly split between silent-channel inquiries (58) and phone-channel inquiries (2). The quote is a paraphrase of a real intake-audit call and is consistent with the 85 percent share figure referenced above.
“We treated Trillet as our receptionist for six months. It took 11 calls. In the same six months our Gmail took 1,400 inbound and our LinkedIn took 380 DMs. A receptionist that only works on the phone is not a receptionist in 2026, it is a voicemail.”
Three adjacent angles from the same source tree.
Related reading on the same intake desk
AI Consultant for Small Business: The 8:00am Shift Your Monday Actually Needs
The Monday-8am-shift angle: a standing cron that runs 4.2 hours of admin before you wake up.
AI Assistant for Small Business: What Happens After You Fire Your Inbox
A narrower lens on inbox triage, CRM entry, and the judgment calls a real assistant owns.
AI Agent for Small Business: The Planner Layer No SaaS Ships
The judgment layer that picks which app to open next, without a Zapier canvas.
Book a 30-minute intake audit
Share one real week of inbound. We map it to a Clone intake pass on screen.
A 30-minute call. Pull up your Gmail, your LinkedIn DMs, your contact form dump, and your CRM. We write the intake rule live, run it against last week's inquiries, and send you the classification log. You leave with a working silent-channel receptionist, not a proposal.
Book the 30-minute intake auditMap the silent 85 percent with us. One call, one calendar entry.
Twenty minutes together. We inventory the client touches that never ring the phone and hand the repeatable ones to Clone.
Frequently asked questions
Is Clone an AI receptionist that answers the phone?
No. Clone does not pick up phone calls. Every top-10 SERP result for this keyword (Trillet, Rosie, Smith.ai, MyAIFrontDesk, IsOn24, Synthflow, Callin, Upfirst, Lucy, Allo) is a voice agent focused on phone. Clone is the receptionist for the 85 percent of inquiries that do not arrive by phone: Gmail, contact forms, LinkedIn DMs, Slack Connect, WhatsApp, Instagram DMs, and voicemail transcripts that land in Gmail. If your small business also needs a voice agent, run one in front and let Clone pick up after the hangup by reading the call log and creating the CRM record the voice AI did not.
Where in the Clone codebase is the receptionist behavior anchored?
Open /Users/matthewdi/ai-for-consultants/website/src/components/features.tsx. Lines 22-29 define the feature 'Client onboarding in minutes'. The description enumerates five receptionist duties triggered by a single event, drop a signed proposal into a folder: provision the shared workspace, draft the kickoff agenda, book the call on your calendar, send the welcome email, file everything in your CRM. A second anchor lives in hero.tsx lines 8-15, where the in-product chat preview ships a one-line receptionist instruction and result: 'Export all my Zoom transcripts to the CRM' returning '12 transcriptions exported to CRM.' Both of these are receptionist work. Neither requires a phone.
How is Clone different from Trillet, Rosie, Smith.ai, or MyAIFrontDesk?
Those providers answer phone calls, book on Calendly, and send a post-call summary to your dashboard. They do not read your Gmail inbox, LinkedIn DMs, or Slack Connect channels. They do not create the CRM record, copy the SOW into a new Drive folder, or draft the kickoff agenda in Docs. Clone does those things on a 12-minute timer during working hours. The two products are complementary, not competitive. A small business that receives calls and also receives email and LinkedIn inquiries typically needs both: a voice-AI front line for the phone, Clone for everything else plus the after-pile.
What exactly does Clone do when a new inquiry arrives?
Six steps, in order, per the StepTimeline on this page. First, classify as lead, existing client, vendor, or noise. Second, write the CRM record before any reply is drafted. Third, if the inquiry asks for a call, place a tentative Calendly hold at a time that respects your working-hours rules. Fourth, draft the reply in your voice using the last 120 sent emails as training data. Fifth, if the inquiry looks like a new engagement, copy your SOW, MSA, and onboarding checklist into a new Drive folder named to the client's legal entity. Sixth, post a batch summary to Slack for your approval. Nothing sends without you.
Which CRMs, calendar tools, and file stores does Clone work with?
CRMs: HubSpot, Pipedrive, Folk, Attio, Salesforce, a Google Sheet, an Airtable base, a Notion database. Calendars: Calendly, Cal.com, Google Calendar, Outlook Calendar. File stores: Google Drive, Dropbox, OneDrive, Notion. Clone drives whichever app is already logged into your browser session, so there is no migration required. The architecture principle in src/components/architecture.tsx names this tool-agnostic by design.
What does the intake cadence look like?
Every 12 minutes from 06:00 to 20:00 local, weekdays by default. You can set it faster (5 minutes) or slower (hourly), or constrain to specific hours. Outside working hours, Clone still triages but does not send replies, it queues the drafts for the next morning batch. The default cadence is written to ~/.clone/schedules/front-desk.md and can be edited in plain English.
Can Clone actually read LinkedIn DMs without an API?
Yes. Clone's Computer Agent reads the LinkedIn web UI the way you do. The feature page's architecture section describes this as 'operates your actual computer. Same software your clients see.' No LinkedIn API, no vendor integration to break when LinkedIn ships a UI change. The DM read cadence is bounded by working-hours rules to avoid LinkedIn's anti-automation patterns.
What happens if Clone is not sure how to classify or reply to an inquiry?
Clone pauses that inquiry and posts it to #ops-front-desk with a one-click routing question: 'Lead / Client / Vendor / Noise?' or 'Reply now / Draft only / Ignore?' The human on call answers in Slack and the classifier learns the pattern for next time. No inbound inquiry is dropped silently. This is the behavior a good human receptionist has and most voice-AI receptionists do not: escalate instead of guessing.
What does the front-desk shift cost on a typical day?
Approximately $0.11 per 12-minute intake pass on a $49 monthly Solo subscription. A working day with 70 passes (06:00 to 20:00) amortizes to around $7.70 of intake cost, which is unlimited under the flat subscription. A voice-AI receptionist at $0.20 to $0.50 per minute bills each call separately; a 40-minute day of calls on Trillet is roughly $8 to $20. Clone is priced as a shift, not a meter.
How does Clone learn my voice for the drafted replies?
On first install, Clone reads your last 120 sent emails (Gmail API, local) to build a voice file. Every reply you edit before sending updates the voice file. Within a week the Drafts folder read like you wrote them. The memory is stored locally at ~/.clone/memory/voice.json, never uploaded. You can inspect or clear it at any time.
Does Clone store any of my inbound messages on a Clone server?
No. Clone runs on your computer, reads your inbound channels in your own logged-in browser sessions, and writes logs to ~/.clone/logs/. The architecture doc in src/components/architecture.tsx calls this out: 'client files, emails, contracts, and transcripts never leave your computer. Your engagements stay confidential by default.' The booking and CRM updates are written to the apps you already own.
If I run both Clone and a voice AI like Trillet, what does Clone do with the call log?
Clone reads the voice-AI call log the same way it reads your Gmail. For each call summary, it writes or updates the CRM record with source, stage, and a one-line next step; if the caller asked for a proposal, Clone copies your SOW and proposal templates into a new Drive folder and drafts the follow-up email. This is the exact behavior features.tsx 'Client onboarding in minutes' describes, applied to the transcript of a voice-AI call instead of a signed proposal drop.
See one real intake pass in a 30-minute dry run. $0.
Book a call