An example journey where multiple communication steps can be managed in sequence after a configured entry condition for a new customer or member context.
JOURNEY MANAGER
Move from one message
to a controlled customer journey.
Pika Journey Manager brings entry conditions, branching, wait steps and Email, SMS or WhatsApp actions together to help build multi-step customer journeys.
The objective is not to send customers a sequence of messages without context. It is to manage when and under which predefined conditions each step should progress.
START
01
CONDITION
02
WAIT
03
ACTION
04
WhatsApp Business API
Official Meta API
Email & SMS
Verified Channels
Pika Opportunity Engine
Daily Discovery
İYS & KVKK
Consent Verification
Multi-Step Flow
Conditions & Branching
Wait Steps
Email / SMS / WhatsApp
Controlled Automation
THE SHORT ANSWER
What is Journey Manager?
Journey Manager is Pika's multi-step journey-orchestration layer for managing how a customer or audience progresses through predefined entry conditions, decision points, branches, wait steps and communication actions.
Campaign Manager focuses on controlled delivery for a defined campaign, while Journey Manager manages a flow that can contain multiple steps and decision points over time.
Journey Manager answers one central question:
CENTRAL FOCUS QUESTION
“In this customer context, what should the next step be, and under which condition should it progress?”
The journey structure is defined and activated by the user. Progress inside an active journey can then follow configured condition, wait and action rules.
REPEAT PURCHASE SCENARIO
A timely reminder. Another reason to return.
Imagine a customer whose coffee may soon need replenishing. Watch a sample journey check purchase status and offer a product reminder when conditions allow.
01 · ENTRY
Customers approaching replenishment
02 · WAIT
Wait until the planned reminder time
03 · CONDITION
No new purchase and email permission valid?
YES · ACTION
Remind them of their favorite coffee
A personal email with a product link: “Ready for your next coffee break?”
NO · END
End without a reminder
Skip this reminder if they purchased again or permission is not valid.
Goal: invite the customer back with a reminder relevant to their needs.
Conceptual animation; no real customers are processed and no messages are sent.
FROM ONE SEND TO A FLOW
Some customer processes do not end with one campaign.
A campaign can manage controlled delivery of a particular communication to a defined audience. But in some customer processes, the next step may depend on a customer response, elapsed time or a newly satisfied condition.
For example, after reaching one step, the next communication may wait rather than being sent immediately. In another case, the journey may move into a different branch depending on a condition result.
Journey Manager allows these multi-step decision flows to be defined in advance.
A CAMPAIGN
executes a communication decision.
A JOURNEY
manages progression logic across multiple steps.
The value of Journey Manager is therefore not to create more messages, but to turn customer processes involving time and conditions into controlled flows.
BUILDING BLOCKS
Define the journey through steps and decision points.
Journey Manager builds a multi-step flow from building blocks with different responsibilities.
Start
Defines the context or configured entry condition through which a customer or audience enters the journey.
Condition
Evaluates whether available customer, behavioral or journey context satisfies a defined rule.
Branch
Allows the customer to progress into a different journey path based on the condition result.
Wait
Allows the next step to wait according to defined timing logic rather than executing immediately.
Channel Action
Associates an appropriate communication step in the journey with Email, SMS or WhatsApp.
End
Represents the point where the customer's defined journey process is complete or should no longer continue.
The meaning of a journey does not come from individual nodes alone, but from how those nodes are connected through sequence and rules.
ENTRY CONTEXT
Define why the journey begins.
A journey is not a sequence of messages that customers enter at random. The context or configured condition through which a customer enters the flow is defined first.
Entry context can come from customer or audience membership, relevant transaction context, a behavioral condition or another configured journey condition available in Pika.
Here, a trigger is the configured entry condition evaluated before journey progression begins.
Trigger:
provides context for: “When should this journey begin evaluation?”
Trigger:
does not mean: “Pika made the commercial decision independently of the user.”
The journey structure itself is defined and activated by the user.
CONDITIONS & BRANCHING
Not every customer has to follow the same path.
One of the key advantages of a multi-step journey is that it does not force every customer through one linear sequence.
A configured condition can be evaluated at a decision point. If the condition is satisfied, the journey may progress into one branch; otherwise it may continue into another.
Those conditions rely on available customer, audience, transaction or journey context that can be used in the flow.
BRANCHING LOGIC
CONDITION → YES / NO → DIFFERENT JOURNEY PATHS
Branching is not an AI decision predicting what the customer will do. It is the application of decision logic defined by the user inside the journey.
WAIT & TIMING
The right next step does not always belong immediately after the current one.
Wait logic can be placed between steps in a journey.
A wait step keeps the customer within the journey while preventing the next action from progressing until the configured timing condition is reached.
This creates controlled timing across multi-step communication instead of allowing every action to execute one after another at the same moment.
A wait step:
does not answer: “What should we send the customer now?”
A wait step:
manages: “When should the configured next step progress?”
Timing is part of journey strategy; it is not the only safety control governing communication frequency.
CHANNEL ACTIONS
Connect the journey decision to an appropriate communication channel.
Communication steps in a journey can be associated with Email, SMS or WhatsApp.
A communication channel for journey steps that require richer or visual content.
Explore Email →A messaging channel that can be used for relevant journey communication steps through approved WhatsApp templates.
Explore WhatsApp →A channel action is only one part of journey logic. Conditions, sequence, waits and permission controls are separate contexts.
The journey determines which step progresses. The channel is the execution path for that communication step.
FROM “WHO?” TO “WHAT NEXT?”
Audience Manager defines who belongs. Journey Manager manages what happens next.
Audience Manager and Journey Manager do not perform the same product role. Audience Manager defines a relevant customer group from customer context and rules.
Journey Manager manages the sequence and conditions through which those customers progress inside a configured multi-step flow.
AUDIENCE MANAGER
“Which customers match this context?”
JOURNEY MANAGER
“After those customers enter the journey, through which sequence and conditions should they progress?”
An audience can be one entry context for a journey. The audience definition is not the journey itself.
FROM OPPORTUNITY TO FLOW
Journey Manager does not create the opportunity. It connects a decision to a multi-step process.
Daily Opportunities makes evaluable commercial opportunities such as repeat purchase, cross-sell and win-back visible.
When a decision is made to build a multi-step relationship process around an opportunity, Journey Manager can manage configured conditions, waits and communication steps.
This relationship does not mean that an opportunity automatically launches a journey. Journey design and activation remain under user control.
DECISION & FLOW CHAIN
CUSTOMER & PRODUCT INTELLIGENCE → DAILY OPPORTUNITIES → HUMAN DECISION → AUDIENCE / ENTRY CONTEXT → JOURNEY MANAGER → EMAIL / SMS / WHATSAPP
Opportunity:
“Why?”
Audience / Entry:
“Who?”
Journey:
“What sequence and conditions come next?”
An example journey where waits, conditions and communication steps can be combined after relevant cart or transaction context.
An example journey where configured timing and communication steps can be used after repeat-purchase context has been evaluated.
An example journey where multiple controlled steps can be configured after relevant behavioral change or win-back context.
CAMPAIGN AND JOURNEY
Campaign Manager and Journey Manager do not solve the same delivery problem.
CAMPAIGN MANAGER
Campaign Manager
Manages content, channel, timing and pre-send controls within one campaign context for a defined audience.
“Which campaign and controlled delivery should be executed?”
JOURNEY MANAGER
Journey Manager
Manages the sequence and conditions through which a customer progresses across multiple decisions, waits and communication steps.
“What is the next step in the journey, and under which condition should it progress?”
Campaign: defined campaign execution. Journey: multi-step decision and progression flow.
A journey can contain communication actions, but that does not make Campaign Manager and Journey Manager the same product.
AUTOMATION ≠ UNCONTROLLED COMMUNICATION
The journey can progress. Control does not disappear.
Journey Manager is an automation product, but automation means progressing according to conditions, sequence, waits and actions configured by the user.
A customer reaching a channel-action step in a journey does not mean communication is sent through that channel without controls.
Available consent, opt-out, reachability and relevant delivery-eligibility controls are evaluated separately during communication execution.
Generative AI is not the source that independently determines commercial truth or the customer's next journey step.
Journey Manager:
can progress a configured flow automatically.
The user:
defines the journey structure and business rules.
Consent / delivery controls:
separately evaluate whether communication can be executed.
AI:
may assist preparation or explanation; it does not take control.
The purpose of automation is not to remove human control, but to make configured decision logic repeatable.
Frequently Asked Questions
What is Journey Manager?
Journey Manager is Pika's multi-step journey-orchestration layer for managing how customers progress through predefined entry conditions, decision points, branching, wait steps and Email, SMS or WhatsApp communication actions.
What is the difference between Journey Manager and Campaign Manager?
Campaign Manager manages campaign content, channel, timing and controlled delivery for a defined audience. Journey Manager manages the sequence through which a customer progresses across multiple conditions, waits and action steps.
Which communication channels can Journey Manager use?
The confirmed active communication channels in C08 are Email, SMS and WhatsApp. Relevant communication steps in a journey can be associated with one of these channels.
What do conditions and branching do in Journey Manager?
A condition evaluates whether available customer or journey context satisfies a configured rule. Branching allows the customer to progress through a different journey path based on that result.
What does a wait step do in Journey Manager?
A wait step keeps the customer within the journey while preventing the next action from progressing until the configured timing condition is reached. This allows multi-step communication to follow controlled timing.
Is Journey Manager fully automatic?
The journey structure, conditions, branches, waits and actions are defined by the user, and the journey is activated by the user. After activation, customers can progress according to those configured rules. This does not mean the system creates commercial strategy independently of the user.
Does Journey Manager bypass communication consent?
No. Reaching a communication step inside a journey does not automatically mean delivery permission is valid. Available consent, opt-out, reachability and relevant channel controls are evaluated separately during communication execution.
Does Journey Manager create journeys autonomously with AI?
No. Journey Manager is not positioned as an autonomous AI journey engine that removes user control. Pika Pilot may assist preparation, while control of journey structure and business rules remains with the user.
CONTROLLED JOURNEYS
Define the condition.
Define the condition.
Build the sequence.
Let the journey progress under control.
Let's explore how Pika Journey Manager brings entry conditions, branching, wait steps and Email, SMS and WhatsApp actions together within controlled multi-step customer journeys.
Pricing is tailored to your requirements and scope of use.
GDPR Compliant
Enterprise Security
Dedicated Support