Back to Use Cases
Marketing Suite

Drip Campaigns

Trigger-based automation

Used byMarketing

Turn one-off blasts into automated, multi-channel journeys that run themselves.

Drip Campaigns is BOL7's automation engine for scheduled, trigger-based sequences across WhatsApp, Email, SMS, RCS and Voice. Design each step with its own channel, template and delay, enroll audiences from forms, e-commerce orders, ad leads, CSVs or CDP segments, and govern timing with timezone, business-hours and quiet-hours rules. It solves the problem of manual, inconsistent follow-up by letting teams launch reliable nurture journeys and measure them end to end.

8 use cases

Documented use cases

01

5-Step WhatsApp Onboarding That Runs On Autopilot

Customer onboarding manager
Problem

New users sign up and then get a single welcome message before going quiet, because the team has no reliable way to keep nudging them over the first week. Onboarding emails get sent manually and inconsistently, so activation stalls and support tickets pile up from confused users who never learned the basics.

How BOL7 solves it

Build a 5-step WhatsApp sequence where each step carries its own template and a delay measured in days, hours or minutes — for example a 1-day gap after welcome, then a 1-hour reminder. Steps inherit the campaign timezone and business hours so messages land at sensible times, and you can enroll new signups automatically via the form_submitted trigger.

Outcome

Every new user gets the same well-paced, on-channel onboarding journey without anyone sending messages by hand, so activation becomes consistent and predictable.

WhatsAppOnboardingAutomation
02

Mix Channels In One Sequence For Better Reach

Lifecycle marketer
Problem

Relying on a single channel means a chunk of the audience never sees the message — emails sit unread, or a WhatsApp number is stale. Running parallel campaigns on separate tools to cover the gaps is fiddly, duplicates effort, and makes it impossible to treat the follow-ups as one coherent journey.

How BOL7 solves it

Assign a different channel per step inside one sequence: WhatsApp for step one, Email for step two, and an SMS fallback for step three, each with its own template and delay. Because channel is set at the step level, you orchestrate the whole multi-channel cadence in a single campaign with shared timing rules.

Outcome

You reach contacts where they actually respond and maintain one connected narrative across channels instead of disconnected, competing campaigns.

WhatsAppEmailSMSMulti-channel
03

Auto-Enroll Meta Ads Leads The Moment They Arrive

Performance marketing manager
Problem

Leads from Meta Ads lead forms go cold while they wait to be exported, cleaned and uploaded into a follow-up tool. That lag between a prospect raising their hand and the first reply kills conversion, and manual handoffs mean some leads slip through entirely.

How BOL7 solves it

Use the lead_created trigger to enroll leads from a specific Meta Ads campaign into your drip sequence the instant they submit. New leads flow straight into the steps you've defined, with suppressions applied so anyone who shouldn't be contacted is excluded automatically.

Outcome

Ad spend converts faster because every lead enters a timely nurture journey without manual export-and-upload, and unwanted contacts are filtered out at enrollment.

Meta AdsLead nurtureTriggers
04

Drip To A CDP Segment While Protecting Unsubscribers

CRM / audience manager
Problem

Targeted campaigns require pulling a precise segment, but exporting lists by hand risks sending to people who already opted out — a compliance and reputation hazard. Reconciling suppression lists across tools is error-prone, and one mistaken send to unsubscribers can damage deliverability and trust.

How BOL7 solves it

Import a CDP segment directly as the campaign audience instead of juggling CSVs, then apply suppressions so known unsubscribers are filtered out before any step fires. Enrollment from the segment and the suppression list work together so only the right, consented contacts enter the sequence.

Outcome

You reach a precisely defined audience while keeping opted-out contacts safely excluded, protecting deliverability and compliance.

CDPSegmentsSuppressionsCompliance
05

Respect Quiet Hours And Holidays Automatically

Marketing operations lead
Problem

Automated messages fired at 2am or on a public holiday feel spammy and erode trust, yet manually checking the clock and calendar for every send doesn't scale. Coordinating timing across regions is especially painful, and one badly timed batch can spike opt-outs.

How BOL7 solves it

Set campaign-level timezone, business hours, quiet hours and holiday dates that cascade to every step, so sends are automatically held outside acceptable windows. Each step can inherit, override, or opt out of these rules, giving you a global default with precise exceptions where a particular step needs different timing.

Outcome

Messages arrive at considerate, locally appropriate times by default, with the flexibility to override timing for the rare step that needs it.

Quiet hoursSchedulingHolidays
06

Catch Errors Before You Hit Launch

Campaign QA / operations specialist
Problem

Discovering a broken template, missing variable or misconfigured step after a campaign has gone out to thousands of contacts is a costly, irreversible mistake. Without a structured pre-launch check, teams rely on eyeballing the setup and inevitably miss issues that only surface once real messages start failing.

How BOL7 solves it

Run preflight validation to surface issues classified by severity — error, warning, or info — where blocking errors stop the launch until they're fixed. Once the setup is clean, use Test Send (or Test Call) to deliver a step to your own number and confirm it renders correctly before going live.

Outcome

You launch with confidence, having resolved blocking problems and seen a real step land on your own device first.

PreflightTest sendQA
07

Pause For A Sale, Resume Without Losing Your Place

Retail / e-commerce marketing manager
Problem

During a major promotion, ongoing nurture messages clash with sale communications and overwhelm customers, but tearing down and rebuilding a campaign afterward wastes effort and loses configuration. Teams often just let conflicting messages go out because stopping cleanly feels too disruptive.

How BOL7 solves it

Pause an Active campaign for the duration of the sale period so its steps stop firing, then Resume it afterward to pick up where it left off. The campaign configuration, audience and timing rules stay intact, so there's nothing to rebuild.

Outcome

You can step out of the way during peak promotions and resume nurturing seamlessly, with no rebuild and no conflicting messages.

PauseResumeE-commerce
08

See What Worked And Export The Full Log

Growth / marketing analyst
Problem

Without per-campaign metrics, teams can't tell which steps and channels actually drove engagement, so they keep repeating sequences on gut feel. Stitching together delivery and engagement data by hand for reporting or audits is slow and incomplete.

How BOL7 solves it

Review built-in results for open, click and delivery metrics across the sequence, then dig into the execution log to see exactly what fired and when. Export the execution log for deeper analysis, reporting or audit trails outside the platform.

Outcome

You understand which steps and channels performed, and you have a clean, exportable record for reporting and compliance.

AnalyticsReportingExport