Skip to content
← All results

Case study / Dubai-based forex broker / 2026

Customer follow-up, rebuilt around a dependable schedule.

Four automated customer journeys across WhatsApp and email, running unattended every two hours with per-message delivery tracking.

Email delivery
99.6%
Email delivery
Reported campaigns
21
Reported campaigns
Customer journeys
04
Customer journeys

Reported 27-day window · 1,123 / 1,127 emails delivered · Client identity withheld

01 / What changed

From activity without a record to a system you can inspect.

Before

Manual follow-up. Unpredictable scheduling. No clear distinction between a failed send and a message that never ran.

After

A scheduled journey with suppression checks, controlled dispatch and a recorded result for each eligible step.

02 / How it works

Every branch has a reason.

Multi-channel lifecycle engine

Identifiers, endpoints and customer data removed.

03 / The decisions

Reliability lives in the details.

  1. 01

    Rebuilt the scheduler around a fixed two-hour window with explicit day-offset routing, replacing the cadence logic that had been misfiring

  2. 02

    Joined every send against a suppression list and an already-sent ledger before dispatch, so a retry can never double-message a customer

  3. 03

    Throttled dispatch to one message at a time with a fixed delay, keeping the send rate under the provider's frequency ceiling

  4. 04

    Logged failures as a first-class path — every rejection stored with its provider error code, not collapsed into a generic error

04 / What it changed

  • n8n
  • MySQL
  • WhatsApp Cloud API
  • SendGrid
  • GCP
  • Docker
  • 99.6% email delivery across the measured window (1,123 of 1,127)

  • Throughput grew roughly 18× in four weeks while the failure rate fell from 28% to 2%

  • Every failure is now attributable to a specific cause — provider frequency capping accounts for the majority, which is a tuning problem rather than a defect

  • 21 campaigns run across four lifecycle journeys with no manual intervention

What the evidence shows

Delivery and throughput describe operational behaviour. They do not establish incremental sales. Measurement definitions and channel scope stay attached to the result.

Your next chapter

Does follow-up lose consistency as your volume grows?

Bring one process, one bottleneck or one growth goal. Let’s find a useful next step.

Book a strategy call