You're great at the job. The phone still rings while you're on it.

Ordinary voicemail leaves the caller to tell the story. Our planned Smart Voicemail workflow asks a few agreed questions so the owner can review a structured request: who called, what they need, where the project is and when they want help. It is an intake assistant, not an autonomous salesperson.

That is the goal. Where your carrier supports it, conditional forwarding can route unanswered or busy calls to the assistant while you keep answering normally. After-hours routing depends on your phone system. We verify support, fees, fallback and how to turn forwarding off before a trial. Number porting is not required for our proposed trial workflow.

Only the fields agreed for your workflow, typically a name, callback contact, requested project, general location and urgency or preferred timing. It can ask approved follow-up questions, but details can be missing or wrong. Your team verifies the scope, address and availability before quoting or scheduling.

Yes. The goal is a useful list to review, filter and mark for follow-up or pass, not a system that chooses your customers. The preview above uses fictional notes. You decide whether a project fits your service area, capacity and work preferences, then handle the follow-up.

That is the intended pilot workflow, not a connection already running on this page. We agree where summaries go, who can access them and how long they are kept, then configure and test delivery and storage. CRM, calendar, email and other custom integrations are separate scope. The sample filters here do not save anything.

It identifies itself as an automated assistant. The default is a distinct voice, not a clone of you or us. A custom cloned voice is a separately quoted add-on after the trial and requires the voice owner’s consent. It still must disclose that it is automated.

We agree on disclosure, consent, access and retention before activation. Recording or transcription must follow the requirements applicable to your calls; a generic greeting is not a legal-compliance guarantee. We scope the workflow to avoid collecting unnecessary sensitive information. Ask us to walk through the proposed data handling before starting.

AI can misunderstand, miss a call or give a wrong answer. We limit it to approved information, test fallback routing and require human confirmation of prices and appointments. This is not an emergency service or a safety-monitoring system. Immediate danger belongs with 911 or the appropriate local emergency service, not this assistant.

Not as part of this standard intake offer. A request is not a confirmed appointment. SMS, outbound campaigns and custom booking integrations are excluded and would need separate scoping, permissions and testing. There is no promise of instant texts, automatic sales or guaranteed response times.

Seven days or 50 connected AI-call minutes, whichever comes first, once the pilot scope and routing are ready. There is no setup or subscription charge during the trial. If you continue: $599 / month, including 500 connected AI-call minutes per month, plus $1,000 one-time setup. Connected minutes include conversation and silence while the AI is on the call. Additional usage is $0.50 per minute only within a budget you approve. At the agreed limit, new calls follow your agreed fallback unless you approve more usage. Usage measurement and fallback controls must be tested before activation. New-customer pricing in USD. Existing purchased plans and their agreed terms stay unchanged. Setup, support scope, usage, and fallback are agreed in writing before activation.

We are preparing the new real-time experience with Chimpipi as the first pilot. Customer rollout follows real-call testing; this page has an illustration, not a live calling demo. Timing depends on your provider, approved business information, routing, data handling and fallback tests. We agree a realistic start date rather than promise same-day activation.