Blog · August 22, 2026 · 10 min read

The Voice AI Agency Contract: What Goes in an AI Receptionist Service Agreement (2026)

By Nabeel Hassan — builder of VoiceDash

The Voice AI Agency Contract: What Goes in an AI Receptionist Service Agreement (2026)

TL;DR: Most voice AI agencies sign their first clients on a payment link and a Loom video, then get burned around client four by scope creep, a usage bill nobody agreed to, or an argument over who owns the phone number. A workable AI receptionist service agreement covers eight things: scope written as what the agent does and never does, uptime you can stand behind, ownership of the agent, number and call data, pricing with the usage pass-through spelled out, compliance and recording consent, a change request process, term and offboarding, and what the client gets to see. I build production voice agents for US clients and run VoiceDash, the white-label client portal agencies use to show clients what their agent did, so this is the clause list I wish I had written down before my third client. I am not a lawyer and none of this is legal advice, so have an attorney in your jurisdiction review anything you actually send.

A voice AI retainer is an unusual thing to sell. You are reselling infrastructure you do not control, running an autonomous system that talks to the client's customers unsupervised, and billing monthly for something the client cannot see happening. That combination produces a very specific set of disputes, and nearly all of them are preventable with a page and a half of plain language.

Why a handshake stops working around client three

Your first client is usually forgiving, often someone who already knows you. The agreement is a Stripe link and a promise. That works right up until it does not, and it fails in the same few places every time.

  • "Can it also call our old leads?" Outbound was never in scope, but nothing says so, and now saying no feels like bad service.
  • A usage bill nobody expected. A busy month triples call minutes, your Retell and Twilio costs move with it, and the retainer you quoted assumed a quiet month.
  • The phone number fight. The client cancels and wants to take the number you provisioned on your own Twilio account. If you never wrote down what happens to it, you are negotiating that under pressure.
  • A bad call at 2am. The agent mishandles something, the client asks who is responsible, and the answer is a conversation instead of a clause.
  • The month-three quiet. The client cannot see anything happening, so they start wondering what they pay for.

A contract here is not about suing anyone. Nobody is taking a $1,200 a month client to court. It is about a shared definition of done, so that when one of these moments arrives you are reading from a document instead of improvising.

Clause 1: Scope, written as two lists

The single highest-value paragraph in the whole agreement is a plain-language description of what the agent does, followed by an equally plain list of what it does not.

Included should name specifics, not categories: inbound answering on one business number, around the clock, answers drawn from the knowledge base the client approved, booking on one named calendar, transfers to a human under the agreed rules, and a post-call summary written into the client's CRM.

Not included is the half most agencies skip, and the half that protects the relationship: outbound campaigns, extra numbers or locations, extra languages, integrations beyond the ones listed, changes to the client's booking system, SMS or email marketing, and rewriting the agent for a new service line.

Attach the knowledge base and the escalation rules as an exhibit instead of describing them loosely in the body. The material you gather during client onboarding is already most of that exhibit, and the transfer logic from how to transfer a voice AI call to a human belongs there in writing. List what the agent refuses to do as well, drawn from the prompt you wrote, because a client who sees the refusals up front does not read them as failures later.

Clause 2: Uptime, and the promise you cannot make

You sit on top of Retell, a telephony provider, and a model provider. You control none of their availability, so promising 99.9% uptime is writing a check three other companies have to cash.

Commit instead to the things you actually control:

A monitoring and response commitment. You monitor the agent and respond to a reported outage within a defined window, during business hours in a stated timezone, on one channel. Response time, not resolution time, because resolution depends on vendors you do not control. Agencies that promise round-the-clock support on a $500 retainer find out what that costs during the first bad weekend.

A defined failover. Say exactly what happens when the agent is unavailable: calls forward to a human line, to voicemail, or to a fallback number the client nominates. Clients care about this clause more than any other in the section, because it turns an outage into an inconvenience.

An explicit dependency disclaimer. Name your upstream providers and state that outages originating with them are excluded from any service credit. If you offer a credit at all, cap it at a portion of that month's fee.

Clause 3: Who owns the agent, the number, and the data

Three different questions, and clients assume the answer to all three is "us."

