What is a WhatsApp call-to-action button template

A template with a call-to-action (CTA) button is a message pre-approved by WhatsApp that includes a button with a clear action: for example, 'View offer', 'Call', or 'Visit site'. It is used within the official WhatsApp Business API to send proactive messages to your contacts, that is, messages that are not a response to a previous query. The button must be linked to a URL or a phone number, and the entire template must be approved by Meta before use.

Why it matters to an SME

If you have a business, you surely want to send offers, reminders, or news to your customers without waiting for them to write to you first. WhatsApp is the most used channel in Argentina and Latin America, and a template with a CTA button allows you to start the conversation legitimately and with a direct call to action. Without this, any mass message you send can be blocked or marked as spam, and your number can be suspended.

How it is used in practice

1. 1Create the template in the Meta panel (or from a tool like Wando that connects to the API).
2. 2Choose the button type: it can be 'Call' (linked to a number) or 'Visit site' (linked to a URL).
3. 3Write the message: it must be clear, brief, and without misleading promises.
4. 4Send it to Meta for review; it can take up to 48 hours to be approved.
5. 5Once approved, use it to send messages to your contacts, always respecting reasonable hours and frequency.

Concrete and complete example

Imagine you have an online clothing store. You create a template that says: 'Hello {{1}}! This week we have 20% off on the entire summer collection. Tap the button to see the offers.' The button is 'View offers' and leads to https://yourshop.com/offers. You send it to 200 contacts who gave you their number before. Result: 30 people tap the button, 10 buy. Without the template, you could not have started that conversation.

What it is confused with and how it differs

It is confused with session messages (those you reply to within 24 hours from the customer's last interaction). The key difference: session messages don't need a template and can have any text; templates are for starting conversations after those 24 hours or for scheduled messages. It is also confused with quick reply buttons, which are only for choosing options within a conversation, not for leading to an external action.

Common errors

• Not asking for permission before adding a customer to your list: that generates blocks and reports.
• Using shortened URLs that Meta cannot verify: it can reject the template.
• Writing texts that are too long or with exaggerated promises ('You won a trip!') that violate Meta's policies.
• Sending the same template to everyone without segmenting: the response rate drops and you can be marked as spam.
• Not reviewing results: if no one taps the button, the template is useless and you have to try another one.

What happens if you don't take it into account

If your SME doesn't use templates with a CTA button, you will depend only on response messages, which greatly limits your reach. You can't notify about a promo, a schedule change, or an event without the customer writing to you first. Also, if you try to send mass messages via the API without approved templates, Meta can restrict your number and you lose the ability to write to your customers.

How it relates to Meta's official API

Templates with a CTA button are a native feature of the WhatsApp Business API (WhatsApp Cloud API). Meta requires them for any proactive message. The approval process can take up to 48 hours, and conversation prices vary by country; I recommend checking Meta's official documentation to know current costs. Tools like Wando connect to this API and allow you to manage templates from a simple inbox, without programming.

When it does NOT apply

It does not apply to messages within the 24-hour window: there you can write freely, without a template. It also does not apply if the button does not lead to a useful action (for example, a 'See more' button that goes nowhere, that is spam). And if your business does not have a clear website or contact phone number, a quick reply button or a simple message might suit you better.

How it is set up in practice

To set it up from the Meta panel, you go to WhatsApp Manager > Account tools > Message templates. There you tap 'Create template', choose the category (Marketing, Utility, or Authentication) and in the content field you add the text. In the 'Add buttons' section, you select 'Call to action' and choose the type: 'Visit website' or 'Call phone number'.

If you use Wando, the flow is shorter: you go to the Templates section, tap 'New template', write the message, and choose the button with its destination. The platform sends it to Meta for you and notifies you when the status changes to 'Approved'. You do not need to touch the Meta panel at all.

The key permission you need to have active is sending proactive messages, which is granted when you verify your business number in the API. Without that verification, you cannot create or use templates.

How to tell it went well

The first thing you look at is the template status: it must say 'Approved', not 'Pending' or 'Rejected'. You can see that both in the Meta panel and in the Wando template list.

When you send it, the message must arrive with the button visible and working. Test it with a test contact: tap the button and verify that the URL opens in the browser or that the call goes out to the correct number.

If something doesn't work, the review order is: first the template status (whether it's approved), then the button type (whether it's website or call), and finally the destination (whether the URL is well written and public). 90% of problems are a broken URL or a template stuck in review due to a formatting error.

What changes depending on business size

In a one-person business, the CTA button template is a manual tool: the owner sets it up once, sends it to their contact list, and then responds to inquiries that come in through the button. There's not much more to it: it's configured once and used on a case-by-case basis.

With fifteen people, the game changes. You need the template to be used in a coordinated way: who approves it, who sends it, how the list is segmented, and how follow-up is done on those who tapped the button. That's where multi-agent comes in: several operators see the same inbox and each one handles the conversations generated by the template.

Frequency also changes. A small business sends one promo per month; a larger one may need several approved templates in parallel for different campaigns and segments. Template management stops being a formality and becomes a process.

What Meta's official documentation says and what it doesn't

Meta's official documentation defines the hard rules: what button types exist, how a template is structured, character limits, and the approval process. That's non-negotiable and any platform using the official API complies with it equally.

What is left to each platform's discretion is how all of that is managed: the interface for creating templates, the tools for segmenting contacts, performance statistics, and how it integrates with the rest of the business. Meta does not tell you how to track a campaign; that is resolved by each tool.

Another thing not in the official documentation is strategy: what text to use, what time to send, how often. Meta only regulates format and content, it does not tell you how to sell better.

Second-order questions

Once you understand the concept, finer questions remain. For example: what happens if Meta rejects the template? The answer is that you edit it and send it again; rejection is not final and does not affect your number.

Another: do templates expire? They have no expiration date, but Meta can deactivate those that are not used for a long time. If an old template is no longer active, you recreate it.

There is also the question of costs: templates themselves are not paid for, but each conversation initiated with a template has a cost per country, according to Meta's rate. That cost varies and it is advisable to check the official documentation.

And one that always comes up: can I use the same template for different audiences? Yes, but with variables like {{1}} you can customize the name or product, which improves response without having to create a new template for each segment.