Price the service, not just the minute: AI receptionist agency pricing

Define the receptionist service before costing it

Call intake, appointment requests and confirmed booking require different work. A service that collects a callback request can end when the correct record reaches the staff queue. A service that books appointments has to inspect availability, handle conflicts and confirm only an accepted booking.

Write the completion condition in the proposal. Include the business locations, languages, supported call reasons, destination systems and human handoff. Decide which information staff must supply and approve before launch.

If you are still choosing the first offer, read the first-client guide. Pricing a broad promise to automate reception leaves too many variables unresolved.

For setup, estimate discovery, configuration, integration, test calls, failure cases and staff handover. For the recurring fee, estimate monitoring, investigation, reporting, agreed information updates and client support. Record assumptions beside the estimate so you can compare them with actual delivery later.

Reconstruct the billable usage

A caller's conversation duration may differ from the units on provider invoices. Check the provider and route you intend to use, including transfers and any separately billed services.

For example, Twilio's call-forwarding billing guidance describes an inbound leg and an outbound leg, billed separately. That claim applies to the Twilio forwarding arrangement described, not every voice platform's bundled pricing.

Inspect sample invoices or usage exports before treating one call minute as one billable minute. Add phone numbers, model or speech services, recording or storage charges, and integration fees where your chosen stack bills them separately. Avoid double-counting components that a provider includes in a bundled charge.

The business may only be able to estimate expected volume. In that case, price a clear allowance and a rule for exceeding it. Define the measured unit and the source of the usage report. The client should be able to reconcile the report with the invoice.

A worked monthly quote

Consider a hypothetical monthly quote based on expected AI receptionist call minutes. The calls cost less than the fee, so the quote appears profitable. During the month, the owner changes opening hours, staff report missing callback details, and the agency spends a day investigating a transfer problem.

The call bill still looks fine. The delivery cost has changed.

The following arithmetic is hypothetical. It is neither Vora pricing nor a recommended market rate. It assumes one receptionist workflow, 1,000 billable units per month, an internal blended usage estimate of $0.12 per unit, and four hours of delivery work valued at $50 an hour.

The difference is $800. Dividing it by the $1,200 fee gives 66.7% after the listed delivery costs. This is an illustrative contribution calculation before other overhead, tax and acquisition costs. It is not a net profit figure or an agency margin benchmark.

If the same month takes eight support hours, listed delivery cost becomes $600 and the contribution becomes $600, or 50%. The usage estimate has not changed. Tracking only the phone bill would miss the difference.

Use an internal hourly cost even when you do the work yourself. The time still occupies capacity you could use for another client. Keep that rate consistent while comparing quotes; otherwise, a change in costing method can look like an improvement in delivery.

Quote setup separately

Consider a hypothetical setup fee of $900. If the work takes ten hours at the assumed $50 internal rate and another $100 in testing or other direct costs, listed delivery cost is $600. That leaves $300 before the agency's other costs.

If setup takes sixteen hours, the same calculation reaches $900 in delivery cost. The fee then leaves nothing for other costs or profit. That is a reason to inspect the estimate before signing, especially where the client's system or data needs work.

List the setup deliverables and acceptance conditions. A paid configuration task could include one approved workflow, a defined test set, staff training and a documented handover. A new calendar, extra location or historical data clean-up needs a decision about whether it belongs in that price.

Connect the final payment or service start to a clear acceptance process. Testing the saved record and staff handoff gives you observable conditions to use. A polished demonstration is weaker evidence than the correct result in the client's queue.

Choose a billing model the client can understand

A fixed monthly fee with a defined usage allowance can make ordinary months predictable. Specify the overage rule and what happens before a significant increase. If you offer a pure usage model, account for the support work that continues during low-volume months.

Some agencies separate the managed service fee from provider usage. That can make cost changes easier to explain, provided the client understands who owns each account, how charges are reconciled and whether the agency adds a markup.

Choose the model after looking at the workflow and buyer's preferences. A fixed fee without a meaningful scope boundary creates exposure to unlimited work. A complicated list of small charges can make a straightforward service difficult to buy.

The quote should answer these questions:

• What is the monthly service result?
• Which usage unit and allowance apply?
• What happens when usage exceeds the allowance?
• What support hours and response commitments are included?
• Which routine information updates are included?
• What counts as additional implementation work?
• Who pays provider charges, and where can they inspect them?

Give a worked quiet-month and busy-month example using the proposed terms. Keep those examples labelled and include any minimum fee.

For Vora itself, see pricing: discuss platform access, metered usage and external service charges for the configuration you need, and confirm inclusions and payer responsibilities in the quote.

Reserve capacity for changes without promising unlimited work

Define a routine update, such as an approved opening-hours correction within the existing workflow. Specify how often staff can submit those changes and when the agency applies them.

A request to add appointment rescheduling is different. It changes the actions, access and tests required. The scope-change guide covers how to assess that request before it becomes recurring work inside the original fee.

Avoid charging for every defect as though the client requested an enhancement. If the accepted scope requires corrected callback details and the workflow loses them, the existing deliverable needs repair. A change-control process should preserve that distinction.

When the buying question needs evidence, propose a paid AI pilot with its own fee and acceptance conditions. State the likely recurring commercial terms before the pilot, so the client can assess the result against the service they would actually buy.

Review the quote against the first delivery period

Keep usage and work records by client. Separate routine support, defects, client changes and improvements you chose to make for the agency. Compare each category with the assumptions in the quote.

If support time repeatedly exceeds the allowance, inspect the cause before changing the price. The service may need a better handover, a repaired workflow, narrower scope or a revised commercial agreement. Those call for different conversations.

Before sending the next quote, fill in its estimated setup hours, recurring support hours, billable usage and excluded work. Then ask another person to calculate the quiet-month and busy-month totals from the proposal alone.

Reusable quote worksheet

Fill one copy per client. Keep each cost in one row only: if a provider bundles two components into one charge, list the bundle once and note what it includes.

First confirm the units you are using. Workload: the calls or conversations the client expects. Platform: the fees for the software you operate. Usage: metered units on the invoice. Provider: separately billed telephony, speech or model charges. Service effort: your hours for setup, monitoring, support and changes.

Then calculate a quiet month and a busy month from the same sheet. A result from this worksheet is a planning figure for one client, not a guarantee. For Vora platform access, metered usage and external service charges, see the pricing page and confirm inclusions and payer responsibilities in the quote you receive. This article does not set a Vora tariff.