Bow Chat·policy-guide·Version 1

Safe use of a WhatsApp Web connection

Use a linked WhatsApp number for consented, human-scale service work without treating it as a way around WhatsApp messaging rules.

The rule

A WhatsApp Web connection brings an existing business number into Bow Chat. It does not turn the consumer or Business app into an unrestricted messaging API, and it does not bypass WhatsApp policy.

Use this channel for consented, human-scale operational communication. Use the WhatsApp Business Platform for planned campaigns, approved templates, and higher-volume automation.

Appropriate use

Continue an existing patient, customer, or partner conversation.
Send a low-volume operational update the recipient expects.
Work established WhatsApp groups from a shared team inbox.
Let a human review sensitive or unusual messages before sending.

Do not use it for

Purchased, scraped, inferred, or stale contact lists.
Unsolicited marketing or repeated contact after no response.
High-volume automated sends intended to avoid template approval or Meta charges.
Any recipient who opted out, blocked the number, or objected to the message.
Claims of guaranteed delivery or guaranteed protection from account restrictions.

WhatsApp's published messaging guidelines prohibit unofficial clients, bulk messaging, auto-messaging, repeated unwanted contact, and spam. Its help centre also states that unauthorised automation or bulk messaging can lead to enforcement.

Operational safeguards

Record the purpose and the recipient's consent or other approved communication basis before sending.
Keep operational and marketing audiences separate.
Use one sender identity consistently for the doctor, clinic, or service team.
Serialize sends per connected number and keep conservative rate limits.
Stop immediately on opt-out, block, quality warning, disconnection, or policy error.
Monitor the linked session and require a human reconnect when it drops.
Keep a deduplication key so reconnects and retries cannot send the same business event twice.

Delivery expectations

sent means Bow Chat handed the message to the channel path. delivered and read are stronger states when the provider reports them. failed is terminal for that attempt. A linked Web session can disconnect, the provider can delay receipts, and WhatsApp can restrict the number.

If another channel is configured as a fallback, use the delivery and fallback guide. Never use an automatic fallback to defeat an opt-out or policy decision.