Click to WhatsApp (CTWA)

Click to WhatsApp (CTWA) is a link or button that, when clicked, opens a direct conversation with a WhatsApp number. In plain terms: it's the fastest way for a customer to message you without having to save your number, search for your contact, or copy anything. It's used on websites, social media, ads, or even on a physical QR code, and it's one of the most effective tools for selling and providing support via WhatsApp.

Why does it matter to an SME?

Because 90% of customer service messages in Latin America go through WhatsApp. If your business doesn't have a well-placed CTWA, you're forcing the customer to go through many steps: copy the number, open the app, paste it... and by then you've already lost the sale. With a single click, the customer lands directly in your chat with a pre-filled message (like "Hello, I saw your website and wanted to ask something"). This reduces friction and increases the likelihood that they'll write to you.

Concrete example

Imagine a grocery store that has a page with the weekly menu. If the customer has to copy the number and type "hey, do you have tomatoes?", they might not do it. But if there's a green button that says "Order via WhatsApp" that opens the conversation directly with the message "Hello, I want to place an order", the customer just taps it and that's it. That's CTWA. It's also used on Instagram: the WhatsApp button on the profile is basically a CTWA.

Common mistakes

• Not using a pre-defined message: if the chat opens empty, the customer has to think about what to write. Better to have a greeting that provides context.
• Placing the CTWA somewhere it can't be seen: if it's hidden in the footer, it's useless. It needs to be at the top, in the hero, or on each product.
• Not linking the number with the correct format: the link must be https://wa.me/549XXXXXXXXXX (with country code and no spaces). Otherwise, it won't open.
• Leaving it without follow-up: if the customer writes and no one responds, the CTWA is useless. That's where chat management comes in.

How is a CTWA created?

1. 1Write the link https://wa.me/<your_number> (with country code, without the 15 in Argentina).
2. 2Optional: add ?text= to set a predefined message (e.g., https://wa.me/5491112345678?text=Hola%2C%20quiero%20info).
3. 3Place that link on a button, image, or QR code.
4. 4Test that it works on your phone and on a friend's.

If you already have a CTWA and receive many messages, tools like Wando (wando.online) can help you respond faster with AI that suggests replies and that your team approves with one click. But that's another level: CTWA is just the first step.

How it's used in practice: the complete customer journey

Imagine a clothing store in Córdoba that sells through Instagram. It posts a story with a new t-shirt and, in the description, puts the CTWA link with the predefined message "Hi, I saw the t-shirt in the story and I want to know the price." The customer taps the button, lands directly in the WhatsApp chat with that message written, and only has to press send.

On the other side, the owner receives the message in the WhatsApp Business app (or in a tool like Wando) and replies with the price, size, and payment method. If the store uses Wando, the AI suggests a reply like "Hi! Yes, the t-shirt is $15,000 and we ship nationwide. Should I reserve it for you?" and she approves it with one click. That way she serves twice as fast without losing control.

CTWA is not just a button: it's the entry point of an entire customer service system. Without the link, the customer doesn't arrive. With the link but without a quick response, the sale is lost. The magic is in the link and chat management working together.

What CTWA is confused with and how it differs

CTWA is often confused with two things: the chatbot and the WhatsApp Business API. They are different things, although sometimes they work together.

CTWA is just the link that opens the chat. The chatbot is a program that automatically responds within that chat. CTWA attracts, the chatbot serves. You can have CTWA without a chatbot, or a chatbot without CTWA (for example, if the customer already has you saved).

The WhatsApp Business API is Meta's official platform to connect your WhatsApp to management tools (like Wando) and do things that the regular app doesn't allow: multi-agent, statistics, campaigns. CTWA can work with the regular app, but if you want to scale, you need the API.

In short: CTWA is the door, the chatbot is the receptionist, and the API is the building's management system. They complement each other, but they are not the same.

What happens if you don't use CTWA: the cost of friction

If you don't have a CTWA, the customer who finds you on a website or on Instagram has to do extra work: copy your number, open WhatsApp, paste it, write a message. Each extra step is an opportunity for them to abandon. In an internal study we did, we saw that friction in communication is the main cause of lost sales in SMEs, more than price or quality.

The concrete consequence is simple: fewer inquiries, fewer sales. A customer who has to copy a number is a customer who probably won't do it. And if they do, they arrive in a worse mood, because they already had to make an effort.

Also, without CTWA you lose the opportunity to capture context: the predefined message gives the customer a starting point and tells you where they came from (web, social network, ad). That data is gold for measuring your campaigns.

How CTWA relates to Meta's official API

Common CTWA uses the wa.me link, which is free and doesn't require the API. But if you want to go further, Meta's WhatsApp Business API is the next step. With the API, you can receive messages that arrive via CTWA in a shared inbox, assign them to different agents, use approved templates for campaigns, and pull statistics.

Tools like Wando connect to that API and give you a simpler interface than Meta's console. But beware: the API is not free. Meta charges for business-initiated conversations (not for customer-initiated ones, which are free). Prices vary by country and change over time, so it's always a good idea to check the official documentation.

In practice, many businesses start with simple CTWA and then, when volume grows, migrate to the API with a tool like Wando. CTWA remains the same, but the management on the other side changes.

When NOT to use CTWA (and what to do instead)

CTWA is not a magic solution for everything. If your business doesn't have the capacity for fast responses, a CTWA can be counterproductive: the customer writes to you, nobody answers, and the experience is worse than if there were no button. In that case, first solve chat management (hire someone or use an AI tool like Wando) and then add the CTWA.

It's also not advisable to use CTWA as the only channel if your customer prefers phone or email. For example, in complex B2B services, a form with more context can be better than a direct chat. CTWA is ideal for simple inquiries and quick sales, not for long qualification processes.

And beware of overuse: if you put CTWA everywhere without a strategy, the customer feels chased. Use it where it makes sense: on the product page, in the contact section, in a specific ad. Measure what works and adjust.

Common mistakes of those who are just starting to understand CTWA

The first is thinking that CTWA is enough. The link opens the chat, but if no one responds quickly, the sale falls through. CTWA is just the doorway; the service is what closes the deal.

The second is using the wrong link format. The number must include the country code and omit the 15 (in Argentina). If you get the format wrong, the link won't open or will open the wrong contact.

The third is not using a predefined message. An empty chat forces the customer to think about what to write, and that's friction. A message like "Hi, I want info" makes everything easier.

The fourth is not tracking. If you don't know how many clicks your CTWA receives or where they come from, you can't measure if it works. Use UTM parameters or analytics tools to know which campaigns bring more conversations.

And the fifth, the most costly: ignoring that CTWA scales poorly without the API. With the common app, one phone, one agent. When volume grows, you'll need the API and a tool like Wando to avoid drowning in messages.