Configured a business WhatsApp number, but the chosen scenario only offers email? Channel support depends on the automation itself. Connecting a number does not extend every scenario to that channel.
Compare supported combinations
| Scenario | SMS | ||
|---|---|---|---|
| Abandoned cart | Yes | Yes | Yes |
| Welcome after signup | Yes | No | No |
| First purchase | Yes | Yes | Yes |
| Winback | Yes | Yes | Yes |
| Product replenishment | Yes | Yes | Yes |
| Viewed product | Yes | No | No |
| Back in stock | Yes | No | No |
| Price drop | Yes | No | No |
Web Push is not a channel for these automations. Its availability elsewhere in the product does not change this table.
Check each channel's setup
After choosing a scenario and store, the panel displays supported channels and missing configuration.
Email needs a ready sending domain and business details. WhatsApp needs the appropriate business number and a supported, approved marketing template. SMS needs an active store sender, a supported number and available balance. Options can also depend on the account role.
Keep consent scopes separate
Email consent belongs to a contact base, WhatsApp consent to a business number, and SMS consent to a store. An address or phone alone is insufficient. Check the recorded consent.
A WhatsApp cart automation can offer email when WhatsApp consent is missing. Valid email consent is still required. The branch is chosen when due; delivery failures do not switch the channel.
First and second steps differ
The second step follows a first email. Do not assume every initial channel can be combined with every follow-up channel.
Read the specific form and its messages. Adding a sender or editing a template cannot unlock a combination the scenario does not offer.

