WhatsApp nurturing
Conversations,
not broadcasts.
The reply rate on a real WhatsApp message is twenty times higher than email. Rook GTM helps you earn those replies, then keep the thread going.
Hey Ava, saw you signed up for Hloframe yesterday. Want a 10-minute setup walkthrough?
10:14
Yeah actually, send me a link
10:18
Booked: hloframe.com/cal/avr · pick a slot anytime today.
10:18
32%
Reply rate
14m
Time to first reply
100%
Opt-outs honoured
Always
Quiet hours respected
Email teaches you patience. WhatsApp teaches you presence. Rook GTM gives both the same engine.
Mixed-channel sequences
One sequence. Two channels. Real cadence.
Quick intro about Hloframe
Hi Ava, Wanted to share Hloframe. Worth a 10-minute look?
Hey Ava, just nudging on Hloframe. Any questions before we set up a quick call?
One last thing
Sharing how Acme set Hloframe up in 9 minutes. Same path is open for you.
Compliance, by default
STOP works. So do RFC 8058 unsubscribes.
Inbound opt-out
Reply STOP. The campaign stops.
Customer types STOP, UNSUBSCRIBE, REMOVE ME, CANCEL, OPT OUT, END or QUIT. The lead flips to UNSUBSCRIBED. Every active enrollment is paused. The audit log records who and when.
No more chasing the same person across two products because nobody told marketing.
Hey Mia, here's the case study you asked about: hloframe.com/c/acme
11:02
STOP
11:03
Lead unsubscribed
Reason: WhatsApp opt-out keyword.
Active enrollments: stopped.
Visibility
What sent. What landed. What replied.
Provider webhooks land at our doorstep, signed and idempotent. The Inbox flips Sent into Delivered, Delivered into Read, and Read into Replied without you refreshing.
Last 7 days
Provider freedom
Bring your own WhatsApp.
WATI
Production-grade WhatsApp Business API partner. Paste the live-server URL and your access token.
Gupshup
API key plus your registered source number. Webhook URL surfaced post-connect for one-click paste.
Twilio WhatsApp
Sandbox or production sender. Inbound is HMAC-SHA1 verified before any side effect lands.
Old vs new
The old way of nurturing on WhatsApp.
Before Rook GTM
- Sending blasts from a personal account, hoping nobody reports the number.
- No record of who opted out, last week or last quarter.
- Send-now-fix-later. Compliance is a Slack thread, not a system.
- Replies live in three different places. Nobody ever reads them.
With Rook GTM
- Sequenced through a registered Business API provider with templates ready to scale.
- Opt-out keywords detected and honoured the same minute they arrive.
- Quiet hours, allowed days, daily caps, all set in one settings panel.
- Inbox, lead timeline, audit log, all in the same workspace.
Tech specs
What you get out of the box.
- Channels
- Email + WhatsApp in one sequence
- Providers
- WATI, Gupshup, Twilio (more on request)
- Webhook security
- Per-integration secret + Twilio HMAC-SHA1 + idempotency dedupe
- Sending policy
- Per-workspace timezone, quiet hours, day mask, daily cap
- Opt-out
- Keyword detection (STOP/UNSUBSCRIBE/etc) + RFC 8058 email one-click
- Compliance
- GDPR Article 15 export + Article 17 erasure per lead
Make WhatsApp the channel that closes.
Connect your provider. Build your first sequence in five minutes. Send when the time is right.