The phone number is the one that turns into a real fight. If you provisioned it under your own telephony account, say plainly whether it ports out on termination, on what timeline, and at whose cost. My preference is to have the client keep their own number and forward it, which sidesteps the issue entirely and is easier to sell, for the reasons in voice AI phone number setup. If you do provision it, being generous in writing about porting it out costs you nothing and removes a real objection.

Call recordings and transcripts are the client's business data. You are handling it on their behalf. State the retention period, who can access it, and that they can export it. This is also where a healthcare or legal client's requirements land, and it needs to be consistent with the recording rules in voice AI call recording compliance.

The agent configuration and prompt are usually your agency's intellectual property, and it is fine to say so, as long as you say it explicitly. A client who paid a $2,500 setup fee often assumes they bought the build. Either you retain it and license it for the term, or they own it and you priced accordingly. Both are defensible. Silence is not.

Clause 4: Pricing, and the usage pass-through

Price the way I laid out in voice AI agency pricing: a setup fee for the build, then a monthly retainer, never raw per-minute billing to the client. But the contract has to handle the fact that your own costs are per minute.

Spell out an included allowance and an overage rate. Something like "includes up to 750 connected minutes per month, additional minutes billed at $X per minute" is easy for a client to understand and protects you in a spike month. Set that rate with the real underlying economics in front of you, which I broke down in Retell AI pricing explained, and leave margin rather than passing through at cost.

Three short lines finish the section. The setup fee is non-refundable, because it pays for build labor already performed. Payment is due on a stated day, and you may suspend service after a grace period. And an annual review clause lets you adjust pricing with notice, because upstream pricing moves.

Clause 5: Compliance, consent, and who indemnifies whom

This section is short but it is the one that matters if something goes badly.

Recording and disclosure. State that calls are recorded, that the client is responsible for the legality of recording in the states they operate in, and that the agent discloses it is an AI when required or asked. The details are in voice AI call recording compliance, and the clause has to match what the agent actually says on the call.

Outbound warranties, if you do outbound at all. The client warrants they own the number, that any list they hand you has the consent it needs, and that they carry the do-not-call obligation. You dial on their behalf and cannot verify their list. Anything touching protected health information needs its business associate agreements settled with every vendor in the chain before the build starts.

Indemnity that runs both ways, unevenly. The client indemnifies you for the content they supplied, the lists they provided, and their own regulatory obligations. You indemnify for your own negligence. Cap total liability at the fees paid over the preceding few months, which is standard at this size.

Clause 6: Change requests, so scope creep gets a price

Give small changes a home so they do not turn into resentment. "Prompt and knowledge base adjustments within the existing scope, up to two rounds per month" covers the normal drift of a business whose hours or services change.

Everything beyond that gets a written change order with its own fee: a new integration, a second location, a new language, an outbound campaign, a rebuilt booking flow. The point is not to nickel and dime anyone. It is to make the boundary visible, so when a client asks for something genuinely new you can say yes with a number instead of quietly absorbing it. That is the same discipline that lets an agency add clients without adding hours, the theme of how to scale a voice AI agency.

Clause 7: Term, notice, and offboarding

Month-to-month with thirty days notice is the easiest thing to sell and removes the biggest objection in the close, which I get into in how to sell AI receptionists. If your setup fee does not cover your build cost, a ninety day initial term is a fair alternative. Pick one, not both.

Then write the offboarding paragraph, which almost nobody does. On termination the number ports or forwards back on a stated timeline, the client gets a data export within a stated window, portal access ends on a stated date, the agent is deactivated, and the final invoice includes trailing usage. A clean exit clause makes clients sign faster, because it tells them they are not trapped.

Clause 8: What the client gets to see

The last clause is the one that keeps the retainer alive. Say what visibility the client has: a portal with their calls, recordings, transcripts, usage, and the outcomes the agent produced, plus whatever recurring summary you commit to.

This is not a formality. Churn in this business is rarely about a bad agent, it is about an invisible one. A client who cannot see what happened last month assumes nothing did, and that assumption shows up around the third invoice. Writing the reporting commitment into the agreement forces you to build it, which is the whole argument in voice AI client reporting.

