Get started

An AI phone agent for the store that never closes

An online store is open at 2 a.m., but its phone line usually is not. The catalog sells around the clock and across time zones, and the questions follow the same schedule: where is my order, can I still return this, does this jacket run small, my package arrived crushed, I need to skip next month's box. Most of those calls have answers that already exist in the store's own systems—an order record, a tracking status, a returns policy, a product page. What the caller actually needs is someone to look the answer up and act on it, and what the support team actually needs is to not spend its day doing exactly that.

ThunderPhone gives an e-commerce brand an AI phone agent that answers those calls, reads from the store's connected order and product data, follows the store's own policies for returns and subscriptions, and transfers to a person the moment a call needs one. It works from instructions and documents the store approves, so it applies your return window and your exchange rules rather than inventing plausible-sounding ones.

Turn the ticket queue into a workflow

An e-commerce agent can be configured to:

  • answer "where is my order" from a connected order or shipping system—look up the order, read the fulfillment and tracking status, and state it plainly, including what happens next if the shipment is delayed;
  • start a return or exchange under the store's published policy, create the RMA through a connected API or webhook, and give the caller the next step—label, drop-off, or pickup—per the store's process;
  • answer product questions—sizing, materials, compatibility, care, what is in the box—from product pages imported into the knowledge base by URL;
  • take damaged, lost, and stolen-package reports with a structured intake—order, item, what happened, photos requested by follow-up—and route the case into the store's carrier-claims workflow;
  • handle subscription pause, skip, swap, and cancellation requests per the store's script, including approved save offers, without ever obstructing a cancellation;
  • place back-in-stock calls to customers who opted in when a wanted item returns;
  • place checkout-abandonment callbacks where the store has consent to call, following the store's script and offer rules;
  • absorb peak-season overflow so holiday surge does not mean weeks of hold music;
  • answer account and payment questions at the policy level and route anything requiring card details to staff or the store's self-serve flow; and
  • serve callers in 47 languages on a single support number, switching mid-call when the caller does.

The agent does not guess a delivery date it has no source for, does not approve a return the policy would not, and never takes payment-card details over the phone. You define what it may say, what it must collect, and when it must hand off.

Sample e-commerce call flow

Agent: Thank you for calling Alder & Vine. Are you calling about an order, a return, or something else?

Caller: An order. It was supposed to be here Tuesday and it's not.

Agent: I can check that. May I have the order number, or the email or phone number on the order?

Caller: The email is m.okafor at example dot com.

Agent: Thank you. I see one open order—two ceramic planters, placed on the twelfth. The carrier scanned it this morning at the regional facility, and the tracking now shows delivery tomorrow by end of day. Would you like me to text you the tracking link?

Caller: Sure. And if it shows up broken? The last one did.

Agent: I'm sorry that happened. If anything arrives damaged, call us or use the returns page, and we will replace it under the damage policy—no need to return the broken item first. For this call, I have sent the tracking link to the number ending in 0142. Is there anything else I can help with?

The order status came from the store's connected order system, the damage answer came from the store's own policy documents, and nothing was promised that a system did not confirm. If the tracking had shown no movement past the carrier's lost-package threshold, the agent could have opened a shipping-issue case on the spot and routed it to the claims workflow with the intake already complete.

Features that matter in an online store

Order status from your order data, not from vibes

WISMO—"where is my order"—is the defining e-commerce support call, and it is the call an agent handles best, because the resolution path is deterministic: identify the caller, fetch the order, read the status, offer the next step. ThunderPhone agents can call HTTP APIs and MCP tools mid-conversation, so the agent can query the store's order platform or shipping system live and answer from the actual record. Where a delay is showing, the agent says what the store's policy says—not a soothing guess—and can open a case or arrange a callback.

Returns and exchanges that follow the policy as written

