Adel Atya Talk to the demo
Blog · Ai Phone Agent

How long does it take to set up an AI phone agent?

Adel Atya · 15 November 2026

A demo number you can call comes within about 48 hours. Going live on your real line is a separate date, set mostly by your phone number. A simple port can take one business day under the FCC rule. A complicated one takes longer.

Treat "demo" and "live" as two milestones, and ask any builder for a date on each.

What happens in the first 48 hours?

On my voice agent page the process has four steps:

  1. You tell me the three calls you get most.
  2. I build and test it. The agent runs against 20 scripted calls first.
  3. You call it yourself. You get a demo number before go-live.
  4. Go live and hand over.

The 48 hours is the service page's promise of a demo number you can call, and the 20 scripted calls in step 2 happen inside it. Going live is step 4, and it has no fixed clock.

What decides how long going live takes?

Three things set the date.

Your approval. After you call the demo, you decide when the script is right. The longer you take to reply, the later go-live is.

Your phone number. The agent must receive calls on the number your customers already dial. How that connects depends on your carrier.

Text registration. Only if you want text-back, covered below.

How do you connect your existing business number?

The simplest idea is call forwarding: your carrier sends calls to the agent's number. Ask your carrier whether your plan supports it.

The other route keeps your number where it is and connects it to the agent platform. On Retell this is called SIP trunking, which is a way for a phone provider to pass calls over the internet to another system. The steps below come from Retell's custom telephony guide, not from my own setup, so check your platform's docs if you use another one:

Then comes the step that is easy to skip. The same page says a passing connection test does not verify call behavior. It tells you to place an outbound call and receive an inbound call to confirm routing and audio. Do both before you call it done.

What if the number has to move to a new carrier?

Moving a number is called porting, and I cannot speed it up. The FCC reduced the interval for simple wireline-to-wireline and simple intermodal ports to one business day, effective August 3, 2009. It is a 2009 rule and covers simple ports only.

Ask your carrier whether yours counts as simple before anyone promises you a launch date.

Does the text-back add time?

Twilio says anyone sending texts over a normal 10-digit US number must register for A2P 10DLC. That means creating a brand (who is sending) and a campaign (what the messages are for).

Twilio's page gives no approval time, so I will not invent one. Ask your builder about registration at the start, so it does not surprise you at go-live.

Why not skip testing to go live faster?

Because testing is where the real problems show up, and the demo call is where you hear them. Before you hear an agent, it runs against 20 scripted calls. My own test suite is bigger.

It runs 38 simulated callers and 114 calls per run, for about $0.25 a run. Its first run caught 5 missed emergency handoffs in 41 plumbing calls on a cheaper model.

A launch that skips testing ships that gap to your real customers. I describe the method in how I test AI phone agents.

Before launch, run your own check. Call the agent ten times, ask for something it does not know, interrupt it, and try an emergency.

When is fast setup the wrong goal?

Checklist before you start the clock

How the paths compare (only the FCC figure is a published duration):

Then the steps to take:

When you are ready, call the Blue Ridge recovery demo. It answers in about 1 second.