Voice AI Client Offboarding: What to Do When a Client Cancels Their AI Receptionist (2026)

TL;DR: Every voice AI agency loses clients, and the way you handle the exit decides whether that client refers you, comes back in six months, or tells everyone in their local business group that you held their phone number hostage. A clean offboarding has six parts: confirm the cancellation in writing with a stated end date, hand the phone line back before you switch the agent off, settle the final bill including trailing usage, give the client their call records, close portal access on the agreed date, and run a short exit conversation that tells you why they left. I build production voice agents for US clients on Retell, n8n, GoHighLevel and Twilio, and we run VoiceDash, the white-label client portal agencies hand their clients. This is the offboarding checklist I use, and the mistakes that made me write it.

Most agency content is about winning clients. This one is about losing them well. If you want to lose fewer in the first place, read voice AI client retention first. This post assumes the decision is already made.

Why the exit matters more than it looks

Small business owners talk to each other. Your next client in a niche is often a friend, competitor or supplier of the last one. A dental office that cancelled politely and got a clean handover is a neutral or positive reference. One that missed calls for two days because the agent was switched off before the number came back is a story they will tell at every chamber of commerce lunch.

Cancelled clients come back. Many of the reasons clients leave, a budget cut or a new office manager, do not survive six months of missed calls. The client who left on good terms is the easiest sale you will ever make, because you already have the prompt, the integrations and the call history.

The phone line is a real liability. An AI receptionist sits on the most important wire in a small business. If you get the order of operations wrong during the exit, real customers hit dead air. That is the one part of offboarding where a mistake costs the client money the same day.

Step 1: Confirm the cancellation in writing, with a date

The cancellation often arrives as a casual text or a mention on a call. Do not act on that. Reply in writing, restate what you heard, and propose a specific end date based on your agreement's notice period.

The confirmation should say:

• The date the agent stops answering calls
• What happens to the phone number, and when
• What the final invoice will include
• When portal access ends
• That you will send their call records before that date

This is the paragraph I recommend writing into every agreement up front, covered in the voice AI agency contract post. If the terms already say all of this, the confirmation is a two minute email instead of a negotiation.

Step 2: Hand back the phone line before you switch anything off

This is the step that hurts people when it goes wrong, so I do it in a fixed order.

If the client kept their own number and forwarded it

This is the setup I recommend for every deployment, for exactly this reason, as I explain in voice AI phone number setup. Offboarding is simple:

1. Agree a cutover time with the client, ideally a quiet afternoon.
2. The client, or their carrier, removes the forwarding rule to your Retell number.
3. Call their main number from an outside phone and confirm it rings their office or whoever now answers.
4. Only after that test passes, deactivate the agent.

If you deactivate the agent first and the forwarding is still in place, every caller gets silence or an error until someone notices. Always remove the forward first, test, then turn off.

If you provisioned the number on your own telephony account

If the client's public number lives on your Twilio account, you have two clean options:

• Port it out to the client. They open an account with a carrier of their choice and request the port. You release the number when the request arrives. Ports take days, not minutes, so start this as soon as the cancellation is confirmed, not on the last day.
• Forward it to the client while the port completes. Point the number at their office line so calls keep landing somewhere while the port is in flight.

Do not release the number back to the carrier pool to save a few dollars a month. A number printed on the client's trucks and Google profile is not yours to throw away, even if it sits on your account. Being generous here is what separates a professional exit from a bitter one.

Do not forget the integrations behind the call

Voice agents rarely work alone. Before the final shutdown, list everything the agent touches: calendar booking, CRM updates in GoHighLevel, n8n workflows, SMS confirmations, call transfers. Each one either needs to be switched off or handed over. If you followed the patterns in how to connect Retell AI to n8n, those workflows are easy to find because they are named per client.

Step 3: Settle the final bill, including trailing usage

The last invoice is where good exits turn sour, so make it predictable.

