Weeks 1–2 · Diagnostic & channel pilot
Mapped real orders, message templates and exceptions. Activated WhatsApp coexistence and a confirmation flow on one pilot route.

Home Cases Carbón del Sur: orders, routes and confirmations…
Last updated: 2026-11-17
We deployed LogIA to automate order intake, route planning and WhatsApp delivery confirmations on the company's existing number.
Carbón del Sur, distributor (Silla, Valencia).
Carbón del Sur delivers on fixed weekday routes. The day before each run, the team manually messaged a WhatsApp Business broadcast list. About 60% of customers confirmed there; the rest needed one-by-one morning calls. That burned care hours and left gaps when someone did not reply in time.
Orders arrived by phone, WhatsApp and sometimes email. Someone on the shift retyped them. Ambiguous messages («the usual», «a bit more») meant another call. Routes were built from driver experience and Excel — last-minute changes blew up the day plan.
The bottleneck was not «missing software» but three chained frictions: order capture, confirmation on the customer's real channel (WhatsApp), and assignment to route/driver. Without closing that triangle, any fleet app stays half-finished.
We deployed LogIA — Ship Shift's distribution product — on the live operation. WhatsApp coexistence came first (Ship Shift is a Meta Tech Provider): customers keep writing to the number they already know; behind it, an agent structures, validates and leaves an audit trail.
AI does not replace the sales person or the driver: it cuts typing and the call round. Ambiguous messages go to review; a human decides. That kept team trust from the first pilot.
Operational detail mattered too: cut-off times for confirmation, copy in the company's tone, and a board where admin sees who still needs to reply before the truck leaves.
Authorised qualitative outcome: the team stopped hand-building the daily confirmation round and orders enter with less friction between channel and system. Calls concentrate on exceptions, not on the ~40% who never answered the broadcast.
We do not publish invented savings percentages. Value was measured in daily ops: less admin time per route, fewer orders lost to forgotten retyping, and a WhatsApp channel that remains the familiar one for end customers.
In practice the change shows on route morning: less last-minute stress and a shared source of truth between office and driver.
Mapped real orders, message templates and exceptions. Activated WhatsApp coexistence and a confirmation flow on one pilot route.
Wired capture → validated order with a human review queue. Trained admin and tuned rules on recent real messages.
Extended to route planning and the driver app. Phased go-live; improvements driven by incident evidence, not hallway opinions.
Main lesson: in B2B distribution with fixed routes, ROI shows up when confirmation and order live in the same operational thread. Changing the WhatsApp number is often a non-starter; coexistence was a success condition.
It fits if you deliver by zone/day, confirm by phone or broadcast, and still retype orders. It fits less if you already have a mature mobile order ERP and the channel is not the problem.
Tell us routes and channel. We'll say if LogIA or a custom agent fits.