View all app connections
View all AI automations
View all chatbots
View all lead automations
View all booking automations
View all payment automations
View all workflows
View all Shopify
View all WooCommerce
View all HubSpot
View all Salesforce
View all Stripe
View all Google Sheets
View all Slack
View all dental practice
View all law firm
View all medical practice
View all real estate
View all restaurant and food
View all home services
View all construction
See all: get more leads
See all: get paid faster
See all: save admin time
See all: support customers
See all: book more appointments
See all: sell more online
See all: hire and onboard
View all AI automations
View all AI automations
View all AI automations
View all AI automations
View all AI automations
View all AI automations
View all AI automations

Crisp WhatsApp automation for teams that follow up where customers already chat

Crisp to WhatsApp automation that sends follow-ups only to people who opted in, choosing a reply or an approved template by the 24-hour window

WhatsApp lets a business answer freely only within 24 hours of the customer's last message, and after that only an approved template can start a conversation. BoldBellows looks up the consent held for the phone number and notes the session it came from, checks the 24-hour window before it chooses between a reply and an approved template, then designs the Crisp to WhatsApp route around three checks before any send: is there consent for this number, is the number in international format, and is a free-form reply allowed or must a template be used. The result is a Crisp WhatsApp follow-up message that is wanted, correctly worded and recorded with its delivery state.

View Pricing

From $710, paid once. Connect Crisp to WhatsApp.

  • Connect Crisp to WhatsApp
  • Consent checked before each send
  • Reply or template by the 24-hour window
A Crisp chat followed up on WhatsApp only where consent is recorded, as a reply or an approved template, built by BoldBellows

What Crisp to WhatsApp needs to show before launch

  • Consent firstno recorded opt-in, no message
  • Window checkeda reply inside 24 hours, a template outside it
  • Number validatedinternational format before every send
  • Delivery recordedsent, delivered, read or failed is saved on the chat
  • Honest reportingFailed runs are reported with their cause, not hidden
  • Fixed scope, fixed fee$710 opens the build, and every extra is priced on the page

B2Before and after

A message to every number is how a business gets blocked

Crisp holds a phone number in the visitor's profile whenever one was shared, and it is tempting to message all of them. A person who gave a number for a delivery did not agree to marketing, a message outside the 24-hour window is rejected unless it is an approved template, and a number typed with spaces or no country code simply fails. The team learns about all of it from complaints, not from a record.

Sound familiar?

A message nobody agreed to

Consent was never recorded.

A free-form message rejected

The window had closed.

A number that failed

It had no country code.

The same follow-up twice

A redelivered event sent again.

A template mismatch

Wording differed from the approved text.

Delivery unknown

Nobody saved the status.

Crisp chats followed up on WhatsApp, with permission

Before

Before Crisp to WhatsApp automation: manual conversations exports, duplicates and broken formulasThe old way: a spreadsheet with a duplicated conversation, #N/A and #REF! errors and a note asking which row is right.conversations (2).csvreassignments v3.csvconversations_export_FINAL_v3.xlsxConversationCustomerClosedStatus#1048Maya Chen9Resolved#1049Omar Hale14Resolved#1049Omar Hale14Duplicate#1050Lena Brooks#N/AResolved#1051Sam Ortiz21#REF!Which row isthe right one?
  • Each notice is trusted as it stands
  • Every number in Crisp can be messaged
  • Nobody knows whether a message arrived

After

After Crisp to WhatsApp automation: one clean number that matches CrispThe new way: a five-week calendar grid coloured by daily net chat volume, from low to high.Closed chat volume by dayLast 5 weeksMTWTFSS9k13k13k14k18k15k19k19k16k16k20k16kLowHighUpdated live
  • Matching uses the website ID, session ID and WhatsApp message ID; titles and labels are ignored
  • Only people with recorded consent are messaged
  • Each send keeps its window, template and delivery state

D4How it works

How a Crisp chat becomes a welcome follow-up on WhatsApp

The sequence is fixed so that a replay reaches the same answer every time.

