Both tickets below are invented, built to show the two ends of the triage range: something safe to draft-and-hold for approval, and something urgent enough that only a person should send it. A real build sorts a business's actual incoming messages this way, using their own products, policies and reply-time standards.
Drafted, held for approval
What arrived
"I ordered nine days ago and the tracking still says label created. Can someone tell me what's going on?"
Drafted reply, waiting for a person to send
Hi there,
Thanks for flagging this, and I'm sorry for the wait. Your order shipped with a label created 9 days ago, but tracking shows no scan since. I've asked our fulfillment team to check whether it's still with us or was handed to the carrier without being scanned in, and you'll hear back by [date] either way.
[Name]
Held rather than auto-sent because the honest next step (checking with fulfillment) isn't something the system can actually confirm on its own.
Safe to auto-send
What arrived
"Just checking, has order #4471 shipped yet?"
Drafted reply
Hi there,
Order #4471 shipped on [date] via [carrier], tracking number [number]. Expected delivery is [date].
[Name]
Safe to send automatically because the answer is a direct lookup, not a judgment call.
How this gets built for real
Real tickets, real products. A real build reads a business's actual incoming messages and drafts against their real order data, policies, and product names, not invented ones.
The urgency sorting is the point, not the drafting. Anything ambiguous, emotional, or where the honest answer isn't a simple lookup gets held for a person. Only clean, verifiable answers go out unattended.
See it built for a real business: Jewelry Candles.