Find clear answers to the core questions that come up when evaluating Pika.

Pika is a Customer Intelligence & Omnichannel Marketing Platform that brings customer, product and sales data together to identify commercial opportunities and turn them into controlled, measurable omnichannel actions.

Pika is not positioned as a traditional CRM for tracking sales opportunities, customer conversations or sales-representative activity. It uses existing customer, product and transaction data within intelligence, opportunity, audience and controlled marketing-action context.

No. Email, SMS and WhatsApp are Pika's communication execution channels. The platform begins with understanding customer and product data, creating commercial opportunity and decision context and then moving into controlled action.

Pika can be evaluated by organizations that want to connect customer, product and transaction data to marketing decisions, make commercial opportunities visible and turn that context into controlled omnichannel action. C21 does not claim a required company size, industry or customer count.

Pika's core data context consists of customer, product and transaction data. The exact fields and data scope required depend on the usage scenario and are clarified during integration evaluation.

Yes. Excel and CSV are among Pika's verified data-intake paths. Customer, product and transaction data can be imported using an appropriate file structure.

Yes. Pika's documented REST Ingestion API can be used for programmatic data ingestion. API access includes X-API-Key context, while X-Idempotency-Key is used in the context of controlling repeated requests.

C21 makes no such claim. Systems such as CRM, ERP, POS, e-commerce or data warehouses can be source-system categories; actual integration scope depends on the API, file flow and data contract being used.

Customer Intelligence is Pika's intelligence layer for calculating customer behavior, value and purchase context from data so customers can be evaluated more meaningfully.

Product Intelligence is Pika's intelligence layer for evaluating products not only as catalog records, but through their commercial meaning, purchase behavior and relationships with other products.

Pika 360 is a Pika view for evaluating customer context together with relevant intelligence and commercial-evaluation outcomes. It is not itself a campaign or communication channel.

Daily Opportunities is Pika's decision layer for making evaluable commercial opportunities visible from calculated customer, product and transaction context. It presents opportunities for user evaluation and does not autonomously send communication.

Audience Manager manages the actual audience definition through customer data, transaction or behavioral context and explicit rules. An opportunity list or communication channel is not itself audience truth.

Content Studio is Pika's content layer for preparing visual Email content through drag-and-drop composition, modular blocks, templates, personalization fields and preview.

Campaign Manager manages defined audience, content, channel, timing and pre-send controls within one campaign context. Journey Manager manages a multi-step customer flow consisting of conditions, branching, waits and action steps.

Pika's public product model makes no such autonomous-delivery claim. The audience is defined through rules, campaign or journey action is managed in the relevant product layers, permission and delivery controls apply and final decision remains under user control.

Pika's confirmed public communication channels are Email, SMS and WhatsApp. Push is not marketed by C21 as an active public capability.

Email is an execution channel for richer visual communication, SMS for concise and time-sensitive text communication and WhatsApp for eligible approved WhatsApp Business template communication. Channel selection is not a universal performance ranking.

Yes, but telemetry varies by channel context. Available Email context can include delivery, bounce, open, click and unsubscribe, while available SMS and WhatsApp delivery-outcome or status context can participate in measurement. Analytics & Reporting evaluates these outcomes together with relevant campaign and audience context.

No. A technical delivery outcome does not guarantee that the customer will read, click, reply, purchase or produce a particular conversion or revenue outcome.

No. Audience Manager answers “who?” Consent Management evaluates how available consent, IYS and opt-out context affects communication eligibility. Audience membership does not replace consent controls.

No. Pika's current public preference-update flow covers Email and SMS preferences. WhatsApp opt-in is not managed through that same public checkbox form; WhatsApp opt-in context can come from separate webhook or import flows.

Verified public security context includes role-based access control (RBAC), masked communication-data presentation in relevant interfaces and API-key access control in documented API flows.

C21 does not market SOC 2, ISO 27001, SAML / SSO or specific encryption and physical tenant-isolation capabilities as public product claims without verified evidence.

Pika Pilot is Pika's AI-assisted layer that uses customer, product and opportunity context calculated by Pika to help accelerate campaign preparation and content drafting.

No. Pika Pilot does not invent a customer or opportunity and turn it into source truth. AI uses customer, product and opportunity context calculated by Pika to provide explanation, drafting and creation assistance.

No. AI-generated drafts and suggestions remain under user review. Audience, campaign, journey, consent and delivery controls are managed in separate product layers, and the final decision remains with the user.

Pika's documented AI-preparation boundary excludes direct identifiers such as TCKN, raw phone numbers and full names from LLM prompt tokens. This does not mean no personal data exists anywhere in Pika or that the product is absolutely “Zero-PII.”