E-commerce Order-Status Support Agent

In retail and e-commerce support, 'where is my order' is one of the most common questions, and it spikes whenever a carrier misses a sort or a hub backs up. Support staff answering by hand switch between the order system, carrier tracking and the notification log to piece together one reply. This Botlit concept shows an order-status agent, linked to a customer support bot, that looks those records up itself, answers with the latest tracking event and revised estimate, cites what it read, and knows which requests belong to a person.

The illustration shows the Conversations view of a sample Customer Support Bot with its Order Status Agent open, badged active, on web chat and with a tools count. A shopper writes that an order has not moved since Monday. The reply explains that the parcel is at a regional sort hub because the carrier missed a sort, gives a new estimated date, confirms a delay notice already went out that morning and promises a message when the parcel is out for delivery. Two citations name the Kadaikodi order and the MoveTheWheels shipment, marked delayed. When the shopper asks for a refund instead, the agent passes the conversation to a teammate who can see the order and the delay, tagged as handed off to the refunds queue.

A Tool calls this turn panel lists each call with its record, latency and result: a Kadaikodi order lookup returning OK, a MoveTheWheels shipment lookup returning Delayed, a MoveTheWheels exceptions list for the affected hub with a shipment count, and a FluidGrids delay notice run showing when notices were sent and how many. An Escalation rules card sends refund requests to the refunds queue, damaged items to claims and exceptions older than 48 hours to a team lead, and a Today card counts order-status chats, conversations handed to a person and delay notices sent.

The design divides the job among four Burdenoff products. Kadaikodi holds the order and MoveTheWheels the shipment, and the agent is designed to call tools against both and to check whether FluidGrids has already notified the shopper before it replies. A FluidGrids workflow is designed to send proactive delay notices from the MoveTheWheels exception list, as well as the out-for-delivery message the agent promises, so Botlit handles only the questions that still come in. The concept is aimed at e-commerce support leads, customer service teams and the operations staff who watch delivery exceptions.