Attach the returns policy to the knowledge base and connect the returns endpoint, and the agent can run the whole intake: confirm the item and reason, check the request against the window and eligibility rules, create the RMA through the connected API or a webhook into the store's returns system, and tell the caller exactly what happens next. Exchanges can follow the same path. Exceptions—out-of-window requests, final-sale items, anything that smells like fraud—route to a person instead of being decided by the agent.

Product questions answered from the catalog you already publish

Import product pages, FAQ pages, and policy pages straight from the store's website by URL, or attach documents (up to 5 MB per text file and 50 MB per PDF or DOCX). The agent searches those sources mid-call, so "does it fit a 15-inch laptop" and "is this machine-washable" get answered from the same copy the site shows. When the catalog changes, re-import the pages and the phone answers change with them.

Shipping-issue intake that feeds the claims workflow

Damaged, lost, and stolen packages are where support earns loyalty or loses it. The agent collects a complete report—order, items affected, delivery-scan status, what the caller sees—applies the store's customer-first policy where one is configured (replacement or refund per the rules), and posts the structured case to the store's carrier-claims workflow by webhook. The claim itself, with its carrier-specific deadlines and evidence requirements, stays with staff and the store's process; the agent's job is to make sure the intake arrives complete on the first call.

Subscription changes without the runaround

For subscription boxes and replenishment programs, the agent can handle pause, skip, swap, and frequency changes through a connected API, following the store's script—including an approved save offer where the store uses one. Cancellation is handled the same way: the agent may present the store's configured alternatives once, and then it processes or routes the cancellation as instructed. It is configured never to obstruct a cancellation, and the reason the caller gives is captured as structured data instead of evaporating.

Back-in-stock and abandoned-checkout calls, under consent

On an eligible production number, the agent can place individual outbound calls or run campaigns: a call to opted-in customers when a wanted item is back in stock, or a callback to a shopper who abandoned a checkout and consented to be contacted. Voicemail detection lets each call follow your policy—leave a configured message, hang up, or let the prompt decide—and campaigns retry voicemail outcomes on a schedule. The store remains responsible for consent, identification, calling windows, do-not-call requests, and other applicable outbound-calling laws.

Peak season without a seasonal hiring spree

Holiday surge is predictable: order volume climbs through Q4, and returns crest after the gifts are opened. An agent does not need to be hired in September to be ready in November. Many stores route the phone to the agent as overflow—after a set number of rings, when all staff are busy, or outside staffed hours—so the team keeps the conversations that need judgment and the agent absorbs the volume that needs a lookup. Because ThunderPhone supports SIP trunks and bring-your-own numbers, the published support number stays exactly as it is.

Account and payment questions, routed—not handled

The agent can answer policy-level billing questions from approved documents—when a refund posts, how store credit works, what the charge descriptor looks like—and route anything that requires account changes or card details to staff or the store's secure self-serve flow. It never asks for or accepts card numbers over the phone.

One number, 47 languages

ThunderPhone supports 47 voice languages. Set a primary language and additional languages, and the agent switches mid-call when a caller changes to one of the configured languages, provided the selected voice supports the set. A store that ships internationally—or simply sells to a multilingual customer base—can offer real phone support in the caller's language without staffing a desk for each one.

The same agent on your website

The web voice widget puts the same agent, with the same connected order data and the same policies, on the store's site as an on-page voice channel. A shopper on the order-status page can ask by voice instead of dialing, and gets the same answer the phone line would give.

Every call reviewable, every change testable

With recording enabled, calls produce recordings, transcripts, and grading, so a support lead can skim how the agent handled the post-Black Friday spike. Before any prompt change goes live, run simulations—a caller with two orders and a vague complaint, an out-of-window return, a cancellation with an emotional edge, a non-English speaker, a lost-package report with no tracking scan—and gate changes behind regression suites with minimum pass rates. A/B experiments can compare two return-flow scripts on live traffic.

Webhooks into the stack you already run

