What is Consent Management?
Consent Management is Pika's permission and preference-governance layer for helping evaluate available consent, IYS status and opt-out context before customer communication is executed.
Belonging to an audience does not mean permission to communicate. Reaching a channel action inside a campaign or journey also does not mean delivery occurs without consent checks.
Consent Management answers one central question:
Relevant Pika delivery flows can evaluate available permission and suppression context before communication execution.
Consent Management does not create the commercial opportunity. It brings permission eligibility into the communication-control process.
The right customer does not automatically mean permitted communication.
Customer Intelligence or Audience Manager can make a particular customer context commercially relevant. That customer being appropriate for a campaign does not mean current permission for the selected communication channel is also appropriate.
When consent context is separated from action, the target audience and customers who can actually be contacted can become confused.
Consent Management brings that distinction into the delivery decision.
“Who do we want to communicate with?”
“Can we communicate with this customer under this consent context?”
“What technical outcome did the eligible communication produce?”
The right audience does not replace consent checks.
Do not reduce the communication decision to one consent field.
Delivery eligibility can require evaluation of multiple control signals.
IYS Status
Where applicable to commercial communication, a pre-dispatch IYS status check can provide one input into consent evaluation.
Pika Opt-Out State
Central opt-out state held in Pika helps determine whether communication should be suppressed.
Email / SMS Preference
Customers can update Email and SMS preferences through the public preference-update flow.
WhatsApp Opt-In Context
WhatsApp opt-in is not managed through the same Email/SMS public form; context comes through separate webhook or import flows.
Channel & Delivery Context
Consent eligibility is not the same thing as actual delivery or provider outcome; channel execution is evaluated separately.
The role of Consent Management is not to produce one universal “consent yes/no” label, but to bring available permission context into the delivery decision.
Evaluate applicable consent state before delivery.
Within Pika's delivery process, IYS status for relevant commercial-communication context can be queried before communication execution.
The result can participate in delivery-eligibility evaluation, and ineligible communication can be suppressed.
An IYS check does not mean Pika independently defines the customer's commercial or legal truth.
provides a control input about available consent state.
uses that context during pre-dispatch eligibility evaluation.
Pika does not replace IYS. It brings IYS context into the communication-control process.
Do not reopen communication through a campaign rule after the customer has opted out.
Opt-out is an important suppression signal indicating that the customer does not want communication.
Pika's centralized opt-out state can be checked during delivery-eligibility evaluation.
A customer entering an audience, having an opportunity or reaching a journey step does not remove their opt-out state.
can establish a reason for communication.
can establish commercial context.
can be a permission signal requiring suppression.
Action logic does not replace opt-out control.
Manage Email and SMS preferences through a flow customers can update.
Pika's tokenized public preference-update flow supports customers updating their available Email and SMS communication preferences.
That public flow contains Email and SMS preference fields only.
C12 therefore does not position this page as a universal preference center for every channel.
EMAIL + SMS
WHATSAPP / PUSH
WhatsApp permission context comes from separate sources. Push consent does not exist.
Describe the public preference flow according to its actual channel scope.
Do not confuse WhatsApp opt-in context with the Email/SMS preference form.
WhatsApp is one of Pika's confirmed active communication channels.
However, the current public preference-update form does not contain a WhatsApp consent checkbox.
WhatsApp opt-in context can arrive through incoming webhook or import flows and is evaluated separately within the relevant communication process.
is an active communication channel.
is not the WhatsApp consent-management screen.
Being part of the same platform does not mean using the same consent-acquisition flow.
Permission to communicate does not mean the message will necessarily be delivered.
Consent Management evaluates communication eligibility from the permission perspective.
A customer having permission does not guarantee that their Email address or phone number is valid, that the provider will accept the message or that delivery will succeed.
Reachability, provider outcome and delivery telemetry are separate operational contexts.
“Is communication eligible from the permission perspective?”
“Can this customer technically be reached on the channel?”
“What happened to the delivery attempt?”
Do not interpret consent as a delivery guarantee.
Consent Management does not replace action products.
Audience Manager defines the target audience. Consent Management does not create the audience itself.
Campaign Manager manages audience, content, channel, timing and controlled-delivery context for a campaign.
Journey Manager manages multi-step conditions, waits and communication flow.
Consent Management helps evaluate available permission and suppression context during relevant communication execution.
WHO?
WHAT ACTION?
IS COMMUNICATION ELIGIBLE?
WHAT HAPPENED TO THE SEND?
Consent control is part of the action chain. It is not the entire action chain.
Pre-Dispatch IYS Check
Evaluate available IYS status before communication execution within relevant commercial-communication context.
Central Opt-Out Check
Use existing opt-out state in Pika as a suppression signal during delivery-eligibility evaluation.
Email / SMS Preference Update
Support customers updating Email and SMS communication preferences through the public preference-update flow.
WhatsApp Opt-In Context
Evaluate WhatsApp permission context through webhook or import sources separate from the public Email/SMS form.
Audience vs Consent
Do not confuse a customer belonging to the target audience with permission to communicate.
Consent vs Delivery
Evaluate permission eligibility separately from actual channel reachability and delivery outcome.
Related Platform Solutions
Apply consent controls. Do not present them as an automatic legal guarantee.
Pika provides technical controls that help use IYS status checks, opt-out suppression and available preference context during the delivery decision.
These controls support permission governance within commercial communication operations.
The presence of a software control does not mean an organization automatically satisfies every legal obligation.
helps implement permission and delivery controls.
separately manages its legal obligations, data sources and communication policies.
Do not position Consent Management as an “automatic legal compliance engine.”
Put Consent Management in the right place.
Consent Management is not Audience Manager.
Audience Manager defines the audience. Consent Management helps evaluate whether communication with that audience is eligible from the consent perspective.
Consent Management is not Campaign Manager.
Campaign Manager manages campaign operations. Consent Management brings pre-dispatch permission and suppression controls into action context.
Consent Management is not Journey Manager.
Journey Manager manages multi-step flow. Reaching a journey step does not remove consent controls.
Consent Management does not replace IYS.
Pika can include pre-dispatch IYS status in the control process. It is not IYS itself or a replacement for the underlying permission authority.
The public preference flow does not manage every channel.
The current public preference-update form covers Email and SMS preferences. WhatsApp opt-in comes from separate sources.
Consent Management is not reachability.
Permission to communicate does not mean a customer is technically reachable on the channel or that delivery will definitely succeed.
Consent Management is not an automatic legal-compliance guarantee.
Technical permission controls do not automatically satisfy every legal and operational responsibility of the organization.
Consent Management is not Push consent management.
Push consent does not exist and C12 does not market Push as an active consent channel.
The role of Consent Management is not:
To automatically declare communication “compliant.”
It is:
To make available consent and opt-out context a controlled part of the delivery decision.
Frequently Asked Questions
Choose the right customer. Check permission context. Execute communication under control.
Let's explore how Pika Consent Management brings pre-dispatch IYS status checks, centralized opt-out handling and the Email/SMS preference-update flow into the communication decision.
Pricing is tailored to your requirements and scope of use.