Bring concise, time-sensitive communication
to the SMS channel
inside Pika's controlled action chain.
Pika SMS is the communication channel through which audience context defined in Audience Manager can be used within controlled actions managed by Campaign Manager or Journey Manager.
Before delivery, IYS status, opt-out state and applicable communication-time controls are evaluated separately within SMS permission and delivery-eligibility context.
What is Pika SMS?
Pika SMS is one of Pika's confirmed communication channels for using concise, time-sensitive text communication within controlled campaign or journey context.
The role of SMS is not to analyze customers, independently select the audience or manage journey flow. Those contexts are created through Pika's relevant intelligence, Audience Manager, Campaign Manager and Journey Manager layers.
SMS answers one central question:
“How is this defined communication executed through the SMS channel after permission and action controls?”
For relevant commercial SMS communication, pre-dispatch IYS status, opt-out state and applicable communication-time controls form part of delivery-eligibility evaluation.
SMS: is the communication channel.
Pika: is the surrounding chain of understanding, decision, permission and measurement.
Put SMS in the right place inside Pika's decision chain.
Pika is more than bulk SMS software. SMS 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 the action is executed. SMS is one technical communication channel for that eligible action.
SMS does not create the decision.
It is the communication channel for a defined decision.
Concise Messaging Channel
Execute concise, direct text communication through SMS within controlled campaign or journey context.
Audience Context
Use the audience defined in Audience Manager as upstream customer context for the SMS action.
Permission & Time Control
Evaluate IYS, opt-out and applicable quiet-hours controls within SMS delivery-eligibility context.
Measurable Delivery Outcome
Evaluate available SMS delivery-outcome or status data within Analytics & Reporting context.
Use the channel appropriately for concise, time-sensitive communication.
SMS is a channel that can be used when communication requires concise, direct text rather than rich visual content.
Time-sensitive campaign communication, a short reminder or a defined journey step can be examples of SMS context.
This does not mean SMS is the “best” or “fastest” channel for every customer communication.
SMS: is a concise text channel.
Use context: depends on the campaign or journey objective.
Channel selection: is not a universal performance ranking.
The right channel depends on communication context.
SMS 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 SMS channel is not to independently segment customers or choose the “best” recipient group.
An SMS action inside Campaign Manager or Journey Manager can use the relevant audience context within controlled communication.
Audience Manager: “Who belongs in this audience?”
SMS: “Within which action context will eligible SMS communication reach this defined audience?”
Audience truth is not created by the SMS channel.
Campaign SMS
A campaign context where a defined audience and prepared short-message content can be used in a controlled SMS action through Campaign Manager.
Journey SMS Step
A journey context where SMS can be used as a channel action inside conditions, sequence and wait logic managed by Journey Manager.
From Opportunity to SMS Action
An action context where a commercial opportunity evaluated in Daily Opportunities can reach the SMS channel after user decision, actual audience definition and permission controls.
Campaign Manager manages the campaign. SMS carries the communication.
Campaign Manager manages defined audience, content, channel, timing and pre-send controls within the same campaign context.
When SMS is the selected channel, prepared short-message content can be used within controlled campaign execution.
The availability of SMS does not mean a campaign starts automatically.
Campaign Manager: manages campaign context, timing and controlled delivery.
SMS: is the selected communication channel.
The campaign decision and SMS execution do not perform the same product role.
SMS 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.
SMS can be used as one configured communication-channel action inside that flow.
The SMS channel does not independently determine behavioral conditions, sequence, waits or the next step.
Journey Manager asks: “What is the next step and under which condition should it progress?”
SMS asks: “Is SMS the communication channel used at this step?”
SMS is not an autonomous journey-trigger engine.
It is a channel action that can be used inside a journey.
Use available customer context. Do not let the SMS channel reinvent the customer.
SMS content is prepared for concise text communication and can be used within campaign or journey context.
Available personalization fields based on existing customer data can be considered during message preparation.
Personalization does not mean the SMS channel creates new information about the customer or independently chooses the audience.
Customer context: comes from Pika's data and intelligence layers.
Audience: is defined through explicit rules.
Message content: is prepared and used under user control.
SMS: is the execution channel for the communication.
The channel is not the source of customer truth.
Do not execute SMS action independently from permission and communication-time context.
For relevant commercial SMS communication, a pre-dispatch IYS status check forms part of communication-eligibility evaluation.
Available opt-out state can cause SMS communication to be evaluated for suppression.
Documented commercial-message quiet-hours control helps applicable communication-time restrictions participate in the delivery process.
IYS: is a control input about available consent state.
Opt-out: is a suppression signal.
Quiet-hours: is a communication-time control.
SMS: is the execution channel used after those controls.
These technical controls do not mean Pika or the SMS channel automatically guarantees every legal obligation.
SMS action does not replace permission controls.
Move controlled SMS action into delivery through operator-gateway context.
SMS communication in Pika moves into operator-gateway delivery context after the relevant action and permission controls.
This channel layer does not create the campaign or journey decision. It is the technical dispatch path for defined SMS communication.
Passing a delivery request into operator-gateway context does not guarantee immediate or definitive delivery to the customer's device.
Campaign / Journey: defines the action.
Consent controls: evaluate delivery eligibility.
SMS channel: moves communication into operator-gateway dispatch.
Delivery outcome: occurs after execution.
Dispatch is not an outcome guarantee.
After SMS action, evaluate available delivery outcomes within measurement context.
SMS communication does not end with the delivery request. Available delivery-outcome or status context can become part of campaign evaluation.
That outcome helps explain what happened in the technical communication-delivery process.
A delivery outcome does not by itself prove that the customer read the message, took action or produced a commercial conversion.
SMS: produces available delivery-outcome context.
Analytics & Reporting: evaluates that outcome together with campaign, audience and other measurement context.
Delivery outcome: is measurable operational context.
Customer behavior: is a separate evaluation question.
Put SMS in the right place.
SMS is not Customer Intelligence.
Customer Intelligence calculates customer behavior and value context. SMS is one channel through which controlled communication based on that context can be executed.
SMS is not Audience Manager.
Audience Manager defines the actual audience through explicit rules. SMS does not independently choose the audience.
SMS is not Campaign Manager.
Campaign Manager manages audience, content, channel, timing and controlled-delivery context. SMS is one selected execution channel.
SMS is not Journey Manager.
Journey Manager manages conditions, sequence, waits and action flow. SMS is a channel action that can be used inside a journey.
SMS is not Consent Management.
Consent Management evaluates available permission and opt-out context. SMS is the execution channel for eligible communication.
SMS is not a guarantee of “instant delivery.”
Operator-gateway dispatch does not guarantee delivery to the customer's device within a particular time or with certainty.
SMS does not guarantee visibility or reading.
C16 makes no performance claim that the customer will necessarily see, read or act on an SMS.
SMS is not an outcome guarantee.
SMS delivery does not guarantee a particular conversion, sale, revenue or campaign-performance outcome.
The role of SMS is:
To execute concise communication for a defined audience and action context through the SMS channel after permission and time controls.
It is not: A replacement for Pika's decision layers.
Frequently Asked Questions
What is Pika SMS?
Does Pika SMS automatically choose the audience?
How does SMS work with Campaign Manager and Journey Manager?
Does Pika check IYS status before SMS delivery?
Does SMS communication include opt-out and communication-time controls?
Does Pika SMS guarantee instant or definitive delivery?
Which SMS outcomes can be measured?
Does SMS delivery guarantee that the customer reads the message or converts?
Define the audience.
Apply permission and time controls.
Execute SMS communication under control.
Let's explore how Pika SMS brings Audience Manager context, Campaign Manager or Journey Manager actions and Consent Management controls together through the SMS communication channel.
Pricing is tailored to your requirements and scope of use.