Solution building block

B2B

Business buyer first

WhatsApp-ready channel toggle

An operator can select intended channels and see what is ready versus waiting on credentials.

Used by the business or delivery team before customer-facing channels go live.

Included in: Growth, Professional

What the customer uses

A usable piece inside a launched package.

Email, SMS, WhatsApp, chat, booking, CRM, and document readiness matrix.

How it is produced

What powers it in the deployed product.

Provider toggles are stored during onboarding; live sends require verified credentials.

Done when

This is how you know the deliverable is complete.

Each channel has a readiness state.
Missing credential requirements are explicit.
No channel is represented as live unless configured.

Implementation guide

WhatsApp-ready channel toggle is a working building block inside a complete Lead OS solution. It exists so the business buyer can understand exactly what was created, how it is used, and how completion is verified.

Start here

Read the buyer outcome first.
Confirm whether the block is B2B internal or B2B2C customer-facing.
Review the delivered artifact and backend reality before using the example.
Run or inspect the live example on this page.

Implementation steps

Use the block inside a package workspace, not as a disconnected asset.
Match the block to the client success metric before presenting it as value.
If the block touches downstream customers, verify the copy, consent, routing, and escalation expectations.
If the block depends on live account access, use safe sample or managed-handoff mode until approved access exists.
Document the next operator action in the client delivery hub.

Operating workflow

Capture or inspect the input.
Produce the visible artifact.
Route the result to the correct business or customer-facing next step.
Measure the result against the acceptance criteria.
Improve the package workflow if the artifact does not advance the promised outcome.

If unclear or blocked

If the artifact looks like a sample, treat it as a demo until connected package data is present.
If the next action requires a client-owned account, do not represent it as live until approved access exists.
If the block does not map to the selected package outcome, return to the package delivery hub.
If the customer cannot tell what to do next, use the implementation steps and acceptance checklist before handoff.

Next milestones

Today: confirm the block exists and the acceptance criteria are visible.
This week: connect it to a package workspace or run a sample scenario.
This month: use reporting evidence to decide whether the surrounding package should be optimized, expanded, or bundled.

Channel	Configured now	Required to go live
Email	Selected in onboarding	Verified email provider account access
SMS	Toggle available	SMS provider account access and consent policy
WhatsApp	Toggle available	WhatsApp provider account access and approved templates
CRM	Toggle available	CRM API key saved in account access
Documents	Toggle available	Document provider or internal generation config

Channels are never represented as live until approved account access exists.

Loading…

Implementation steps

Use the block inside a package workspace, not as a disconnected asset.

Match the block to the client success metric before presenting it as value.

If the block touches downstream customers, verify the copy, consent, routing, and escalation expectations.

If the block depends on live account access, use safe sample or managed-handoff mode until approved access exists.

Document the next operator action in the client delivery hub.

If unclear or blocked

If the artifact looks like a sample, treat it as a demo until connected package data is present.

If the next action requires a client-owned account, do not represent it as live until approved access exists.

If the block does not map to the selected package outcome, return to the package delivery hub.

If the customer cannot tell what to do next, use the implementation steps and acceptance checklist before handoff.

Channel

Configured now

Required to go live

Selected in onboarding

Verified email provider account access

SMS

Toggle available

SMS provider account access and consent policy

Toggle available

WhatsApp provider account access and approved templates

CRM

Toggle available

CRM API key saved in account access

Documents

Toggle available

Document provider or internal generation config