• Stop the subscription at the end date, not the day they told you. If your agreement has a notice period, the final period is billed as normal.
• Bill trailing usage. If the client is on included minutes with an overage rate, the final period's usage gets counted like any other month. Say this in the confirmation email so it is not a surprise.
• Do not invent exit fees. If it is not in the agreement, do not add it now. You will win back more from goodwill than from a surprise fee.

If you bill through Stripe subscriptions, cancelling at the end of the period is a setting, not a manual reminder in your calendar. The full billing setup is in how to bill voice AI clients.

Step 4: Give the client their call records

Clients rarely ask for this, which is exactly why offering it matters. Months of recordings, transcripts and summaries are a record of their own customers calling their own business.

Before portal access ends:

1. Tell the client in writing that access ends on a specific date.
2. Remind them a few days before that date to save anything they want to keep, and offer to send an export of whatever they ask for.
3. Agree what happens to the data after that, in line with your agreement and any rules their industry follows.

If the client is in a regulated industry, such as healthcare, retention and deletion are not just courtesy. Check what applies before deleting anything, and read voice AI call recording compliance and HIPAA compliant AI receptionist if that covers your client.

Step 5: Close access cleanly

Once the end date passes:

• Remove the client's logins and their team's access to the portal.
• Deactivate or delete the agent in Retell so it cannot take a stray call.
• Remove their API keys, calendar connections and CRM credentials from your tools.
• Archive their prompt, knowledge base and configuration in your own files.

That last point is easy to skip and worth a lot. If the client comes back, you restart from a working build instead of from zero.

In VoiceDash, every client is its own isolated workspace with its own login and team access, so offboarding one client is contained to that workspace. Nothing about closing one client's access touches any other client's agents, calls or analytics.

Step 6: Run a short exit conversation

Ask for fifteen minutes. Not to win them back on the spot, but to learn. I ask three questions:

1. What made you decide to stop?
2. Was there a moment where you started doubting it was worth it?
3. What would have to be true for you to come back?

The answers cluster fast. In my experience, clients rarely cancel because the agent was bad. They cancel because they could not see what it was doing. The owner hears about one awkward call from a customer and has nothing to weigh it against, because the hundred calls the agent handled well are invisible to them. That is a reporting problem, not an agent problem, and it is why I push agencies to give every client a portal from day one. What to put in front of them is in voice AI client reporting, and the complaint side is in voice AI client complaints.

The offboarding checklist

Here is the whole thing in order:

1. Confirm the cancellation in writing with an end date.
2. Start any number port immediately if you own the number.
3. List every integration the agent touches.
4. Remind the client to save their call records before access ends.
5. On the cutover day, remove forwarding or point the number at the client.
6. Test the main line from an outside phone.
7. Deactivate the agent and switch off its workflows.
8. Cancel the subscription at the end of the period and bill trailing usage.
9. Remove portal logins and stored credentials.
10. Archive the prompt and configuration.
11. Run the exit conversation and write down the answer.
12. Put a reminder in your calendar to check in three to six months later.

Mistakes I made so you do not have to

Agent off before the forward came off. Callers heard silence for most of a morning. The order is now fixed: forward removed, line tested, then agent off.

No end date. A client said "let's wrap this up" and I kept the agent running for three weeks while we went back and forth. Now every cancellation gets a dated confirmation within a day.

Deleting the build. I cleaned up a cancelled client's agent completely. They came back four months later and I rebuilt it from memory. Now everything gets archived.

The bottom line

Offboarding a voice AI client is mostly about order of operations. Confirm the end date in writing, give the phone line back before the agent goes quiet, bill the final period exactly as agreed, let the client take their call history, close access, and ask why they left. Do it well and the client who cancelled becomes a reference, a referral, or a returning customer.

The fastest way to need this checklist less often is to make sure clients can see what their agent does every day. If you want every client in a branded portal with your logo on your domain, showing their calls, recordings, transcripts and usage, start free on VoiceDash or book a demo and I will walk you through it.