Source
Channels & personalisation — found from sitemap — Customer.io
Checked for Customer.io on 1 Oct 2026
- Page
- https://docs.customer.io/messaging/channels/whatsapp/send-whatsapp/
- Checked
- 1 Oct 2026, 09:52 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:09847d0ffda81c41b9b092cc5982f5c935f5f7cfaebab16f78ae047c758f3daa
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Whatsapp send workflow Report an error
“After you've enabled WhatsApp support and created WhatsApp-approved templates, you can send WhatsApp messages in any automation or broadcast.”
-
Whatsapp sender selection Report an error
“Select a WhatsApp approved sender in the From field. If you only have one sender phone number, it’s already selected for you.”
-
Twilio whatsapp Report an error
“If you send WhatsApp messages using Twilio, and you select a sender that is not WhatsApp approved, your messages will fail.”
-
Whatsapp liquid personalization Report an error
“Fill in the templated variables for your message. You can use liquid in these fields to personalize your message.”
-
Whatsapp media header public URL Report an error
“If your template has a media header (image, video, or document), you must host your media publicly and provide a public URL to the file in Customer.io.”
-
Whatsapp localization Report an error
“WhatsApp supports different languages, but only one language per template. If you want to translate your WhatsApp messages, you’ll need to create a separate template for each language.”
-
Whatsapp session types Report an error
“In general, WhatsApp messages sent through Customer.io are business-initiated.”
-
Whatsapp inbound Report an error
“Customer.io supports inbound WhatsApp messages, so you can respond to your audience when they reply to or message you. Inbound messages can trigger automations, add people to segments, and mark your messages as replied.”
1 fact read from this page is not shown because it could not be confirmed on the page as captured.