Embedding tracking into agent interface
Brian Whalley, Co-Founder of Wonderment, on Klaviyo's product-market fit
Embedding tracking data inside the help desk turned shipping status from a manual lookup into a native support workflow. Instead of an agent opening a WISMO ticket, clicking out to a carrier page, interpreting the status, and then replying, the shipping facts appeared in the same screen where the reply was written. That small UI change matters because SMB ecommerce teams often have only one or two reps, so every extra click makes the biggest ticket category slower and more expensive.
-
The broader pattern is the same one that made Klaviyo work. Pull fragmented customer data into the system where work already happens, then make it usable without spreadsheets or tab hopping. Klaviyo did that for segmentation in marketing, Wonderment did it for shipping support inside Gorgias or Zendesk.
-
Wonderment extended beyond showing status. It auto created tickets for return to sender, delivery errors, and fulfillment delays, giving brands a four to five day head start before the customer complained or the box physically came back to the warehouse.
-
This sits inside a larger support stack shift where the help desk is becoming a system of record with more automation layered on top. Gorgias reached $69M ARR in 2024, and newer AI support products are pushing even more value into the agent interface by resolving or routing work from the same screen.
The next step is for the interface to move from showing shipping context to acting on it automatically. Help desks will generate the ticket, draft the message, trigger the reship or refund workflow, and escalate only the edge cases, which makes post purchase operations look less like inbox management and more like exception handling on top of live logistics data.