How long does an AI receptionist take to set up?

Where the time actually goes

Almost none of it is technical. In rough proportion:

• Call inventory — the largest share. Listening to real calls and working out what actually arrives. Most businesses are wrong about their own call mix, and this is where that gets corrected.
• Knowledge. Service area, services, pricing rules, hours, what you will not do. Often the first time a business has written this down in one place.
• Rules and triage. What counts as an emergency, what it must never promise, when it escalates. The highest-stakes part.
• Integrations. Calendar and dispatch. Quick with a modern API; this is the step that stretches a timeline when the system is older.
• Testing. Every call type, including the emergency paths, before it answers a real call.

What makes it run late

• Nobody can state the pricing rules. If price is case-by-case and lives in the owner's head, there is nothing to encode yet.
• A scheduling system with no usable API. The common one.
• No decision on what is an emergency. This needs an owner's judgement and cannot be delegated to us.
• Starting during your busy season. Nobody has time to review transcripts in the middle of a heat wave. Build before the season.

What you can do before you call us

1. Pull a month of call logs. Count missed, voicemail-without-message, and simultaneous calls.
2. Write down your four or five real call types.
3. Write down what counts as an emergency and who it goes to.
4. Write down your pricing rules, even roughly — ranges and call-out fees.
5. Find out what your scheduling system can actually expose.

Businesses that arrive with those five things go live considerably faster, and the exercise is worth doing regardless of what you buy.