# FAQs and Troubleshooting

If you encounter issues with Content Templates, use the following diagnostic tips to resolve common problems.

## FAQs

### Common terms and definitions

* **Content SID**: The unique SID that identifies a content template. A Content SID can be used only by asingle Twilio Account SID. It is a 34-character string that starts with `HX`.
* **Content variables**: The variables used to substitute in values at run time. Variable samples are typically required at creation if a template has variables.
* **Content types**: Twilio's omnichannel representation of rich content. Most content types can be used across channels without customization. In a few cases, components that a content type defines for one channel make the template incompatible with another channel that normally supports the type.

### My template was submitted to WhatsApp and rejected. What should I do?

See the [WhatsApp Message Template Approvals & Statuses](/docs/whatsapp/tutorial/message-template-approvals-statuses) article for a summary of the WhatsApp template approval guidelines and common rejections reasons.

### How can I format text?

Use the following formatting options when inputting a string:

* `~strikethrough~`
* `***bold**`
* `*italics*`

### Are emojis supported?

Yes.

* On macOS, press `Control` + `Command` + `Space`  to open the emoji picker.
* On Windows, press `Windows` + `;`  (semicolon) or `Windows` + `.`  (period).

### How do I use a newline in my templates?

Press `Enter` or `Return` to start a new line, just as you would in a text editor.

### Can I include multiple languages in a single template?

No. Each Content Template supports only one language.

### Are there any limitations around URLs?

URLs must be valid, publicly accessible, and not contain whitespace characters. For WhatsApp, the URL up to the domain name must be static.

### Do templates created in the "WhatsApp Templates" area of Console appear within the Content Editor and API?

Templates created in the Console under **WhatsApp Templates** are incompatible with templates created using the Content API or Content Editor, known as "Content Templates". Only Content Templates can be sent using the `ContentSid` and `ContentVariables` parameters.

You can request to have your existing WhatsApp Templates duplicated and converted to Content Templates by [contacting Twilio Support](https://help.twilio.com/). This is a manual task and will be serviced on a first come, first served basis.

### Can I still use my previously created `twilio/buttons` now that they've been deprecated?

Yes, `twilio/buttons` that were previously created will still continue to work on WhatsApp and FBM. However, we encourage you to create new `twilio/call-to-action` and `twilio/quick-reply` templates to take advantage of template delivery on future channels as they become available. `twilio/buttons` templates will not support future channels.

### How do I see all templates?

Make a `GET` request to the following endpoint: `https://content.twilio.com/v1/Content?PageSize=1000` (adjust page size as needed).

### Can I use the Content Templates without adding senders to a sender pool or specifying a Messaging Service in the From field?

Yes, you can instead specify a `MessagingServiceSid` field and a WhatsApp sender `From` field in the Twilio Programmable Messaging send request. With this workaround, the WhatsApp Sender does not need to be in the Messaging Service sender pool and a unique From can be used for each message. However, a Messaging Service must still be created and specified in the Programmable Messaging request. An example send request would be structured as follows:

```bash
curl -X POST https://api.twilio.com/2010-04-01/Accounts/ACXXXXXXXXXXXXXXXXXXX/Messages \
-u $TWILIO_ACCOUNT_SID:$TWILIO_AUTH_TOKEN \
-H 'Content-Type: application/x-www-form-urlencoded' \
-d "To=whatsapp:+15551234567" \
-d "MessagingServiceSid=MGXXXXXXXXXXXXXXXXXXX" \
-d "From=whatsapp:+15559991111" \
-d "ContentSid=HXXXXXXXXXXXXXXXXXXX" \
-d 'ContentVariables={"1":"ABC123"}'

```

## Limitations of the Content API

* **Personally identifiable information (PII)**: PII is not supported in Content API templates. However, PII can be passed in content variable parameters sent via the Programmable Messaging API.
* **Templates limits**: The Content API supports an unlimited number of templates, however, WhatsApp limits users to 6000 approved templates.
* **List**: The top-most heading in list are not independently configurable.
* **Media**: Media hosted on Google Drive is not supported. Google Drive links render a preview page rather than the media file itself. The Content API requires a media URL that resolves directly to the image so that it can download the file during sample submission.