Concept build: a demonstration project, not client work
A support automation agent for an online retailer. It resolves routine requests within policy and escalates exceptions to staff with full context.
Interface shown with illustrative data.
An online brand's inbox fills with the same questions. Where's my order? Can I change the address? Does this run small? Each answer means three open tabs: orders, shipping and the help center. Around launches and holidays, replies slow down. Staff who should be on the hard cases spend the day pasting tracking numbers.
Parcelhand handles that routine work within firm limits, using retrieval over the help center and catalog. It acts through a few typed tools: find an order, fetch tracking, fix an unshipped address, start a return. Refunds over a set amount wait for a person. When it's unsure, or a customer asks for a human, it opens a ticket for staff.
Escalated tickets arrive with the transcript, order details and the agent's notes. Nobody asks the customer to repeat themselves.
The model can only call typed functions. Each one checks identity and store policy on the server first.
Past transcripts, scrubbed of personal data, get replayed before any prompt or tool change ships.
How a request moves through the system.
01Customer writes in by chat or email
02Agent sorts the request and pulls help articles
03Order requests need an identity check before tools run
04Server-side policy checks approve or block each change
05Routine cases close; the rest become tickets for staff
Next concept build
StandworkManufacturingDescribe your version of the problem. We reply with questions and a proposed approach.