A raw Retell developer dashboard is not an answer, because it exposes another vendor's brand and makes a real service look like a side project. That is why I built VoiceDash. It connects to your Retell account, pulls every agent's calls, recordings, transcripts and usage, and gives each client a portal with your logo on your own domain, scoped to their own data only. Live in under 10 minutes, no code, plans start at $19/mo with a 7-day free trial. VAPI and Bland support are coming soon; today it is purpose-built for Retell agents.

The clause checklist, condensed

  • Scope: two lists, included and excluded, with the knowledge base and escalation rules as exhibits
  • Uptime: monitoring, response window, defined failover, upstream dependency disclaimer
  • Ownership: phone number porting, recording retention and export, prompt and configuration IP
  • Pricing: setup fee, retainer, included minutes, overage rate, payment terms, annual review
  • Compliance: recording consent, AI disclosure, outbound warranties, regulated vertical requirements
  • Indemnity: client covers their content and lists, you cover your negligence, liability capped at recent fees
  • Changes: included revisions per month, written change order for anything new
  • Term: month-to-month with notice, plus a real offboarding paragraph
  • Visibility: portal access and reporting commitment
  • Boilerplate your attorney will add anyway: confidentiality, assignment, governing law, entire agreement

The bottom line

The contract is not the hard part of running a voice AI agency, but it decides whether client four is a good month or a bad one. Write scope as two lists, promise only the uptime you control, settle the number and the recordings before anyone needs them, spell out the usage pass-through, put the compliance burden where it belongs, give changes a price, and commit in writing to showing the client what their agent did. Then have an attorney read it once and reuse it forever.

Want the visibility clause to be something you can actually deliver on? Start free on VoiceDash or book a demo and I will walk you through the reporting layer that turns a Retell agent into a retainer that renews.

FAQ

Do I really need a contract for voice AI agency clients?

Once you are past the first client or two, yes, and not because you plan to enforce it in court. Nobody is taking a $1,200 a month retainer to litigation. The value is that a written agreement gives you and the client a shared definition of done before the five predictable disputes arrive: a request for outbound calling that was never in scope, a spike month where per-minute usage blows past what the retainer assumed, a cancellation where the client wants to take a phone number you provisioned on your own telephony account, a call the agent handled badly with no stated allocation of responsibility, and the month-three moment where a client who cannot see any activity starts asking what they are paying for. Each of those is a paragraph of plain language written in advance rather than an argument improvised under pressure. Have an attorney in your jurisdiction review it once, then reuse the same document for every client. I am not a lawyer and none of this is legal advice.

What uptime or SLA should a voice AI agency promise a client?

Not 99.9%, because you do not control it. Your agent runs on top of a voice platform like Retell, a telephony provider, and at least one model provider, so a hard uptime number is a promise three other companies have to keep for you. Commit instead to the parts you actually own. First, a monitoring and response commitment: you watch the agent and respond to a reported outage within a defined window, during business hours in a stated timezone, on one channel, and it is response time rather than resolution time because resolution depends on upstream vendors. Second, a defined failover that says exactly what happens when the agent is unavailable, whether calls forward to a human line, to voicemail, or to a fallback number the client nominates. That is the clause clients care about most, because it turns an outage into an inconvenience. Third, an explicit dependency disclaimer naming your upstream providers and excluding their outages from service credits, with any credit you do offer capped at a portion of that month's fee.

Who owns the phone number and the call recordings, the agency or the client?

Whoever the contract says, which is exactly why it needs to say. These are three separate questions and clients tend to assume the answer to all three is them. The phone number causes the most friction: if you provisioned it under your own telephony account, state plainly whether it ports out on termination, on what timeline, and at whose cost. The cleanest arrangement is for the client to keep their own number and forward it to the agent, which removes the question entirely and is easier to sell. Call recordings and transcripts are the client's business data that you handle on their behalf, so state the retention period, who can access it, and that they can export it on exit. The agent configuration and prompt are usually agency intellectual property, and that is a fine position to take as long as you write it down, because a client who paid a setup fee often assumes they bought the build. Either you retain it and license it for the term, or they own it and you priced accordingly. Silence is the only wrong answer.

Give your clients a dashboard with your name on it

VoiceDash turns your Retell agents into branded client portals. Live in under 10 minutes, no code.

Start freeBook a demo

Keep reading