AI handles 79.7% of forwarding inquiries
A parcel forwarding and shopping service with warehouses in Canada and Japan. The AI looks up, edits and creates shipment requests, calculates shipping fees and tracks parcels through the order API.
The challenge
What changed with Cliptalk
Work the AI handles directly through the API
It calls the customer’s API for live data, asks the end customer to confirm, then writes the change straight into the system.
Automation in action
Recreations of real production conversations.
Splitting a lottery-prize order into English line items
The customer pastes the Japanese prize names; the AI turns them into customs-ready English items, splits the price and updates the request. One “Yes” writes it to the order system.
GET /customers/:seq/shipmentsPOST /shipments/:id/modifyOne screenshot: new request filed, shipping fee quoted
From a store’s order confirmation, the AI reads the item, price and tracking number, files the request with the saved recipient, then quotes the shipping fee for the customer’s tier.
GET /customers/:seq/shipment-defaultsPOST /customers/:seq/shipmentsPOST /calculate-feeWarehouse checks go to an agent with the lookup attached
When a parcel shows as delivered locally but hasn’t been received, the AI checks tracking and arrival records first, then hands off. The agent only has to check the warehouse.
GET /shipments/:id/trackingPOST /notify-handoffGET /agent/shipmentsAutomation flow
How much work the AI takes over
Calculated from real production chat logs. Only conversations with at least one customer message are counted.
Workload = Σ(AI replies ÷ all replies in each conversation) ÷ number of conversations