← Back to portfolio

WhatsApp Automation

Transactional notifications, cadence engines and conversational scheduling over the WhatsApp Business API — cutting manual follow-ups by 80%+.

Full-Stack Engineer2023 — 2024
  • WhatsApp Business API
  • GupShup
  • Fastify
  • Node.js
  • PostgreSQL
  • TypeScript
WhatsApp Automation case study cover

Challenge

Operations teams spent hours every day chasing confirmations, reminders and follow-ups by hand over WhatsApp — the channel their customers actually use. It didn't scale, and messages were inconsistent and easy to forget.

Solution

I integrated the WhatsApp Business API (via GupShup) into the platform: templated transactional notifications, a cadence engine that schedules and throttles message sequences, and conversational flows that let customers confirm or reschedule appointments by simply replying. State lives in the platform, so conversations stay in sync with the underlying records.

Overview

WhatsApp is where this market lives, so automating it well removed the single biggest source of manual work for operations teams — without making the channel feel robotic.

How it works

  • Transactional templates — approved WhatsApp templates fire on lifecycle events (bookings, payments, reminders) through GupShup.
  • Cadence engine — sequences are scheduled, throttled and de-duplicated, so customers get the right nudge at the right time and never a flood.
  • Conversational flows — inbound replies are parsed into intents (confirm, reschedule, cancel) and reconciled back into the platform’s records in real time.

Outcome

Follow-ups that used to eat hours of manual work now happen on their own, reliably, in the channel customers already prefer.

Impact

  • Reduced manual follow-ups by 80%+
  • Templated transactional notifications at scale
  • Cadence engine for scheduled, throttled message sequences
  • Conversational scheduling — confirm or reschedule by reply
  • Message state synced with platform records