Back to case studies

Case study · Flagship engagement

Samleng — AI voice notifications for enterprise logistics.

How an automated native-language calling platform was designed and built to cut a major logistics network's customer-notification cost by roughly 75% — on the order of US$3M a year. The flagship engagement behind Motta Thong's AI systems work, delivered with Ongkrong Consulting.

Public, de-identified version. Client de-identified; no pricing, margins, or stack internals. Figures are engagement design figures, validated pre-rollout. The full named technical version is available to qualified prospects under NDA.

At a glance

Client
One of Southeast Asia's largest logistics and parcel networks (named under NDA)
Sector
Logistics / last-mile parcel delivery
Challenge
A manual, branch-based operation calling customers by hand to announce parcel arrivals
Scope
Discovery → solution design → telecom procurement → financial modelling → cloud architecture → build & load test → rollout plan
Delivery model
AI-native: a lean senior team directing AI agent fleets under human architecture and review
Headline outcome
~75% reduction in notification cost — on the order of US$3M per year
Engineering proof
181/181 automated tests with zero dependency vulnerabilities; outbound dialling layer load-tested to 20,000 concurrent calls
Timeline
~7 weeks from first engagement to a built, validated platform and a contract-ready rollout
Notification cost — manual operation vs. SamlengRelative · designed
Manual calling operation100%
Baseline — millions / year
Samleng managed service~25%
~75%
Cost reduction
~US$3M
Designed saving / year
~7 wks
To contract-ready

Summary

A market-leading logistics network was notifying customers of parcel arrivals entirely by hand — hundreds of branches, a calling workforce in the thousands, hundreds of thousands of calls a day. The cost ran into the millions annually, and an internal attempt to automate it had stalled.

Samleng places parcel-arrival calls in natural, native-language voice, triggered automatically the moment a parcel is scanned at a branch. The design cuts the cost of the operation by roughly 75% — around US$3M a year. The engagement was full-scope: opportunity discovery and business-case construction, a solution scoped against a complete call-flow audit, live telecom procurement to secure a local caller ID, a defensible cost-and-margin model, a documented enterprise cloud architecture, and a production-grade governance package.

Seven phases to contract-ready · rollout on signatureWeeks
Phase
123456789101112
1 · Discovery
2 · Solution & MVP
3 · Telecom procurement
4 · Financial model
5 · Cloud architecture
6 · Deploy & load test
7 · Rollout & governance
On signature · 8–12 wks
Delivered to contract-ready (Weeks 1–7)Begins on contract signature

The approach

  1. 01

    Engagement and discovery

    Rebuilt the cost baseline from the ground up — branch count, staffing, per-agent cost, and a defensible regional loading multiplier — so the business case would survive a CFO's scrutiny. Mapped how the decision would actually be made and where the real competition was: the client's own stalled internal build.

  2. 02

    Solution scoping and MVP

    Scoped an event-driven product: a parcel is scanned, an event reaches the platform, a native-language voice message is rendered and the call is placed within seconds. Scoping included a full end-to-end call-flow audit — a multi-agent review that surfaced 8 critical, 13 high, and 12 medium failure modes, each given a chosen fix before any real customer was dialled. A separate red-team pass triaged 61 issues into a hardening backlog.

  3. 03

    Telecom procurement

    Placing automated calls with a genuine local caller ID is a telecom problem, not a coding one. Ran a live procurement across the call-platform layer and the local carrier market, took a competitive carrier offer to a signed quotation, and designed a multi-vendor path so no single provider owns the whole stack — surfacing the single commercial variable that governs the platform's economics and flagging it for written resolution.

  4. 04

    Cost and financial model

    Built a model designed to survive a CFO and to tell the truth about the economics, running multiple cost scenarios rather than one flattering case. It proved the client's ~75% saving and isolated the one variable that could undermine it — early, while it was still cheap to address.

  5. 05

    Cloud architecture

    Produced an enterprise target architecture documented to an auditable standard: ten formal Architecture Decision Records; service-level objectives engineered to 99.9% while publishing a 99.5% SLA, with a 1-hour RTO and a 5-minute RPO. Validated with the platform vendors' own solution engineers, then pressure-tested through structured review and an independent automated audit.

  6. 06

    Deployment and load test

    The platform passes 181 of 181 automated tests with zero dependency vulnerabilities. The outbound dialling layer was soak-tested to 20,000 concurrent calls — roughly 250× the launch ceiling — at a 99th-percentile latency of 76 milliseconds, with no errors. A reusable load suite was built for every future scale step.

  7. 07

    Production rollout and governance

    The enterprise wrapper is complete and contract-ready: a phased, gated migration plan with explicit go/no-go criteria and a parallel-run period; a 25-item risk register with named owners and mitigations; and a governance layer including a client-facing data-security overview and a pilot security checklist.

