Can someone end up in two campaigns that contradict each other?

Only if you build it that way. Entry frequency and exit conditions are settings you fill in, not defaults you discover later.

Do I have to import a list to start a campaign?

No. Journeys trigger on events, so the audience builds itself as people qualify. There is no upload and nothing to keep in sync.

Can a journey change what someone sees inside my app?

Yes. Alongside email, SMS, push and Slack, a journey can place an in-app surface such as a nudge or a video. Your app reads it through the SDK off the same profile, so it is the audience you already defined.

How does it know what happened in my product?

It reads the same customer profile your pages and reports read. There is no export step and no second pipeline in between.

Does each channel cost extra?

Sends are metered per channel, the way email and SMS always are. Push runs through Firebase as an ordinary channel on the same canvas rather than as an upsell.

Build journeys around what customers actually do.

Build email, SMS, push, Slack, and in-app journeys from one customer profile and trigger every step on live behavior.

Start for free

0.0on G2

10B+events

500M+users

7+years profitable

50+enterprises

Run every channel from one journey.

Send email, SMS, push, and Slack from the same flow, next to waits, branches, and webhooks.

Send email through SendGrid, Amazon SES, or your own Gmail
Add SMS, push, and Slack to the same campaign
Reach anything else with a webhook step

Meet customers where they are.

A nudge or a video lands while someone is already using the thing you want them to use.

Add in-app surfaces alongside email, SMS, push, and Slack
Use the same entry and exit rules for both
Trigger from the segment you already built

Let behavior start the next step.

Start a journey the second an event fires, with no list to import and no schedule to wait for.

Fire on any product event, the moment it lands
Skip the CSV upload and the list sync
Drop the nightly run

Keep every journey tied to the customer.

Journeys, pages, reports, and the CRM all work off one customer record, so nothing is exported between them.

Share one profile across every channel
Pick up a segment change the same second it happens
Remove the drift between two systems

Keep every journey focused.

Set entry and exit rules so nobody sits in two campaigns that say opposite things.

Enroll someone once, or every time they qualify
Include people who already matched, or only new ones
Write the exit rule instead of leaving it implied

Let Blu build the journey for you.

Describe what you want, and Blu drafts the structure, then you change what you like and publish.

Get a trigger, delays, and messages back as a draft
Start from a welcome, win-back, or abandoned cart in one line
Publish nothing until you have read it

Use cases built for the metrics that matter.

Three outcomes lifecycle teams measure from day one.

RFM tiers, churn risk and a journey triggered when the tier changes

Wired into the toolsyour team already opens.

Slack, Stripe, Twilio, SendGrid, Gmail, Google Calendar, Firebase, Apache Kafka, AWS. Blu Agent operates them for you without a browser tab.

See the full list

Teams love it

They stopped stitching tools andhired one system.

Jim Stromberg, CEO at StockInvest — “Acquisition and retention finally feel like one connected motion instead of two separate problems.”
Jim Stromberg
CEO, StockInvest

“Acquisition and retention finally feel like one connected motion instead of two separate problems.”
Jim Stromberg
CEO, StockInvest

Eric Gardner, COO at FieldsUSA — “We finally have one system that sees the whole customer journey.”
Eric Gardner
COO, FieldsUSA

“We finally have one system that sees the whole customer journey.”
Eric Gardner
COO, FieldsUSA

Tadas Kertenis, Co-founder at Hoperfy — “With Intempt, we built a signal-led pipeline driven by real behaviors.”
Tadas Kertenis
Co-founder, Hoperfy

“With Intempt, we built a signal-led pipeline driven by real behaviors.”
Tadas Kertenis
Co-founder, Hoperfy

Frequently askedquestions.

Start from behavior, shape the journey, review the message, then send from one customer profile.

01 / 06

Isn't a journey builder the old way of doing this?

It is, if the journey is all you have. A tree with fixed branches breaks when someone does something you did not plan for. A journey here sits on the same profile as your site, your app and your reports, so the branch reads what is true about the person right now rather than what was true when they entered. And you do not have to draw the tree yourself, because Blu will draft it from a sentence.

It is, if the journey is all you have. A tree with fixed branches breaks when someone does something you did not plan for. A journey here sits on the same profile as your site, your app and your reports, so the branch reads what is true about the person right now rather than what was true when they entered. And you do not have to draw the tree yourself, because Blu will draft it from a sentence.
Only if you build it that way. Entry frequency and exit conditions are settings you fill in, not defaults you discover later.
No. Journeys trigger on events, so the audience builds itself as people qualify. There is no upload and nothing to keep in sync.
Yes. Alongside email, SMS, push and Slack, a journey can place an in-app surface such as a nudge or a video. Your app reads it through the SDK off the same profile, so it is the audience you already defined.
It reads the same customer profile your pages and reports read. There is no export step and no second pipeline in between.
Sends are metered per channel, the way email and SMS always are. Push runs through Firebase as an ordinary channel on the same canvas rather than as an upsell.

Intempt Marketing

Your first journey, live this week.

Connect your sources, map your first lifecycle trigger, and send your first behaviorally driven message the same day. The agent runs the journey inside the branches and exit conditions you set.