WhatsApp lead agent on the Meta Cloud API
Verifies every message came from Meta, reads it, answers, books, hands complaints to a human and follows up inside the 24 hour rule.
The problem it solves
Leads that arrive on WhatsApp after hours get answered the next morning, by which time a good share have bought from whoever replied first. A bot that answers everything is worse: it books wrong slots, argues with complaints and keeps messaging people who said stop.
What it does
- Verifies the X-Hub-Signature-256 on the raw request and answers a forged request with a 401.
- Ignores duplicate deliveries by message id and keeps the conversation in memory so the second message is read in context.
- An AI step returns intent, language, lead score and a reply. Pricing and greetings get an instant answer.
- A booking request gets three real calendar slots and a CRM task with a 15 minute deadline.
- A complaint pauses the AI for that chat, alerts the team on Slack and creates a callback task. STOP tags the contact as opted out.
- An hourly branch nudges quiet conversations: free text inside 24 hours, an approved template outside it.
How it was tested
- 14 scripted events: handshake, wrong token, greeting, pricing, booking, Roman Urdu, complaint, message during handoff, duplicate delivery, status update, forged signature, STOP, 30 hour old message, follow up sweep.
- All 14 passed; 9 WhatsApp sends, 2 refusals, 1 template.
Screens
Who it is for
Clinics, real estate, home services, trading companies where WhatsApp is where leads land.
See it running on a call → hamza.jamal@finamatik.com
Built and tested on sample data before any live credential is connected. Every system Finamatik ships is adapted to the client's own tools and owned by the client outright.