How Crisp to WhatsApp automation works: conversations in, one clean conversation each, on a scheduleYour Crisp workspace sends data through a read-only link to the BoldBellows sync, which removes duplicates and handles reassignments, then fills your WhatsApp on your schedule.Your CrispworkspaceConversations,visitors,ConversationsInboxReassignmentsBoldBellows syncReads only, writes onceNo duplicate conversationsEdits and reassignments updateYour time zone and settingsYour WhatsApp BusinessnumberTemplates,reports and aRead-onlyYour scheduleHow Crisp to WhatsApp automation works: conversations in, one clean conversation each, on a schedule, stacked: your workspace, the BoldBellows sync, then your WhatsApp Business number.Your Crisp workspaceConversations, visitors,operatorsConversationsInboxReassignmentsBoldBellows syncReads only, writes onceNo duplicate conversationsEdits and reassignments updateYour time zone and settingsYour WhatsApp BusinessnumberTemplates, reports and adashboardRead-onlyYour schedule

1. Filter at the door

The Crisp event is authenticated and recorded first; only a chat event that matches the rule continues.

2. Check, choose, validate

Consent is looked up, the 24-hour window decides between a reply and a template, and the number is put into international format.

3. Send, record, follow

The message is sent once, its delivery state is recorded on the chat, and a failed send is reported to the operator.

E5Inside your number

What the WhatsApp route contains: consent, window, record

Each layer adds one job: Kickoff decides, Build-out delivers, Review verifies.

What lands in your number: conversations, templates and reports from CrispWhatsApp split view: raw conversations scroll in on one template while a summary template fills itself with totals and a trend line.ConversationsSummaryConversationCustomerClosed#1053Kai P.6#1054Zoe L.14#1055Ben R.3#1056Ada M.10#1057Noah S.7#1058Eva T.21#1059Liam D.4#1060Mia K.9#1053Kai P.6#1054Zoe L.14#1055Ben R.3#1056Ada M.10#1057Noah S.7#1058Eva T.21#1059Liam D.4#1060Mia K.9auto-fillsConversations1,2041,208Closed chat volume4.82k4.84kReassignments1213Closed chat volume, last 14 daysConversationsNotesDaily conversationsInboxReassignmentsResolutionsCustomersDashboard

Kickoff

Qualification check

Applies the written qualification rule to each event and keeps the result beside it.

Kickoff

Stable identity ledger

Maintains the link between a Crisp record and its WhatsApp twin, so updates land in the right place.

Kickoff

Mapping documentation

Produces the field map as plain documentation your team can read and keep.

Build-out

Consent check

Looks up the opt-in you hold for the number and blocks the send when there is none.

Build-out

Window and template chooser

Chooses a free-form reply inside 24 hours and an approved template outside it, filling in the variables.

Build-out

Number formatter

Normalizes the Crisp phone number to international format and rejects one that cannot be fixed.

Review

Delivery register

Flags any message whose content no longer mirrors Crisp, and says since when.

Review

Template drift watch

Flags a template that was changed or rejected before a send fails.

Review

Exception alerts

Notifies the right person when an exception appears, not the whole team.

From connect crisp to whatsapp to crisp to whatsapp and crisp to whatsapp error handling, one route. Related searches include crisp to whatsapp duplicate prevention, crisp whatsapp follow-up message, crisp to whatsapp implementation, crisp to whatsapp Zapier alternative, crisp whatsapp template message, sync crisp conversations to whatsapp, crisp to whatsapp service, crisp whatsapp integration, crisp whatsapp Make scenario, sync crisp with whatsapp, crisp to whatsapp workflow, crisp to whatsapp historical migration, crisp to whatsapp API integration, crisp resolved chat whatsapp, crisp to whatsapp integration, crisp whatsapp automation, crisp whatsapp delivery status, crisp whatsapp opt-in, crisp to whatsapp consultant, crisp whatsapp business API, crisp phone number whatsapp, crisp contacts data whatsapp and crisp to whatsapp setup service.

G7Who it is for

Fits agencies managing several Crisp websites and whoever must follow up on a chat by WhatsApp only when the person has agreed, in the window and wording WhatsApp allows

Crisp is where the conversation starts, and WhatsApp is where many customers would rather continue it, if they have said so.

Support lead

"Follow up where people reply."

A resolved chat can send one approved WhatsApp message to a customer who agreed.

Store owner

"Don't annoy anyone."

A number without recorded consent is never messaged.

Compliance lead

"Show me who opted in."

Every send records the consent source, and counsel decides the policy itself.

Operator

"Tell me if it arrived."

The delivery state is written to the chat as a private note.