Call-flow audit — failure modes found before launch+ 61 red-team issues triaged
P0 · Critical
8
Each received a chosen remediation
P1 · High
13
Prioritised in the hardening backlog
P2 · Medium
12
+ 6 false positives, dismissed
Event-driven call path — scan to dialled callMulti-vendor architecture
BranchParcel scanEvent fires on arrival
SamlengSigned webhookHMAC-SHA256 · idempotent
VoiceNative renderValidated · cached by hash
PlatformCall controlProgrammable dial layer
CarrierLocal originationBYOC trunk · local caller ID
Ongkrong-built / orchestratedVendor service
Engineering proofBuilt & load-tested
20,000Concurrent calls · ≈250× cap
181/181Automated tests passing
76 msp99 call-creation latency
0Dependency vulnerabilities
Risk register — severity-rated, named ownersExcerpt · 7 of 25
IDRisk & mitigationSeverityOwnerStatus
R-01
Carrier bills per call attempt, not on connect
Confirm billing basis in writing before any full-volume commit; secure wholesale rates. A roughly 4× swing in cost of goods — the single variable that governs the platform's economics.
CriticalCommercialOpen · pre-signature
R-02
Answering-machine detection races audio playback
Deferred-playback design — a real person never hears the message start late.
CriticalVoice engResolved
R-03
No local caller ID from a single vendor
Bring-your-own-carrier path over a signed local SIP-trunk quotation secures origination and a genuine local caller ID.
HighTelecomMitigated
R-04
Platform capacity at full daily volume unconfirmed
Vendor solution-engineer confirmation pending in writing; outbound layer soak-tested to 20,000 concurrent.
HighTelecomOpen
R-05
DB-pool / webhook-handler ceiling unmeasured
Throwaway database load test scoped and sequenced; not yet run.
HighPlatform engOpen
R-06
Webhook double-counts a call on carrier retry
HMAC-SHA256 signature plus a deduplication key; ingestion is idempotent.
HighPlatform engResolved
R-07
Client-side signature & rollout delay
Phased paid ramp (first 10–20 branches) keeps the engagement profitable through any delay.
HighEngagementMonitored
OpenResolved / mitigatedMonitored
Showing 7 of 25 · illustrative excerpt

Results

Why it worked

Telecom and commercial risk treated as first-class engineering.

The hardest parts were not the application code — they were the local caller ID, the multi-vendor call economics, and the carrier-billing clause that decides the margin. Handled with the same rigour as the software.

Modelled to find the truth, not to win the room.

The model surfaced the scenario that could lose money and named it the headline risk. Enterprise buyers trust a partner who shows them the downside.

Documented to a standard buyers can audit.

Decision records, explicit SLOs, a named-owner risk register, and an NDA-gated technical review — what serious procurement asks for and rarely gets from a boutique.

AI-native delivery is a force multiplier.

A lean senior team orchestrating AI agent fleets — for build, adversarial review, research, and independent audit, under human direction — reached enterprise depth across software, telecom, finance, and governance.

Capabilities demonstrated

Work with Motta & Ongkrong

Enterprise AI systems built end to end — from the business case and vendor procurement through architecture, build, and governance. If you run a large, recurring, manual operation your team hasn't been able to automate, that is the brief Samleng was built against.

Prepared with Ongkrong Consulting. Client details available to qualified prospects under NDA. Accurate as of June 2026.

MOTTA THONG