Cut "where's my shipment?" tickets by 36% — without replacing your logistics system.
If you run a logistics, courier, freight or 3PL operation, you know the daily grind: customers messaging, calling and emailing for tracking status — every hour, all day, every day. FASTCO Oman (OHI Group's logistics arm — express delivery, air/sea freight, customs clearance, oil & gas logistics) solved it. Customers now self-serve on WhatsApp. Tracking status comes straight from FASTCO's own system via API. Support tickets down 36%. And their operational platform never had to change.
Integrated logistics · Express & last-mile · Air & sea freight · Oil & gas · Warehousing · Oman
Sound familiar?
- Your customer service team spends most of their day answering "where is my shipment?" — the same question, over and over, all channels.
- Agents copy-paste tracking status from your logistics platform into WhatsApp / email — slow, error-prone, and it doesn't scale on peak days.
- Customers ping you outside office hours. Nobody answers. Complaint gets loud on Monday.
- Oil & gas or project-cargo customers need urgent status. Your team scrambles to pull it from the system while the customer waits on the phone.
- A route delay hits — you need to notify 500 affected customers in the next 30 minutes. Right now that's a manual, one-by-one job.
- You already invested heavily in your logistics platform (SAP, Oracle, custom TMS, whatever). You don't want to replace it — you want customers to reach it, safely, without giving them a login.
If any two of these sound like your operation, the setup below is the pattern to copy. FASTCO Oman runs an integrated logistics business with these exact constraints. Here's what they built.
Challenge
- Customers needed shipment status at any hour — inquiries, tracking checks, delivery updates — and were fragmenting across phone, email and WhatsApp.
- FASTCO already had its own operational platform for customer requests, shipments, tracking references and status. Replacing it was not an option.
- Tracking information had to come from FASTCO's system — not be manually re-entered by an agent.
- Workflows had to be configurable by request type (tracking vs. inquiry vs. delivery update).
- The business needed to push structured operational updates and broadcast announcements at scale.
- Data ownership and control of the operational systems had to stay with FASTCO.
Solution
- Go4whatsup was wired to FASTCO's existing logistics platform via developer APIs and webhooks — no parallel logistics database, no duplication.
- Two-layer model: FASTCO's platform stays system of record for shipments, tracking references, customer data, operational events. Go4whatsup is the customer-facing WhatsApp workflow + communication layer.
- Guided WhatsApp workflow: customer opens the chat, selects the intent (Track Shipment / Make an Inquiry / Receive an Update / other), and Go4whatsup routes to the right flow.
- For tracking: customer supplies the tracking ID → Go4whatsup calls FASTCO's system via API → current status is retrieved → response returned inside WhatsApp.
- Event-driven notifications: when a status change happens in FASTCO's system, a webhook fires and Go4whatsup pushes the approved template to the customer automatically.
- Custom template library: FASTCO controls its own message content for shipment updates, service notices and operational announcements — no code changes needed.
- Broadcasting: for route delays, holiday schedules or service updates, FASTCO can reach whole customer segments through approved WhatsApp templates in minutes.
- Controlled integration: only the data required for a particular workflow is exchanged — not FASTCO's full operational database.
Capabilities delivered
- -36% WISMO ("where is my shipment?") support tickets — customers now self-serve tracking on WhatsApp, freeing the support team for exceptions.
- 24/7 self-service tracking — no agent needed for the everyday "just checking status" question.
- Tracking status always current — pulled live from FASTCO's own system, not a cached copy.
- Proactive updates — event-driven notifications flow to customers automatically as shipments move.
- Bulk announcements — route delays, service changes and operational updates broadcast in minutes, not hours.
- Consistent messaging — approved templates replace ad-hoc agent drafts.
- Operational system untouched — FASTCO's logistics platform stayed source of truth. Zero risk to core operations.
- Foundation for expansion — new workflows (pickup requests, documentation, quote requests) can be added on top of the same API/webhook layer.
The self-service tracking journey — one connected chain.
Customer starts a WhatsApp conversation with FASTCO's business number.
Go4whatsup presents the guided menu: Track Shipment, Make an Inquiry, Receive an Update, or other configured options.
Customer selects "Track Shipment" and the workflow requests the tracking ID.
Go4whatsup calls FASTCO's logistics platform via the integrated API with the tracking ID.
FASTCO's system validates the request and returns the current shipment status.
The status is delivered back to the customer inside WhatsApp — instantly, no agent involved.
When the shipment status changes in FASTCO's system, a webhook fires and Go4whatsup pushes the update to the customer automatically.
For service-wide announcements — a route delay, a holiday closure — FASTCO broadcasts via approved WhatsApp templates to affected segments.
FASTCO's integrated logistics operation — express delivery, freight, customs clearance, warehousing, oil & gas — runs on its own platform, and that platform stays canonical. Go4whatsup was wired in via developer APIs and webhooks so customers can self-serve their tracking questions on WhatsApp, and FASTCO's system pushes proactive updates without a human in the loop. The support team keeps its focus on exceptions and high-value inquiries.
What powered the story.
Want the same setup on your logistics system? Ship in one working week.
FASTCO's WhatsApp layer talks to their logistics platform without a separate database. Bring your existing system on the demo call — we'll show you the API + webhook flow using your own tracking references.