Agency lead

"A number per client."

A client website uses its own WhatsApp sender and its own templates.

Founder

"Sync Crisp with WhatsApp, simply."

One follow-up per chat, in words you approved.

What changes the price: templates, consent and delivery states

Weigh the WhatsApp cost against the templates you need

Answer a few questions on scope and the total settles on a firm figure from $710.

View Pricing

One setup fee

I9Your options

Side by side: a template sent to every number, a zap and a consent-checked WhatsApp route

Each can send a message. Only one checks consent and the window first.

Comparison table: Side by side: a template sent to every number, a zap and a consent-checked WhatsApp route
How a message is triggeredA template to every numberA zap that sends on every eventOur consent-checked WhatsApp route
What starts the workAn owner checking dailyAny update at allApproved chat events only
How identity is decidedDecided case by caseThe display textWebsite ID, session ID and WhatsApp message ID
What reaches WhatsAppA fraction of the recordA minimal recordOne consent-checked message, reply or template, with delivery recorded
After an uncertain resultRe-run and hopeRetries on a timerProves the outcome before repeating anything
By handstops to export, copy, paste, fixAutomatedno stops · every 15 minutes

A delayed event meets a newer record

The stored time of the last confirmed change guards every write, so a late event cannot regress the message.

A visitor shares a number but never agreed to messages

The send is blocked, the chat is noted as having no opt-in, and the operator is shown the reason instead of a delivery. Searching WhatsApp on the website ID, session ID and WhatsApp message ID shows whether the message is already there, and whether it is right. Nothing new is created unless the lookup comes back empty.

We begin by fixing the website ID, session ID and WhatsApp message ID, and every test afterwards checks that it still holds.

Pricing

Build your Crisp to WhatsApp price

Pick a package, answer three short questions about how Crisp data should reach WhatsApp, and your price and turnaround move as you choose.


Choose your packageRequired

The three packages differ by how much routing, reconciliation and governance sits around the Crisp to WhatsApp route.

A focused production route for one Crisp environment and one WhatsApp destination, delivering WhatsApp follow-ups from Crisp chats sent only where consent is recorded, as a reply inside the 24-hour window or an approved template outside it, with delivery states recorded with identity and failure controls from day one.

  • One approved Crisp event family and business-state admission rule within the Crisp to WhatsApp service.
  • One authorized account, workspace, organization, or base boundary within the Crisp to WhatsApp service.
  • One WhatsApp object contract with field and relationship mapping within the Crisp to WhatsApp service.
  • Stable matching through website ID plus session ID and person ID and customer phone identity plus message ID and source fingerprint
  • Tests for duplicates, stale events, malformed data, denied access, and timeouts within the Crisp to WhatsApp service.
  • Implementation map, test record, and premium PDF operations handover within the Crisp to WhatsApp service.

Adds branching, matching and a bounded historical pass for teams whose route into WhatsApp cannot be one straight-through action, while still delivering WhatsApp follow-ups from Crisp chats sent only where consent is recorded, as a reply inside the 24-hour window or an approved template outside it, with delivery states recorded.

  • Everything in Foundation
  • Up to four approved routing or state-transition branches within the Crisp to WhatsApp service.
  • Existing-record resolution and one bounded historical checkpoint within the Crisp to WhatsApp service.
  • Lookup-before-replay protection for uncertain writes
  • Named exception ownership and a decision-ready evidence packet within the Crisp to WhatsApp service.
  • Field, permission, and destination-state validation before mutation within the Crisp to WhatsApp service.

Adds reconciliation and governance for teams that now depend on WhatsApp follow-ups from Crisp chats sent only where consent is recorded, as a reply inside the 24-hour window or an approved template outside it, with delivery states recorded, with drift detection and an exception register for WhatsApp.

  • Everything in Controlled Flow
  • Scheduled source-to-destination reconciliation
  • Schema, field, scope, and webhook drift checks within the Crisp to WhatsApp service.
  • Volume-aware retry ceilings and stale-event protection
  • Aged-exception reporting with ownership status
  • Thirty-day release watch and operating review

In this Crisp to WhatsApp design, multi-business-unit routing, unrestricted bidirectional synchronization, regulated archives, unsupported extensions, or additional destination systems receive a separate written quote. Third-party subscriptions and usage charges are excluded.

Which Crisp events should reach WhatsApp?Required

