- Item
- Pinecrest 2-person tent
- Last scan
- UPS, Salt Lake City, UT, 6:40 AM
- Expected
- Thu, Oct 8
- Order email
- Matches
Goes to your team: Marked delivered but not at the door? The lost or damaged rule sends that chat to Sam K.
Risolva's order tracking chatbot asks for the order number and checkout email, looks the order up in your system, and replies with the carrier, last scan and delivery date on WhatsApp, Instagram, Messenger or web chat. Lost packages and refunds go to the person your rules name.
Goes to your team: Marked delivered but not at the door? The lost or damaged rule sends that chat to Sam K.
Most stores email a tracking link the moment a label prints, and customers write in anyway because they want someone to tell them it's fine. Each reply means opening the order, opening the carrier page and typing the last scan back into chat. The volume climbs after every sale, holiday cutoff and weather delay, which is exactly when the team has the least time.
Peak & Pine Outdoor sells tents, boots and packs and ships with UPS and USPS. Each answer below comes from a live lookup in its order system, which is what keeps WISMO automation accurate when an order is split, late or not yet packed.
Goes to your team: If Tyler would rather cancel the tent, that goes to your team unless you've also connected a cancel action.
Goes to your team: If Rachel's next message reads as frustrated or angry, the rule "Upset customers go to Leah" routes the chat to Leah W. before the AI replies again, and Rachel gets the handoff message written for that rule.
Goes to your team: If the order has already shipped, the change goes to your team, who can ask UPS or USPS about rerouting it.
Each Peak & Pine rule names whoever can act on that kind of order problem. Sam files carrier claims, the billing team approves refunds, Leah takes anyone who is upset, and customer care writes to VIPs about late orders. Routine status checks never reach them, because the order lookup already answers those.
Topic is Lost or damaged packageSam files the UPS or USPS claim and sends a replacement tent or pack, which the AI has no way to do.
Sentiment is frustrated or angryA tent that won't arrive before a trip calls for an apology and a decision from a person, not another status update.
Topic is RefundsRefunds need someone who can approve them in the payment system, and keeping return-policy questions under a separate Returns topic lets the AI keep answering those.
Customer is VIP and topic is Late deliveryCustomers you've flagged as VIP hear from a person about a late order, even when they ask politely.
An order status chatbot is only as good as the lookup behind it. There's no ready-made Shopify or order-system integration, so lookups run through a custom action that calls your own API.
Your order system, or the store platform it runs on, needs an API call that takes an order number and returns the status, carrier, tracking number, last scan and expected date. Include item-level status if you can, so split and backordered orders get explained properly.
Make the order email or phone a required field on the action, and have your endpoint return nothing unless it matches the order. For extra caution, a separate verification action can be required to succeed first. The Signed-in user only setting goes further: the lookup then runs only for web chat visitors your site has signed in, and not on WhatsApp, Instagram or Messenger.
Add your shipping policy, UPS and USPS delivery times and your 30-day returns page as knowledge. They cover what no lookup answers, like whether you ship to Canada or how to send back boots that don't fit.
Someone on your side with API access works through it with the Risolva team during onboarding. Together you set up the lookup, plus an update_address action if your system supports one, and run test calls with a few real order numbers before customers see it.
Most stores already send a tracking link. Customers still write in, usually because the carrier page shows a scan code and not an answer.
| Compared on | Tracking page plus email | Risolva |
|---|---|---|
| Where customers ask | Find the shipping email, open the carrier page, paste in the tracking number | Ask in WhatsApp, Instagram, Messenger or your site chat, in their own words |
| Split and backordered orders | One tracking number per email, and nothing about the item that hasn't shipped | Explains each item on the order, if your lookup returns item-level status |
| Carrier delays | An exception like "weather delay" with no next step | The reason and the new estimate in plain words, and a person if the customer is upset |
| Changing the address | The customer emails support and hopes the label hasn't printed | Collects the new address and runs your update action once the customer confirms |
| What reaches your team | Every email the tracking page didn't settle, in arrival order | Lost packages, refunds and upset customers, each routed by your rules |
An order tracking chatbot answers "where is my order" messages in chat. In Risolva, the AI looks up the order in your own system through a custom action and replies with the status, carrier and expected delivery date, on WhatsApp, Instagram, Messenger or your website chat. Questions it shouldn't handle go to your team.
We'll show how a lookup against your order system would answer them, which shipping questions your pages already cover, and which order problems your rules should send to a person.