AI receptionist setup. Calls with a next step.

Inbound receptionist setup starts at $2,000 USD for the starter scope shown on this page. We confirm access, scope, exclusions, timing and a written price before work begins. Third-party software and usage charges are separate; ongoing support is optional.

In 30 minutes, we discuss one task, your current tools and the result you need. We check whether the starter fits and what is needed for a written proposal. If paid discovery is needed, we explain its scope and price first. You do not need a prepared brief or a paid assessment to book the call.

We agree a baseline and acceptance checks with the person who owns the work. Test calls follow the agreed booking or CRM route; unavailable slots, unclear requests, and failed connections trigger the tested fallback. Where relevant, we also compare manual effort, correction work and operating costs. These checks guide the handoff; they are not a promise of revenue or savings.

The starter project is from $2,000 USD, one time, for one number, one qualification flow, and one supported calendar or CRM connection. For multiple locations, additional flows, or more integrations, the planning range is $4,000–$8,000. Your scope and fixed project price are agreed before work begins.

The voice platform subscription, telephone number, call usage, and any other third-party charges are separate from setup. We identify those costs for your expected call volume before you commit. Optional monitoring and bounded fixes start at $300–$1,000 per month according to the agreed coverage; new workflows and major changes are quoted separately.

Yes. We start by checking ready-made products against your call flow. If a native feature does the job, the work is configuration, connection, and testing. A custom build is only considered when a specific requirement justifies it.

We check the providers, forwarding options, supported integrations, permissions, and any number-transfer requirements before quoting. The starter includes one supported calendar or CRM connection. Keeping a number or connecting a particular system is not assumed until those checks are complete.

When the selected integration supports it, the workflow can book within the calendar, appointment types, availability, and eligibility rules you approve. If it cannot verify a slot or complete the booking, it captures a request for your team and tells the caller that confirmation is still needed.

The flow follows your escalation rules. A supported live transfer can be used when someone is available; otherwise, it records a callback request with the agreed contact details and routes it to an owner. We test unsuccessful transfers and unclear requests as part of setup.

After-hours handling can be part of the configured schedule when the platform supports it. We agree what callers can complete outside your staffed hours and what must wait for a person. Provider outages and failed connections have an agreed fallback rather than a promise that every call will be answered.

We confirm a delivery schedule after checking the platform, phone setup, integration, and approved script. Access delays, number transfers, and additional call flows affect timing. Activation follows test calls and your approval of the booking, escalation, and fallback behavior.

We configure the greeting, AI disclosure, recording settings, access, and retention around the policy your business approves and the platform's capabilities. You provide any legal review your use case requires. Recording is a decision made before activation, not an assumed requirement.