Every completed call can post structured results to your endpoints—signed with HMAC-SHA256—so order lookups, RMAs, shipping cases, and churn reasons land in the helpdesk, the order platform, or the store's data warehouse automatically, instead of living only in a transcript.

What the agent should not do

Guardrails are part of the configuration, and some are platform policy:

  • No payment-card details, ever. Refunds, payment updates, and reorders that require card entry are completed by staff or by the store's existing secure checkout and account flows. The agent collects everything else and hands off.
  • No invented order or delivery information. If no connected system or approved document answers the question, the agent says so and offers the configured alternative—a case, a transfer, or a callback.
  • No policy exceptions on its own authority. The agent applies the returns, refund, and subscription rules as written; anything outside them routes to a person.
  • No cancellation obstruction. Save offers, where configured, are presented once; the cancellation itself is then processed or routed as the store's script directs.
  • Compliance stays configurable. ThunderPhone's public posture is GDPR and HIPAA compliant; the store still controls recording settings, retention, customer notices, and where call data is sent, and remains responsible for its own obligations, including consent for any outbound calling.

What would this cost each month?

Suppose a store handles 3,000 AI-assisted calls per month, averaging 2.5 minutes each:

3,000 calls × 2.5 minutes = 7,500 minutes per month

  • Spark: 7,500 × $0.02 = $150/month
  • Bolt: 7,500 × $0.05 = $375/month
  • Storm: 7,500 × $0.09 = $675/month

That is base engine usage, not a quote. Premium voice or language paths can add up to 3¢ per minute, and phone-number or carrier charges depend on the telephony setup. Hold time bills a flat 2¢ per minute; voicemail and phone-menu minutes bill at the engine rate. Optional add-ons such as verbal acknowledgements, call supervision, and long prompts carry their own published surcharges. The agent builder shows the current all-in rate before calls are placed.

The arithmetic is illustrative. A small store fielding mostly order-status lookups will run shorter; a subscription brand running win-back campaigns and returns-season volume will run longer.

Frequently asked questions

Can a ThunderPhone agent tell customers where their order is?

Yes, when connected to the store's order or shipping system through an HTTP API or MCP tool. The agent identifies the caller, reads the live order and tracking status, and states it—including the store's policy for delays. Without a connected source, it does not guess; it collects the request and routes it to staff.

Can it process returns and exchanges?

It can run the full intake and create the RMA through a connected API or webhook, applying the store's published window and eligibility rules, then tell the caller the next step. Exceptions—out-of-window, final-sale, suspected fraud—route to a person. Refunds that require payment-card handling are completed by staff or the store's own systems.

Can it answer questions about specific products?

Yes, from the product and policy pages the store attaches or imports by URL into the knowledge base. Answers track what the site says; when the catalog changes, re-import the pages and the answers follow. Questions the sources do not answer route to staff.

Can it cancel a subscription, or will it argue with the customer?

It follows the store's script: it may present a configured save offer once, and then it processes or routes the cancellation. It is configured never to obstruct a cancellation, and it captures the stated reason as structured data.

Can it call customers back—for restocks or abandoned carts?

Yes—individual outbound calls or campaigns on an eligible production number, with voicemail detection and campaign retries, for customers who opted in. The store is responsible for consent, identification, calling windows, and other applicable outbound-calling laws.

Can it handle a holiday surge?

Yes. It answers concurrent calls without seasonal hiring, and many stores run it as overflow—after a set ring count, when staff are busy, or after hours—so the published number and the team's role stay unchanged. Regression suites let you tighten the prompts before the surge, not during it.

What about customers who don't speak English?

ThunderPhone supports 47 voice languages on one number. Configure a primary language plus additional languages, and the agent switches mid-call when the caller changes language, provided the selected voice supports the configured set.

Can the same agent work on our website?

Yes. The web voice widget puts the same agent—same connected data, same policies—on the store's site as a voice channel, so a shopper can ask about an order without dialing.