Cookiebees

WhatsApp & email

Messages that know
who they are talking to.

An inbox tied to the customer record, templates and flows built in the product, sequences that stop the moment someone replies, and email from your own domain. Every send credited, every reply a signal.

Questions this answers

  • Can my team run WhatsApp from the CRM, not another app?
  • Can I build and publish templates without Business Manager?
  • Do sequences stop when someone replies?
  • Does a WhatsApp reply teach Meta anything?

The inbox

Two-way WhatsApp, tied to the person.

One-click Connect through Meta’s Embedded Signup. A shared inbox with per-line tabs and agent assignment, the 24-hour window respected, delivery state on every message. A chat that starts from a button on your website carries its campaign like any form fill.

  • Multiple numbers under one account, per-line tabs
  • Click-to-WhatsApp ads attributed by ctwa_clid
  • Quick replies and free-form media inside the window
  • A warning before Meta’s 60-day token disconnects you
whatsapp · inbox

Template → publish to Meta

Hi {{1}}, your call is booked for {{2}}. Reply here if you need to reschedule.

UTILITY Approved
Built in the CRM · published to Meta for approval
Hi {{name}}, your call is booked for Thu 4 PM 👍
Perfect, see you then!
Here’s your payment link to confirm 🔗
Message the lead…

Templates, broadcasts, flows

Built in the product. Published to Meta. Sent to a segment.

Text, image, video, document and carousel templates, read before submitting, with a Used-in map and dynamic URL buttons. Broadcasts to a whole segment, throttled and opt-out aware, with a live per-recipient delivery report. A stateful flow builder for the bot: menus, ask-and-save, media, timed waits, hand-off.

  • Media-header templates and carousels
  • Broadcasts with per-recipient delivery state
  • A visual flow builder that runs before the workflow event
  • Usage and cost per category, so the bill is never a surprise
Signals · engagementserver-side

You sent

Email campaign
WhatsApp template
what they did with it

Opened the email

→

EmailOpened

email

Clicked a link inside it

→

EmailLinkClicked

email

Replied on WhatsApp

→

WhatsAppReplied

business_messaging

Tapped a tracked link

→

LinkClicked

website

Four more reasons for Meta to keep this person in your audience - and four more things its bidding now knows about who actually engages.

Real actions only. No value is ever attached - engagement is not revenue, and a faked page view would corrupt both.

Sequences

Timed cadences that end the moment someone replies.

Multi-step WhatsApp and email cadences with exit conditions re-checked at send time, not at trigger time. Enrol a segment or a CSV. Comms pause per lead stops every automated send while manual ones still work. Sequential workflows by priority, with your own stage labels.

  • Exit on reply, exit conditions at send time
  • Bulk email campaigns to a cohort
  • Workflow ordering by priority
  • A reactivation template in the builder
Pipelinesource travels with the card
New

₹42,000

Meta

₹18,500

Google

₹64,000

Referral
Qualified
Won
Every stage change is a signal you can send back - so the ad platform learns which leads were actually worth having.

Email

From your own domain. Opens and clicks taught back to the ad platforms.

Every automated email sends through your SMTP or ZeptoMail, with open and click tracking, an unsubscribe that works, and a footer that answers objections. Store emails by moment. Klaviyo syncs natively. Every open and click goes to Meta as a real engagement event.

  • Own SMTP, with a check that your domain authorises the server
  • Store emails: abandoned, won back, reorder, and more
  • Klaviyo audience sync by API key
  • Opens and clicks as EmailOpened and EmailLinkClicked
Event stream · purchase payload

What came in

email

the shopper typed it

phone

from checkout

address

city, zip, country

click id

captured on landing

→

What we sent

em

a1f4…9c02

ph

7be1…44d8

ct / zp / country

3d90…b7e1

fbc / gclid

passed through raw

external_id

stable per customer

Match quality

0/10

Nothing leaves as plain text. Every identifier is SHA-256 hashed first.

Inside the module

Inside Messaging

Every message is measured because it is sent to a resolved person.

WA Inbox

Per-line tabs, assignment, delivery state

WA Broadcast

Approved templates to a segment

Templates

WhatsApp, flows, workflow emails, store emails, system emails

Sequences

Timed, multi-step, exit on reply

Automations

Workflows, scoring, forms, popups, chat

Engagement signals

Opens, clicks, replies, taps, as real events

The WhatsApp carousel on the homepage is the one the recovery playbook actually sends.

Run WhatsApp from the record

One inbox.Every send credited.

Connect WhatsApp in one click, build the first template in the product, and send it to a segment that already knows who it is.