63121: Error for Message sent with Utility Direct Send

Twilio couldn't send your WhatsApp Utility Direct Send message because the provider-side template name generated from the Content Template is already in use by a WhatsApp template that Utility Direct Send doesn't manage. Twilio can't reuse the existing template because it can't verify that the content or lifecycle matches the Utility Direct Send template.

• A template with the same provider-side name was created directly in WhatsApp Manager.
• Another application or integration created the WhatsApp template before Utility Direct Send attempted to create and manage it.

• In WhatsApp Manager, search for the conflicting provider-side template name and identify which system created it. Don't delete templates that production messaging uses.
• If you need to keep the existing WhatsApp template, duplicate the source Content Template in either console:
  • In Twilio One Console, go to Products & Services > Templates. Find the template, open its Actions menu, and select Duplicate template.
  • In the legacy Twilio Console, go to Messaging > Content Template Builder. Find the template, open its actions menu (⋮), and select Duplicate.
• Give the duplicate a distinct template name. The duplicate receives a new Template SID, which Utility Direct Send uses when it generates the provider-side template name.
• Copy the duplicate's Template SID and use it as the message request's ContentSid, then retry the send.
• If you can't identify the conflicting template or the error continues with the new ContentSid, contact Twilio Support and include the Account SID, WhatsApp sender, Message SID, and Content SID.

• Manage templates with the Content Template Builder
• Send templates created with the Content Template Builder
• Content API FAQs and troubleshooting