Bring approved WhatsApp communication
to the right customer context
inside Pika's controlled action chain.
Pika WhatsApp is one of Pika's confirmed communication channels for using approved WhatsApp Business API templates with audience context defined in Audience Manager inside controlled actions managed through Campaign Manager or Journey Manager.
WhatsApp communication is not independent from available opt-in context and approved-template requirements; the channel is not a free-form messaging or chatbot layer that bypasses those controls.
What is Pika WhatsApp?
Pika WhatsApp is one of Pika's communication channels for using approved WhatsApp Business API template communication within controlled campaign or journey context.
The role of the WhatsApp channel is not to independently select the audience, conduct unrestricted two-way customer conversations or generate replies as an AI chatbot.
Those capabilities are not part of the Pika WhatsApp product role.
WhatsApp answers one central question:
“How is this approved WhatsApp communication executed under available opt-in and action context?”
Audience, Campaign and Journey decisions are created in Pika's relevant product layers; WhatsApp is the execution channel for eligible communication.
WhatsApp: is an approved-template communication channel.
Pika: is the surrounding chain of understanding, decision, permission and measurement.
Put WhatsApp in the right place inside Pika's decision chain.
Pika is not a WhatsApp Marketing tool or chatbot product. WhatsApp is one of the confirmed communication channels inside the platform's customer-intelligence and omnichannel-action chain.
Customer Intelligence calculates customer behavior and value context, Product Intelligence establishes product context and Daily Opportunities makes evaluable commercial opportunity context visible.
Audience Manager manages who belongs, while Campaign Manager or Journey Manager manage how communication action is executed. WhatsApp is one execution channel for that controlled action.
Approved Template Communication
Use eligible WhatsApp Business template structures within controlled campaign or journey actions.
Audience Context
Use the actual audience defined in Audience Manager as upstream customer context for WhatsApp action.
Opt-In Control
Do not execute WhatsApp communication independently from available explicit opt-in context.
Measurable Delivery Outcome
Evaluate available WhatsApp delivery-outcome or status context within Analytics & Reporting.
WhatsApp does not create the decision. It is the communication channel for a defined decision.
Execute WhatsApp communication within official Business API context.
Pika's WhatsApp communication channel is used for template-based outbound communication through WhatsApp Business API context.
This does not turn WhatsApp into an unrestricted free-form messaging channel or an independent live-support inbox.
Pika does not independently control external WhatsApp Business platform policies, account eligibility or template-approval decisions.
Pika: uses approved template communication inside campaign or journey actions.
The WhatsApp Business platform: defines external platform context for template and account eligibility.
API connectivity does not remove platform governance.
Prepare WhatsApp campaign communication within eligible template context.
Pika WhatsApp uses approved WhatsApp Business template structures for outbound communication.
Before template content is used inside a campaign or journey action, it must be eligible within the relevant WhatsApp Business approval context.
Preparing a message inside Pika's campaign layer does not mean the template will automatically be approved by the external platform.
Pika: uses an approved template inside controlled action.
Pika does not guarantee: “Every prepared template will be approved automatically.”
Template preparation and template approval are different decisions.
WhatsApp does not choose the audience. It uses audience context.
Audience Manager defines the actual target audience through customer data and explicit rules.
The role of the WhatsApp channel is not to independently segment customers or select the “best” users.
A WhatsApp action inside Campaign Manager or Journey Manager can use the relevant audience context within controlled communication.
Audience Manager: “Who belongs in this audience?”
WhatsApp: “Within which action context will eligible WhatsApp communication reach this defined audience?”
Audience truth is not created by the WhatsApp channel.
Campaign WhatsApp
A campaign context where a defined audience and eligible approved-template content can be used in a controlled WhatsApp action through Campaign Manager.
Journey WhatsApp Step
A journey context where WhatsApp can be used with eligible template communication as a channel action inside conditions, sequence and wait logic managed by Journey Manager.
From Opportunity to WhatsApp Action
An action context where a commercial opportunity evaluated in Daily Opportunities can reach the WhatsApp channel after user decision, actual audience definition and relevant opt-in and template controls.
Campaign Manager manages the campaign. WhatsApp carries the communication.
Campaign Manager manages defined audience, content, channel, timing and pre-send controls within the same campaign context.
When WhatsApp is selected, eligible approved-template content can be used within controlled campaign execution.
The availability of the WhatsApp channel does not mean the campaign starts automatically or template controls are bypassed.
Campaign Manager: manages campaign context and controlled delivery.
WhatsApp: is the approved-template communication execution channel.
The campaign decision and WhatsApp execution do not perform the same product role.
WhatsApp can be one channel action inside a multi-step journey.
Journey Manager manages a multi-step customer flow consisting of entry conditions, branching, waits and action steps.
WhatsApp can be one configured channel action where eligible approved-template communication is used inside that flow.
The WhatsApp channel itself does not determine conditions, sequence, waits or the next step.
Journey Manager asks: “What is the next step and under which condition should it progress?”
WhatsApp asks: “Is WhatsApp the approved communication channel used at this step?”
WhatsApp is not an autonomous journey engine.
It is a channel action that can be used inside a journey.
Do not execute WhatsApp communication independently from customer opt-in context.
WhatsApp communication requires explicit customer opt-in context.
Pika's current public preference-update form covers Email and SMS preferences; WhatsApp consent is not managed through that same public checkbox flow.
WhatsApp opt-in context can come through separate incoming webhook or import flows and is evaluated separately within the relevant communication action.
Public preference form: EMAIL + SMS
WhatsApp: uses separate opt-in context.
Campaign / Journey membership: does not replace opt-in.
Belonging to an audience does not mean permission for WhatsApp communication.
Prepare the content. Preserve template governance.
WhatsApp communication content can be prepared for campaign or journey purpose and placed within an eligible template structure.
Available personalization fields based on existing customer context can be considered inside template content.
Personalization does not mean the WhatsApp channel invents new customer information or removes template-approval requirements.
Message preparation: prepares the content.
Approved-template context: defines the WhatsApp Business communication boundary.
User / campaign control: determines which prepared content is used in the action.
Prepared content does not mean unapproved free-form messaging.
After WhatsApp action, evaluate available delivery outcomes within measurement context.
WhatsApp communication does not end with dispatch. Available delivery-outcome or status context can become part of campaign evaluation.
That outcome helps explain what happened in the technical communication-delivery process.
Delivery status does not by itself prove that the customer read the message, replied or produced a commercial conversion.
WhatsApp: produces available delivery-outcome context.
Analytics & Reporting: evaluates that outcome together with campaign, audience and other measurement context.
Delivery outcome is not the entirety of customer behavior.
Put WhatsApp in the right place.
WhatsApp is not Customer Intelligence.
Customer Intelligence calculates customer behavior and value context. WhatsApp is one channel through which controlled communication based on that context can be executed.
WhatsApp is not Audience Manager.
Audience Manager defines the actual audience through explicit rules. WhatsApp does not independently choose the audience.
WhatsApp is not Campaign Manager.
Campaign Manager manages campaign and controlled-delivery context. WhatsApp is one selected execution channel.
WhatsApp is not Journey Manager.
Journey Manager manages conditions, sequence, waits and action flow. WhatsApp is a channel action that can be used inside a journey.
WhatsApp is not Consent Management.
Consent Management evaluates communication eligibility and opt-in context. WhatsApp is the execution channel for eligible communication.
WhatsApp is not a chatbot.
C17 does not position Pika as a conversational AI chatbot, live two-way customer-service or agent-inbox product.
WhatsApp is not an unapproved free-form messaging channel.
Pika WhatsApp outbound communication operates in eligible approved-template context and makes no capability claim that bypasses template-approval requirements.
WhatsApp is not an outcome guarantee.
WhatsApp dispatch does not guarantee a particular delivery, read, response, conversion, sales or revenue result.
The role of WhatsApp is:
To execute approved-template communication for a defined audience and action context through WhatsApp Business API after relevant opt-in controls.
It is not: A chatbot or autonomous conversation engine.
Frequently Asked Questions
What is Pika WhatsApp?
Does Pika WhatsApp provide a chatbot or live customer service?
Does WhatsApp communication require approved templates?
Does Pika WhatsApp automatically choose the audience?
How does WhatsApp work with Campaign Manager and Journey Manager?
Is WhatsApp opt-in managed through the same Email/SMS preference screen?
Does Pika guarantee WhatsApp template approval?
Does WhatsApp delivery guarantee that the customer reads the message or converts?
Define the audience.
Check opt-in and template context.
Execute WhatsApp communication under control.
Let's explore how Pika WhatsApp brings together Audience Manager context, Campaign Manager or Journey Manager actions, WhatsApp Business approved-template requirements and available opt-in controls within controlled WhatsApp communication.
Pricing is tailored to your requirements and scope of use.