# AI receptionist for agency clients

> An AI receptionist for agency clients is their line, not yours. How to set it up, hand over the keys, and what you should not promise.

Published 2026-11-15 · by RingKit · tags: ai receptionist, small business. Canonical: https://www.ringkit.com/blog/ai-receptionist-for-agency-clients

An AI receptionist for agency clients is a phone line you set up in the client's name. They own the business record, they pay the wallet, and they can cut off your key. RingKit has no reseller program, no agency price, and no white-label brand. The product a client gets is the same product an owner gets by signing up. Your work is the setup, the brief, and the hand-over. If a proposal says "our receptionist platform," rewrite it. The line will say it is an AI for their business, not for yours.

What follows uses a one-person glass shop as an example. It is not a customer, and it has no call volume attached. The judgments are the same for a plumber, a studio, or a shop you already design for. The HTTP steps, if you would rather read them as curl, are the [AI agent phone number](https://www.ringkit.com/blog/ai-agent-phone-number) page and the [docs](https://www.ringkit.com/docs#quickstart). This page is the part those leave to you: whose name is on the account, who pays, and what you are allowed to tell them.

## The record is in their name

Create the business with their legal or trade name, their IANA timezone, and their email as `ownerEmail`. Leave `ownerPhone` off that call. The API refuses it on create with `403 destination_unverified`. A business that does not exist yet cannot have proved it controls a mobile. You add the phone later, after a verification call.

The response is the business id and an API key, once. That key is scope `manage`. It acts as the owner. There is no parent account above it and no agency key that spans clients. If you set up ten shops, you have ten businesses and ten keys. Mix them up and you will change the wrong brief. Name the key after the client the day you create it, and store it where the rest of the team can find it and a stranger cannot.

The client does not need to sign in for any of this. The docs are explicit: the only thing a person must do is pay. Sign-in is optional, and it comes last. Do not block the setup on a portal password they will not pick until Thursday.

## Collect five facts, then stop asking

Before the first API call, get the business name, the timezone, the email that should receive the invite, the mobile they will answer for a verification code, and either a website or the facts in writing. Hours, service area, prices they will stand behind, and the two or three questions callers actually ask. For the glass shop, that might be shower doors, storefront board-up, and whether they do insurance work. If they do not do insurance work, the brief should say so. A caller with a claim will ask.

Do not invent a price to make the profile look finished. The receptionist answers from what you stored. A number you guessed becomes a quote. If a price is "it depends," store that sentence, not a placeholder dollar amount. If you do not have hours, say you do not have them yet and do not publish the line.

A website import fills only fields that are still empty. It does not replace a price someone typed, and it does not know that the homepage still shows last season's special. Read the import with the client before a stranger can hear it. A setup chat is the other way: they answer in sentences, and the same profile gets the result. Either way, the client reads it. You do not "turn it on and fix it from the calls." The first calls are the ones a new customer judges.

## Transfers are their people

`mode` is `ai_only`. The receptionist answers every call. RingKit does not staff a backup person. Transfers go to the client's own numbers, each with a `whenToUse` a stranger could follow.

"Emergencies" is not a rule. For the glass shop, a usable rule is: "the caller has broken glass at a storefront, or a window that is open to the street," and that number is the owner's mobile. "How much is a shower door" is not that rule. It is a message: size, neighborhood, and a callback number. If nobody answers the transfer, the call ends as a message. Do not write a prompt that says a technician is on the way. Nothing in the product dispatches a truck.

Write the rules with the person who actually answers the phone today. An agency that copies the same three rules into every client will transfer the wrong calls. A locksmith and a glass shop both get "emergency" calls. They do not mean the same thing, and they should not share a sentence.

## The client pays the wallet

There is no free trial and no sandbox you can demo on forever. A text simulation runs the real receptionist and is billed from the wallet at the AI rate. Fund the wallet before you treat a test as proof. `POST …/wallet/top-ups` with `amountCents` of at least 1000 returns a checkout URL. The smallest top-up is $10. A person opens the URL and pays. The API does not charge a card by itself.

Hand that URL to the client. Paying it on your agency card makes you the funder of their phone bill, and RingKit will not send you their invoice. The wallet is prepaid. Talk time is $0.20 a minute, the first 10 seconds of each call free, then 6-second increments, so a 2:10 call bills as 2:00. A US local number is $1.99 a month. A month with no calls is $1.99 if the number stays. A payment method is required before the number goes live, and ordering it needs $2 of paid credit or the API returns `402 funding_required`.

The [pricing page](https://www.ringkit.com/pricing) is the rate card to send them. Do not round it, and do not add a monthly plan RingKit does not sell. If your agency charges a setup fee, that fee is yours. Say so in your proposal. Do not imply it appears on the RingKit wallet.

## Their number stays with their carrier

Clients ask to "move the shop number over." RingKit does not port numbers. You order a new US local number, or they keep the number customers already know and forward it. Forwarding leaves the number on their current carrier. Porting is a different job, and it is not this product.

The FCC's consumer guide, [Porting: Keeping Your Phone Number When You Change Providers](https://www.fcc.gov/consumers/guides/porting-keeping-your-phone-number-when-you-change-providers), opened 15 November 2026, describes porting as switching providers and keeping the number, in the same geographic area, between wireline, IP, and wireless. The new company starts the port. The guide says not to terminate the old service before that. It also says porting is not always possible when someone moves to a new geographic area.

None of that is a RingKit workflow. If the client wants to leave their carrier, they start a port with whatever company they are moving to. You do not start that port from this API. If they want to keep the carrier and have calls answered, they turn on forwarding to the RingKit number, using their carrier's own steps. Those are two sentences on a sales call. Mixing them up is how a shop cancels a line it still needed. A new business that does not have a number yet is a different case, covered in [Business phone for a new LLC](https://www.ringkit.com/blog/business-phone-for-a-new-llc). They can start on the RingKit number. They still are not porting.

## Invite them, then decide who keeps the key

When the brief is something they have read, the number is in, and a test call has reached a phone they verified, send the invite. `POST /v1/businesses/:id/owners/invite` emails a sign-in link. Leave `email` out to use `ownerEmail`. The limit is 5 invites per business per hour. The response says the mail was sent. It does not mean they have opened it.

When they sign in, the business gets `ownerSignedInAt`. The dashboard shows that an agent set the line up, and it lets them rotate or revoke the agent's key. Tell them that before they click, not after they find a key they do not recognize. The docs say you can keep running the line either way. That is a permission, not a default you should assume. Ask which they want.

If they want you to keep changing the brief, they leave the manage key in place and they know it. If they want you to pull summaries and nothing else, create a key with `scope` `read` and revoke the manage key. A read key that tries to change routing gets `403 insufficient_scope`. If they want you gone, they revoke every key you hold, and the line keeps answering. Revocation does not release the number and does not empty the wallet.

## The code on the verification call is theirs

The verification call is separate from the invite. `POST …/destinations/verify` rings the mobile and reads a 6-digit code. The person who answers tells you the code. That is their consent to be called. You cannot hear it from the API. Confirm with `POST …/destinations/confirm` and the digits they read you. Then `POST …/test-call` rings that number from the RingKit number. Until the confirm succeeds, a test call is refused.

The docs cap test calls at 5 per business per day, and outbound calls at 3 per number per day. A team that tries the line from three laptops can spend the cap before the client has heard it. One person places the test, with the client on the phone. Do it after they have read the brief. A test of an empty profile only proves the phone rang. Do not ask a teammate to confirm a code the client did not hand them.

## What you may say, and what you may not

You may say the receptionist answers from their brief, says it is an AI, and plays a consent notice because calls are recorded and transcribed for the summary. You may say it transfers to numbers they listed and takes a message otherwise. You may say every call gets a summary: who called, what they needed, the next step. You may quote the rate card above. You may say there is no contract and no monthly minimum beyond the $1.99 number.

You may not say it books appointments. A requested time lands in the summary or in a transfer. You may not say there is a free trial. You may not say it texts callers. You may not say it speaks other languages, that it is HIPAA compliant, that it connects to their CRM, or that there is an SDK. You may not say a person at RingKit will pick up. You may not say you are a reseller or that their number will be ported.

If the proposal needs one of those sentences to win the work, this is the wrong product. Sell a different one, or sell the work you can actually do: the brief, the forwarding, and the hand-over.

## Turn the job down when a person is the point

Some clients should not get this line, and you should say so. A shop that already has someone at the desk who knows the regulars does not need an AI in front of that person during the hours they are there. Use forwarding for the hours the desk is empty, or do not use it at all. A client who wants a confirmed slot on a calendar wants a booking product. This one records the request. A client who will not read the brief should not have a number yet. You cannot fix a wrong price from a dashboard they will never open.

A quiet shop fits the per-minute wallet. A line that rings all day may fit a flat monthly service better, and this page does not price those.

The glass shop example is a fit when the owner is on a job, the board-up calls need a transfer, and the shower-door calls can wait as a message. It is a bad fit when they want you to pretend a person named the estimate. Write the brief so the receptionist says it will take the details and the owner will call back. That sentence is the whole product.

## After they sign in

You do not have their carrier login. Write down which carrier the number is on before you leave. The next "why did that hit voicemail" question needs that carrier's forwarding steps, not another invite. They forward the published number, or they start giving out the new one. Ask them to call from a phone that is not the shop line: once during hours, once when the phone is busy, once with the phone off. If the busy case still hits their old voicemail, the forwarding is not the rule you think it is. Fix that before you call the project done.

Then stop holding the manage key unless they asked you to. Pull summaries with the read key, or teach them where the call list is and leave. A client who can revoke you is a client who owns the line. That was the offer. An agency that cannot stand to lose the key was selling access, not a setup. The invite exists so they can take it back.

---

Try Ringkit: $0.20/min, $1.99/mo per number, no plan. Get started at https://app.ringkit.com/onboard
