customer_support · logistics · workflow
Stuart gains 88 hours per week and handles 90 chats per hour with Intercom across logistics support and engagement
Stuart was relying on email and SMS to communicate with clients and couriers at scale, but these channels were too slow and impersonal for time-sensitive logistics like food delivery, and could not support the company's rapid growth across Europe.
How it works
Common implementation structure
How this type of workflow is generally built, generalized across documented cases — not tied to any one vendor's stack. Click any stage to read what happens there. Specific products that implement these stages appear in “Tools commonly seen” below.
Stage 1 · Query received via Intercom
Tens of thousands of chats are received every week through Intercom.
Tools used
IntercomCustom BotsProduct Tours
Outcome
Stuart gained over 88 hours of team time back every week, enabled agents to handle up to 90 chats per hour, automated 70% of customer queries via bots in a pharmacy test, achieved over 60% goal completion on engagement campaigns, and onboarded over 17,000 users via Product Tours.
What failed first
Email and Zendesk were inadequate for Stuart's fast-paced logistics support needs — email was the wrong channel for food-delivery urgency, and Zendesk could not handle the scale or speed required as the user base expanded.
Results
Time savedover 88 hours per week
Volumeup to 90 chats per hour
Cost replacedsaving significant monthly costs
Grounding & classification
Source type: vendor customer story
35 fields verified against source quotes.
chatbotchat transcriptknowledge basehuman review describedmetric backednamed customerproduction runtime claimedsource backedtools describedworkflow describedlogisticsautomation ratecost reductiondeflection rateemployee productivitythroughput increasetime savedvendor customer storycustomer supportlogistics opsmarketing opsticket triageautonomous resolutionextract classify routeintake to triage