Where it breaks today
Support volume is mostly the same four questions
Where is my order, sent by email, answered by a person, twelve hours later.
Abandoned carts chased by email nobody opens, with no way to reply and ask a question.
Returns start in a web form, continue by email and end in a phone call with no shared history.
Delivery reschedules go through the carrier, so you find out about the failure from the customer.
How whtapis runs it
What this team gets
Order lookup
Live status, carrier scans and delivery windows pulled from the ERP at the moment of asking.
Catalogue and cart
Product cards, variants and checkout links inside the conversation.
Returns and refunds
Guided return flow with label generation and refund status updates.
Cart recovery
Timed WhatsApp reminders with a reply path to a human, not a dead-end email.
Delivery rescheduling
Customer picks a new window, the carrier and the ERP are both updated.
Peak handling
Queue overflow, AI-first routing and campaign throttling for sale periods.
Service
Contacts per order and response time
Commerce
Cart recovery rate and reorder rate
Cost
Share of contacts resolved without an agent
The measures the platform reports on. Targets are set with you during onboarding.
The team using it
Customer care, warehouse and store.
Order questions touch three teams. One thread keeps them all looking at the same answer.
Placeholder frames — drop your own photographs in.
Other use cases