Skip to content
Mumara

Sending

Sequences that send themselves — and route each step right.

A drip is a series of emails with waits and branches between them, running on each contact's own clock. In Mumara ONE every step picks its own Bridge — so nurture steps leave on promotional IPs and any transactional step leaves on transactional ones, inside a single sequence.

Get started Per-step routing →
  • Waits in minutes, hours, or days
  • Branches on behaviour + data
  • Per-step Bridge selection
  • Trigger- or segment-started
drip · onboarding

  • Entry

    joins "New leads" segment

  • Welcome email

    marketing-bridge

    first step, no wait

  • Wait 2 days

  • Getting-started tips

    marketing-bridge

  • Clicked a link?

    yes → offer · no → nudge

each contact on its own clockactive ✓

Drip vs broadcast

A broadcast is a moment. A drip is a relationship.

A broadcast goes to everyone at once. A drip meets each contact where they are — starting the clock when they enter, pacing the emails, and branching on what they do.

Because a drip runs per contact, two people who sign up a week apart both get the same welcome sequence on their own timeline. You build the path once; the platform runs an independent copy for everyone who enters.

Steps aren't limited to sends. Insert wait periods measured in minutes, hours, or days, and branch nodes that split the path on a click, an open, a field value, or segment membership — so the contact who engaged goes one way and the one who didn't goes another.

Under the hood it's the same composing engine as Broadcasts — the same two editors, the same AI composer, the same personalization. A drip step is a broadcast that knows where it sits in a sequence.

The ONE difference

Each step picks its own Bridge.

A nurture sequence often mixes message types — a warm welcome, a couple of educational sends, then a time-sensitive transactional confirmation. In Mumara ONE each step routes through its own Bridge, so the right message leaves on the right reputation lane.

Steps 1–2

Nurture

Welcome and education route through marketing-bridge → your promotional Pool.

Step 3

Transactional

A confirmation or receipt routes through transactional-bridge → transactional Pool.

Result

Clean separation

Marketing volume never sits on the IPs your transactional mail depends on — within one sequence.

Build a drip

From entry to live in five steps.

  1. Step 1

    Define the entry

    Choose what starts the drip — a Trigger event (form submit, list join, field change) or membership in a segment. Matching contacts enter automatically.

  2. Step 2

    Build the steps

    Add emails, wait periods, and branch nodes. Compose each email with the same editors and personalization as a broadcast.

  3. Step 3

    Route each step

    Assign the Bridge per step so nurture and transactional messages leave through the right Pool and IPs.

  4. Step 4

    Activate

    Turn the drip on. New contacts begin entering; existing ones can be enrolled retroactively where it makes sense.

  5. Step 5

    Monitor

    Track per-step delivery, opens, clicks, and drop-off in real time, and tune waits or branches as the data comes in.

What it removes

The friction of running sequences by hand.

  • Manually timing follow-ups

    Without a drip, "send the tips email two days after signup" is a calendar reminder and a copy-paste. A drip runs the wait and the send automatically, per contact, forever.

  • One reputation lane for everything

    Sending a transactional confirmation on the same IPs as bulk nurture risks the mail that matters most. Per-step Bridge routing keeps each message on the right lane.

  • Everyone gets the same path

    A sequence that ignores behaviour wastes sends on people who already converted. Branch nodes split the path so engaged and unengaged contacts get different treatment.

  • No visibility into where people drop

    A black-box sequence hides which step loses people. Per-step reporting shows exactly where contacts fall off so you can fix that step.

“We run onboarding and a transactional receipt in the same sequence, and being able to put the receipt step on its own Bridge was the thing no other tool let us do cleanly. Our marketing volume never touches the IPs the receipts depend on. Set it once, and every new signup just flows through it.”

Verified review

Mumara ONE customer

G2

Common questions

What buyers usually ask.

What starts a drip?

Either a Trigger — a form submission, a list join, a field change — or entry into a segment. New matching contacts begin the sequence automatically, and you can also enrol existing contacts retroactively where it makes sense.

Can different steps send from different IPs?

Yes — that's the ONE difference. Each step selects its own Bridge, and the Bridge determines the Pool and dedicated IPs. So a nurture step can route through your promotional Pool while a transactional step in the same sequence routes through the transactional Pool.

How do branches work?

A branch node splits the path on a condition — did the contact click, open, match a field value, or belong to a segment. Each side of the branch continues with its own steps, so engaged and unengaged contacts get different follow-ups.

Is it the same editor as broadcasts?

Yes. A drip step uses the same HTML editor or drag-and-drop builder, the same Mumara AI composer, and the same personalization (merge tags, conditional content, spintax) as a broadcast.

Can I see where contacts drop off?

Yes. Per-step reporting shows delivery, opens, clicks, and drop-off for each step in real time, so you can tell which email loses people and adjust the content, the wait, or the branch.

Related

Pages that pair with this one.

Mumara ONE · Drip Campaigns

Set the path once. It runs for every contact.

Emails, waits, and branches on each contact's own clock — with each step routed through the Bridge that carries the right reputation. Nurture and transactional, in one sequence.

Get started See pricing