Ecommerce

Nine calls in ten ask where the order is.

An online shop has one kind of call that repeats endlessly, and its answer is already written in the database. The rest of the calls are few and hard. The assistant takes the first kind in full and leaves the second to a person, with the context already gathered.

The assistant identifies the caller by phone number, finds the order in Shopify or WooCommerce, reads back the status and estimated delivery date, records an address change or a return intent as a ticket, and hands anything involving money to a person.

§01 The calls

What rings on the support line

The difference between the calls below is whether the answer exists written down somewhere. When it does, the assistant reads it. When it does not, it hands it over.

Where is my order

Found by phone number or order number, with the status and, if your system holds it, the estimated date.

Address or slot change

Taken as a ticket with the order number, before the parcel leaves the warehouse.

A return request

The reason and the product, recorded as a ticket. Approval and money stay with a person.

Stock and availability

If you expose an endpoint for it, the assistant can quote it. Otherwise it says somebody will check.

A complaint

Recognised early and passed to an operator, with the transcript so far attached to the ticket.

§02 The flow

From a phone number to an order status

The flow uses the commerce connectors that exist today. For a shop on another platform, the same shape is built with your own HTTP tool.

How an assistant is built

01 Identify the caller It looks the customer up by the number they are calling from, through the Shopify or WooCommerce connector. When it finds nobody, it asks for the order number.
02 Find the right order It lists the customer orders and, if several are recent, asks which one rather than assuming it is the latest.
03 Read the status The order status as the platform holds it. It does not invent a delivery date the system does not contain.
04 Open a ticket for everything else Address change, return, complaint: a ticket in Zendesk or Freshdesk, with the order number and the call summary.
05 Hand over the money calls Refunds, disputes, payments. They go to an operator, and the assistant says why rather than attempting them.

§03 The written trail

What stays in support

A support call taken by an assistant has to leave exactly the same trail as one taken by a person, or the support report becomes partial.

What connects to CallAgent today

What stays in support
The ticket	Created in Zendesk or Freshdesk, with the order number, the reason and the call summary.
On the customer	A note on the contact in the CRM, if you keep history there too, through the HubSpot or Intercom connector.
By SMS or email	Confirmation of what was taken down, with the ticket number, so the person has a reference.
On the call record	The transcript, the tools called, the order found, and the structured output with the reason for the call.

§04 Limits

What it does not do for an online shop

It is easy here to imply the assistant resolves the call. Most of the time it does not resolve it, it prepares it.

What is finished and what is not

It executes no payments and issues no refunds The Stripe connector is read-only by design: it finds the customer, the invoices and the subscriptions. It moves money in no direction.
It does not cancel or amend an order The Shopify and WooCommerce connectors are used for search and reading. Amendment stays with a person or with a tool you write.
It does not track the parcel with the courier There is no connector for the Romanian courier firms. It can read the tracking number off the order, but courier status arrives only through your own tool.
It does not identify the caller with certainty A phone number is not authentication. For anything sensitive you need either a verification you build yourself, or a person.
It does not cover platforms with no connector Only Shopify and WooCommerce are ready-made. For a shop on PrestaShop, Magento or something bespoke, an HTTP tool has to be written.

§05 Questions

What shops ask us

Does it find the order if the caller does not know the number?

Yes, it looks the customer up by the number they are calling from and lists their recent orders. If there are several, it asks which one. If the number appears nowhere, it asks for the email address or the order number.

Does it work with my PrestaShop shop?

Not directly. Shopify and WooCommerce are the ready-made ones. For any other platform you write an HTTP tool with a JSON schema over your API, and the flow on this page stays identical. The tools and MCP guide shows how.

Can it take sales calls as well as support?

Yes, but separate assistants with different prompts are worth it, routed on what the caller says at the start. The first-line triage and routing page describes that pattern.

What happens when the customer is angry?

It hands over. The assistant is configured to recognise escalation and transfer without persisting, and the operator receives the context gathered so far. An assistant trying to calm somebody down lengthens the call and makes it worse.

§06 Onward

Notes

1 The tools named on this page are the ones in App\Services\Integrations\ConnectorRegistry carrying implemented. Anything that is only in the catalogue, without that flag, is not named here as though it worked.
2 Order lookup uses find_customer, list_orders and get_order on the Shopify and WooCommerce connectors. The Stripe connector exposes read capabilities only, by design.