Phone AI Agent: The Ring-Delay Decision Every Deployment Gets Wrong

A phone AI agent is a forward target, not a phone

Most vendor pages describe a phone AI agent as something you “install” or “plug in.” Operationally that is misleading. A phone AI agent, PieLine included, is a phone number that your carrier forwards to. Your restaurant's published number does not change. The line on the counter does not move. What changes is the rule on your business line at the carrier: “under condition X, route this call to the AI agent's number.”

That condition is where every deployment silently diverges. Carriers support three practical modes: unconditional forward (every call goes to the AI immediately), delayed forward (forward after N rings if no one picks up), and busy forward (forward only if the counter line is already occupied). Combinations are allowed. No one talks about which to pick because the AI vendor does not own that setting, and the carrier does not know what the AI does.

This page is about that gap. The spec below is the actual decision on deployment day.

The three modes, and who each one fits

Most independents should start in Mode C, move to a hybrid of B and C after two weeks of transcript review, and only adopt A if the transcripts show that staff answering is actively slowing down the order (long holds, hunt for a pen, missed modifiers). A is a QSR pattern, not a default.

Ring-delay changes your concurrency math

A phone AI agent has a concurrency ceiling: how many simultaneous calls it can hold without degrading. PieLine's is 20. Your ring-delay mode changes how much of that ceiling you actually consume.

• Mode A consumes 100% of your call volume. Your ceiling must cover peak.
• Mode B consumes roughly (peak call volume) × (1 minus staff answer rate in the first N rings). If staff answers 40% of calls in the first 4 rings, the AI sees 60% of peak.
• Mode C consumes only the overflow: (peak call volume) minus (your counter-line hardware capacity). A single counter phone caps at 1 call; a 2-line system caps at 2. Everything beyond that hits the AI.

Worked example. A pizzeria with 45 calls in its busiest 15-minute window, 3-minute average call length, 1 counter phone, and staff answering 35% of calls they can physically reach:

• Mode A: 45 × (3/15) × 1.5 safety = 14 concurrent. Well under PieLine's 20.
• Mode B, N=4: 14 × 0.65 = 9 concurrent on the AI side. Staff answers ~16 of 45 calls, the AI handles the rest.
• Mode C: 14 minus 1 counter line = 13 concurrent on the AI side. Staff sees 1 concurrent call at a time, always. This is the politically easiest rollout.

Note that Mode C does not actually save you much concurrency headroom. Its value is not resource savings, it is organizational: staff still feels like the primary voice on the line.

How PieLine is set up in each mode

PieLine does not care which mode you pick. You configure it on your carrier side. What PieLine does is make sure the AI agent's behavior is clean in all three:

• In Mode A, the agent opens with your restaurant name and goes straight to order intake. No “please hold while I connect you” theater.
• In Mode B, the agent knows it is second responder, so its greeting acknowledges the caller already waited: “Sorry for the wait, this is [Restaurant]. How can I help?”
• In Mode C, the agent's first job on pickup is the same as a receptionist's: confirm the caller's intent and apologize that the staff line was busy, then take the order. Callers often do not realize they are on the overflow agent at all.
• Smart Call Transfer, documented on our landing page at src/app/page.tsx in the features section, works in all three modes and passes a conversation summary to the counter phone when escalation is needed.

The agent holds up to 20 simultaneous calls across whichever mode you choose, with 95%+ order accuracy on the phone audio itself. Orders route to your POS (Clover, Square, Toast, NCR Aloha, Revel and others) without re-keying.

How to actually set the ring-delay on your carrier

This is a carrier feature, not a PieLine feature, but here is the shorthand for the ones we see most:

• Most PBX / VoIP business lines (RingCentral, Ooma, Vonage, Grasshopper, 8x8): call-handling rules support “forward after N rings” and “forward on busy.” Set these per number, not per extension.
• Traditional landlines: carrier codes (often *72 unconditional, *71 busy/no-answer, *73 cancel) set the forward. The menu is clunky; expect to call support once.
• Google Voice: unconditional forward only. Mode B and C are not natively supported.
• Mobile-as-business-line: iOS and Android both support conditional call forwarding in their dialer settings. Usable but fragile.

If your carrier supports only Mode A, that is fine, it just means you are committing to AI-first on day one and the staff script needs to match.

Related reading

• Voice agent handoff spec: what to demand from any vendor
• AI receptionist for restaurant phone ordering: full guide
• Vendor comparison for AI phone answering
• POS integration specifics

FAQ

Do I have to change my restaurant's phone number to use a phone AI agent?

No. Your published number stays the same. PieLine gets its own number, and your carrier is configured to forward calls from your business line to PieLine's number under the condition you pick (ring 1, ring N no-answer, or busy-only). The customer dials what they always dialed.

Which ring-delay mode should a typical independent restaurant start in?

Mode C (busy forward only) is the gentlest rollout for a 1 or 2 line independent. The AI only fields the calls that collide with an in-progress call, so staff never feels displaced. After two weeks, pull the transcripts: if staff is missing a lot of calls that the AI never saw, move to Mode B with a 3 or 4 ring delay.

Does ring-delay mode affect the AI's accuracy?

No. The agent's accuracy on order intake is the same in all three modes. What changes is the caller's emotional baseline: a Mode B caller has been waiting 4 rings and wants a brisk greeting, a Mode A caller got picked up in under a second and will tolerate a slightly longer intro. PieLine adjusts the greeting per mode for this reason, not the ordering logic.

What happens if the AI agent is already at its concurrency ceiling?

PieLine's ceiling is 20 simultaneous calls. If you hit it, the carrier either queues, routes to a fallback you define (often voicemail-to-SMS or the counter phone), or rings through. We recommend a fallback that captures the caller's number and triggers an automated callback rather than a cold drop. This is rare in practice: most single-location restaurants never exceed 10 concurrent even at peak.

Can staff still answer if they want to, even after deployment?

In Mode B and Mode C, yes, that is the whole point. The counter phone still rings, staff can pick up, and only calls they do not answer (or cannot answer because another call is in progress) forward to the AI. In Mode A the counter phone does not ring for the forwarded line, so staff would need a separate line or extension to take manual calls.

How does the AI transfer back to staff mid-call?

PieLine's Smart Call Transfer hands the caller back to the counter phone (or a manager line) with a text summary of the conversation so far. Triggers include explicit requests for a human, complaint or refund keywords, allergy mentions, and catering over a size threshold. The summary arrives on the staff side so they can pick up with context in 3 seconds, not re-interrogate the customer.

How fast can a phone AI agent be live on my existing line?

Same day in most cases. Two pieces happen in parallel: PieLine imports your menu from your POS and configures triggers, hours, and greetings; you or your carrier sets the forward rule on your business line. The slowest piece is almost always the carrier console, not the AI. Once the forward is live, every future call routes through the mode you picked.