Governed lifecycle set: Use this when several approved Crisp transitions must converge on one WhatsApp conversation.

How should WhatsApp recognize a Crisp record it has already handled?Required

Ambiguity queue: Route zero-match and multi-match cases to an owner instead of letting WhatsApp guess.

How much Crisp context should travel into WhatsApp?Required
How soon do you need it live?Required

Standard follows the schedule your other choices set. Pay to move up the queue and go live sooner.

Optional extrasOptional

Each one begins switched off. Turn on what your rollout needs, watch the total, switch it back off.

J11The process

Six steps from blanket messaging to follow-ups people want

Six steps from kickoff to a monitored route, each with a written result.

  1. Define who may be messaged

    We agree where consent comes from, which chats may get a follow-up and which templates cover each case.

    Day 1
  2. Approve access

    The connections between Crisp and WhatsApp are made with limited, revocable permissions.

    Access review
  3. Agree templates and wording

    Template names, variables, the reply rules and the failure handling are written down and signed off.

    Build phase
  4. Acceptance runs

    Normal and awkward records are pushed through a test WhatsApp, and you sign off the results before go-live.

    Before you review
  5. Launch with notes

    Once tests pass, the route goes live from a set checkpoint and the documentation is delivered.

    Release day
  6. Close the loop

    A final review confirms the success measures agreed at the start and records what to watch next.

    Day 1
Handover for Crisp to WhatsApp automation: notes, a checked run and a health checkHandover timeline: brief, map, build, test, hand over and a week of support, with the current step highlighted.From first brief to a number that runs itself1Brief1 page2MapFields3BuildSync4TestEdge cases5Hand overPDF pack6Support1 weekClear scopeSet onceTested on real conversationsZero duplicatesOwned by youPlain notes

K12Turnaround

How many days each package needs

Days are counted from approved access, not from Crisp payment.

Kickoff

6 to 10 business days

Build-out

10 to 16 business days

Review

16 to 24 business days

L13Getting started

What you need to hand us

Read access to the Crisp data the route will use

A WhatsApp Business sender with approved templates, and Crisp read access to the website

The Crisp account owner's sign-off for the connection

A list of the statuses or stages that matter to you

A short description of how the team works in WhatsApp today

Your retention rule for anything the route logs

M14Safety and ownership

Only listed fields move, and every permission is explained

Think of it as a pipe with two labelled ends: Crisp on one side, WhatsApp on the other, and nothing kept along the way.

Read-only Crisp to WhatsApp access: your data stays yoursA WhatsApp Business number covered by a padlock with a note that you own it and access is read-only.Conversations (read-only)You own itRead-only access

Outside the core

The route runs beside Crisp and WhatsApp, not within them, so neither vendor's own updates collide with it.

Scoped, revocable access

Each connection has the narrowest permissions that work, recorded in the handover.

Only approved values cross

What appears in WhatsApp is exactly what the field map lists, and the map is part of the handover.

Doubtful writes are verified

If a response goes missing, WhatsApp is searched by the website ID, session ID and WhatsApp message ID and the outcome recorded before anything else happens.

Minimal logging

Diagnostic records are deliberately thin, so there is little to protect.

Full handover

There is no lock-in; the notes explain every setting we chose.

N15In their words

What BoldBellows clients say

Verified reviews from business owners who use BoldBellows automations every day, from marketing and sales to support and operations.

AI Workflow Automation for Agencies

Running a digital agency with many clients was overwhelming. BoldBellows built one automation dashboard that tracks tasks, sends updates and creates client reports automatically.

Clients love the transparency and we love the time we get back. Productivity is up, and project delays have dropped to almost zero.

Samuel BoatengVerifiedAccra, Ghana

AI Customer Journey Automation

We wanted a smoother path from first contact to purchase. BoldBellows built an AI system that guides each customer there automatically.

It sends personalized messages, recommends products and follows up at just the right moment. Customer retention has improved dramatically.

Nadia HassanVerifiedCairo, Egypt

AI E-commerce Listings Automation

BoldBellows automated our product listings. The AI writes descriptions, organizes photos and publishes listings across several marketplaces.

It even answers customer questions instantly. Our store looks more professional and sales have noticeably increased.

Pedro LimaVerifiedSão Paulo, Brazil

AI Document & Contract Automation

