If an outgoing message to WhatsApp returns a 63016 error code, this means an issue was found with the message you sent. This guide covers the following topics for diagnosing and resolving your issues:
Please start at the top, and walk through each of the troubleshooting steps as you work your way down the page.
Template vs Session messages
WhatsApp divides messages into two different types: Template messages and Session messages.
- Template messages: Outbound messages sent via Twilio that use one of the pre-approved templates. These are generally unsolicited transactional messages (delivery alerts, appointment reminders, etc.) sent to users who have opted in to receive messages from you.
- Session messages: All incoming messages, or outgoing replies to these messages within 24-hours. A messaging session starts when a user sends your application a message, and lasts for 24 hours from the most recently received message. Session messages do not need to follow a template, and can include media attachments.
Any messages sent to a destination that has not responded to you in at least 24-hours will need to be a Template message, and follow one of the pre-approved messaging patterns.
If you have confirmed that your response is outside of the 24-hour session window, continue to Review your message and templates. If you received this error within the 24-hour session window, please Escalate to Twilio Support.
Review your message and templates
Approved WhatsApp templates can be seen by clicking an enabled phone number on the WhatsApp Senders page in Console.
Please verify the message you're attempting to send matches an approved template on the WhatsApp phone number. To compare your message and the approved template, you can use a service like Diffchecker (diffchecker.com).
- Your message must follow the template as closely as possible, outside of any placeholders / values.
- Your From address must match the WhatsApp enabled phone number.
- WhatsApp does not permit using more than two consecutive (back-to-back) newline characters in a message, so ensure you are using no more than two newline characters consecutively within your message.
- Avoid including Windows-Style carriage returns (\r\n) in your originally submitted template or in your actual outbound messages, which can both often occur if copy/pasting your template or message content from a text editor like Microsoft Word.
- Instead, please only use Unix-Style (\n) newlines in your templates and outbound message bodies. If experiencing these 63016 errors and you've confirmed that your message content matches the approved template, you can try resubmitting the template by manually entering it in the Twilio Console, using only the "Enter"/"Return" key on your keyboard to automatically apply the correct (\n) newlines.
- Note that we do not show the actual \n or \r\n characters in the Console template view or template editor at this time, but if you see text on separate lines in those views, this indicates a newline character is encoded in the actual template that is sent to WhatsApp(Meta).
- In general, you should not include any extra newline or space characters in your templates that you do not plan to send in your actual outbound messages. This often occurs when one of these characters is unintentionally added at the very beginning or end of your template submission (or outbound message), again likely from copy/pasting the text from an external editor.
If you have confirmed that your message matches the approved template, please Escalate to Twilio Support.
Escalate to Twilio Support
If you can rule out all of the above issues, Twilio's Support team can help investigate what went wrong with delivering your message(s). Please collect 3 or more examples of messages flagged with Error 63016 in your SMS logs from the last 24 hours, and include the following information:
- Message SIDs (If you have them)
- Sending channel endpoint address (from)
- Destination channel user address (to)
- Your Twilio project Account SID
- Timestamps of message attempts
- Name of the template(s) you were trying to match
When you have collected this information, please share it with our Support team.