Logistics
Predictive Fleet Analytics Platform for Mer**** Logistics, Midlands UK
Delivered in approximately four months with a small dedicated team.
Delivered in under three months by a small dedicated team.
Project Highlights
Scalable Architecture
Built for growth — Fixed Price designed to scale
Secure & Compliant
Enterprise-grade security and data protection standards
Measurable ROI
Four agents answering repetitive order queries → Assistant resolving over half of conversations bilingually
United Arab Emirates Delivery
Delivered for a United Arab Emirates-based E-commerce client
Tech Stack
Industry
E-commerce
Sector
Online Fashion & Homeware Retail
Region
United Arab Emirates
Project Type
Fixed Price
This project was delivered under a Non-Disclosure Agreement. The client operates in the E-commerce sector (Online Fashion & Homeware Retail) and is based in United Arab Emirates.
The large majority of incoming messages were variations of 'where is my order', which meant experienced agents spent their day copying tracking numbers instead of resolving genuine problems. The language requirement was the hard part: customers wrote in English, in Modern Standard Arabic, in Gulf dialect, and very often in a mix of the two within a single message, sometimes using Arabic written in Latin characters. Off-the-shelf intent models handled English acceptably and Gulf dialect badly. There was also a trust constraint — the client was clear that a bot which trapped customers in a loop would damage the brand more than slow replies did, so escalation had to be fast and obvious. On the technical side, the order data lived in the ecommerce platform with no clean API for status lookups, and WhatsApp's Business API imposes strict rules on what can be sent outside a 24-hour customer service window, which shaped what the assistant could proactively do.
Four agents answering repetitive order queries
Assistant resolving over half of conversations bilingually
We built the assistant as a Node.js service handling WhatsApp Business API webhooks, with a separate Python service doing intent classification and entity extraction. Rather than relying on a single multilingual model, we trained intent classification on the client's own historical WhatsApp transcripts, which is what made Gulf dialect and mixed-script messages work — the training data reflected how their actual customers write, not how a generic corpus does. Order lookups run against a small integration layer we built over the ecommerce platform, caching status in MongoDB so a lookup does not hit the store on every message. The assistant handles order status, delivery timelines, returns initiation and basic product availability; anything else, or any message where intent confidence falls below threshold, hands off to a human agent with the full conversation context attached. We deliberately made the handoff a single step rather than a menu tree. Arabic responses were written by a native speaker rather than machine translated, because a bot that replies in stilted Arabic reads as a foreign company. Message templates were pre-approved through WhatsApp's process to allow proactive shipping notifications within policy. We also built a small agent console in React so supervisors can watch live conversations, review what the assistant handled overnight, and correct misclassified intents directly — those corrections feed the next retraining cycle rather than sitting in a ticket queue. Related: AI & ML development and our ecommerce practice.
Delivered in under three months by a small dedicated team. The assistant now resolves a substantial share of incoming conversations without human involvement, concentrated almost entirely in order-status and delivery-timeline queries — the categories that were consuming the team. Median first response during busy periods dropped from tens of minutes to near-instant for handled intents. The support team was not reduced; they moved onto returns handling and pre-sales questions, which the client considers higher value. Arabic-language conversations now resolve at a similar rate to English ones, which was not true of the earlier generic chatbot they had trialled. The client has since expanded the assistant to handle exchange requests, which was the next-largest query category once order status stopped dominating the queue.
Transformation Summary
Four agents answering repetitive order queries → Assistant resolving over half of conversations bilingually
This project was delivered under a Non-Disclosure Agreement (NDA). Specific client details, business data, proprietary workflows, and project credentials remain confidential. Screenshots and live URLs are available upon mutual NDA execution.
Request an NDA to see full detailsMost bot failures are escalation failures rather than language failures — customers do not mind a bot, they mind being trapped by one. Escalation here is a single step, triggers automatically when intent confidence is low, and passes the full conversation to the agent so the customer never repeats themselves.
Let's discuss your project and create a success story together.
Logistics
Delivered in approximately four months with a small dedicated team.
Manufacturing
Delivered in approximately three months with a small dedicated team.
Financial Services
Delivered over approximately five months with a small dedicated team, including the supervised pilot period.