Onboarding was slow because we wrote every contract by hand. BoldBellows automated the lot: contracts, welcome emails and client setup.

What took 48 hours now takes under 10 minutes, and clients regularly tell us how professional it feels.

Michael O’ConnorVerifiedDublin, Ireland

AI Social Comment & DM Automation

We get thousands of comments and messages every week. BoldBellows built an AI system that replies instantly, filters spam and surfaces the important ones.

Engagement is up and our page looks active around the clock. It’s like having a full social media team that never stops.

Sofia DimitrovVerifiedSofia, Bulgaria

AI CRM Automation

Our CRM was barely used because updating it by hand was tedious. BoldBellows automated data entry, tagging, segmentation and follow-ups.

Now the CRM is always up to date and our campaigns are far more accurate. It improved our whole sales pipeline.

David KimVerifiedSeoul, South Korea

AI Voice Assistant

BoldBellows built a custom AI voice assistant for our customer hotline. It answers questions, books appointments and handles simple requests.

Customers love how fast it is, and our call-centre workload dropped dramatically. One of the smartest upgrades we’ve made.

Hannah JohnsonVerifiedChicago, USA

AI Automation Partner

BoldBellows is hands-down the best AI automation partner we’ve worked with. Their systems are fast, reliable and built around how our business actually works.

Every automation they’ve delivered, from customer service to content, runs flawlessly. We’ve saved time, cut costs and grown faster than we expected.

Kwame MensahVerifiedKumasi, Ghana

AI Chatbot & Customer Support

BoldBellows built an AI support chatbot for our online boutique, and it has changed how we run the business. We used to have two full-time staff answering the same questions all day. Now the AI handles order tracking, product recommendations and even refund requests on its own.

What surprised me most is how natural it sounds. Customers compliment the ‘agent’ without realizing it’s AI. Our support workload dropped by 75% and customer satisfaction went up dramatically.

Maria GonzálezVerifiedMadrid, Spain

P16FAQ

Messaging customers from Crisp: what teams ask about WhatsApp

Read these first; whatever is left can be asked in your quote request.

PriceTimeAccessHandover?Every question, answered
Can a Crisp to WhatsApp Zapier integration retry safely?

A WhatsApp message for every chat is easy. The hard part, which a zap skips, is to send only to people who opted in, choose between a reply and an approved template by the 24-hour window and record delivery. That is the extra we deliver on top of the trigger.

How do I connect Crisp to WhatsApp for follow-ups?

The route reads a resolved or waiting chat in Crisp, checks consent, and sends a reply or an approved template through your WhatsApp Business sender.

Is there a Crisp to WhatsApp Zapier alternative that checks consent?

A zap sends whatever it is given. Checking opt-in, choosing between a reply and a template and recording delivery are left out.

What happens after the 24-hour window in the Crisp to WhatsApp route?

The route sends only an approved template, with the variables filled in from the chat, instead of a free-form message that would be rejected.

Which Crisp contacts data does WhatsApp receive?

Crisp contacts data WhatsApp needs is limited to the number, a first name and the template variables. Nothing else is sent.

Can it use the Crisp to WhatsApp API integration directly?

Yes. This custom Crisp to WhatsApp automation reads Crisp through its API and sends through the WhatsApp Business Platform, using the sender you set up.

Who decides the consent policy?

You and your counsel do. The route enforces the rule you record and keeps a trail, and it does not give legal advice.

Is there a written map at handover in the Crisp to WhatsApp route?

Yes, and it is part of every package: our Crisp WhatsApp field mapping service assigns each Crisp field a destination, a type and a format for your sign-off before the build starts.

Can we combine several triggers?

Yes. The route is built around your logic, so it is a custom Crisp workflow for WhatsApp with a Crisp WhatsApp integration consultant's care behind it, from $710.

Will an update to WhatsApp break the route?

If the platforms change, the route degrades gracefully: it holds the affected record and flags it. Follow-up support once your review window ends is quoted on its own.

Q17Follow up where customers reply, with their permission

Give your chats WhatsApp follow-ups that are wanted and recorded

We shape the route that will automate Crisp data to WhatsApp and show the price first, from $710.

  • From $710, paid once
  • Consent first
  • Window checked
  • No monthly fee from us

Larger or stranger setups are welcome; they get their own written quote, on the Crisp to WhatsApp route.