Welcome message in WhatsApp Business API: make it send only once per customer

If you're here, it's because you set up a welcome message in WhatsApp Business API and it keeps sending it to the same customer over and over again, in every conversation or even on every message. The good news: you didn't break anything serious or lose your account. It's a configuration problem, not a Meta failure, and in most cases the business owner can fix it from their provider's dashboard or from the tool they use to manage WhatsApp, without touching a single line of code. The bad news: there's no universal "send only once" button. The behavior depends on how the greeting is programmed, so you first need to understand what's triggering the message before rushing to turn it off.

What exactly this problem means

Unlike API errors with codes (the ones that return a number and a text), this is not an API error: it's a behavior of the flow you built. Meta's official WhatsApp API lets you send messages, but it doesn't decide for you when to send a greeting. That decision lives in the automation layer: it could be an auto-reply by schedule, a chatbot flow, an automation in Make, Zapier or n8n, or a function in your provider's dashboard. If that layer triggers the greeting every time a message comes in, the customer will see it repeated. The typical symptom is the same customer who writes "hi," then "do you have stock?," then "hello?" and receives three identical greetings. It's not that WhatsApp is failing: it's that the condition that triggers the greeting doesn't distinguish between the first message and the twentieth message.

Why it happens: the four usual causes

Almost all cases of a repeated greeting fall into one of these four causes. Identifying which one is yours saves you time, because each one is fixed in a different place.

• The greeting is tied to "every incoming message" instead of "the contact's first conversation." This is the most common cause: the automation triggers on any message, with no memory of whether it already greeted before.
• The greeting is sent again every time a new 24-hour window opens. The WhatsApp API allows you to reply within 24 hours of the customer's last message; if the flow interprets each reopening as a new contact, it greets again.
• You have two automations active at the same time: for example, an auto-reply by schedule and a chatbot flow, and both send a greeting. The customer receives two, not one.
• The flow uses the contact's tag or status incorrectly: it marks the contact as "new" every time the session restarts, instead of saving that they were already greeted at some point.

If your tool is a flow-based chatbot, it's most likely the first or the third. If you use automations with webhooks (Make, Zapier, n8n), it's usually the second: every webhook that arrives is processed as if it were the first time. And if you have a team with several people handling messages, it's possible that someone duplicated the greeting in two different places without realizing it.

How to fix it step by step (no code)

These steps can be done by the business owner or the person who manages WhatsApp, without technical knowledge. If at any point you need to edit a webhook or a snippet, that's no longer this path: talk to whoever built the automation for you.

1. 1Find out which channel sends the greeting. Go to your WhatsApp Business API provider's panel or the tool where you handle messages and look for the auto-replies, welcome messages or flows section. There you'll see whether the greeting comes from an auto-reply, a chatbot or an external automation.
2. 2Check the trigger condition. In most panels there's an option that says something like "send when the customer writes for the first time" or "send on every message". Change it to the first option. If your panel doesn't allow it, that's a sign that the greeting is set up as a general reply and needs to be moved to a separate welcome flow.
3. 3Look for duplicate automations. Go through all active rules and check if there's more than one that sends a greeting. If you find two, leave only the one you want active and deactivate the other. This includes auto-replies by schedule (outside business hours, holidays) that sometimes repeat the same text.
4. 4Check the contact's tags or status. If your tool uses tags to mark new contacts, verify that the greeting is tied to the "new" tag and that this tag is removed after the first greeting. If it's never removed, the system keeps thinking it's new.
5. 5If you use Make, Zapier or n8n, check the scenario's trigger. The greeting shouldn't be in the same scenario that processes all incoming messages. If it is, you need to add a condition that checks whether the contact has already been greeted before and, if not, send the greeting. That adjustment is best requested from whoever built the flow.
6. 6Test with a test number. Before considering the fix done, write from a number you haven't used before, send three messages in a row and confirm that the greeting appears only once. Then, wait more than 24 hours and write again to see if the greeting repeats when the window reopens.
7. 7Keep a record of what you changed. Write down the date, which rule you touched and who did it. If the greeting appears again in a few weeks, you'll know where to start looking without reviewing everything again.

How to prevent it from happening again

Once the greeting is sending only once, there are three habits that prevent the problem from reappearing. The first is having a single source for the greeting: if your team uses two tools (for example, one for campaigns and another for support), define which one sends the greeting and leave the other without automatic welcome messages. The second is documenting the active rules in a visible place: a simple spreadsheet with the rule name, what triggers it and who created it is enough so that no one duplicates it without realizing. The third is reviewing after every major change: when you add a campaign, a new channel or a person to the team, test again with a clean number to confirm the greeting still goes out only once.

It also helps to think of the greeting as part of the conversation and not as a fixed sign. A message that says "Hi! Tell me what you need and I'll help" repeated three times is annoying; the same message once, well placed, organizes the chat. If your tool learns from the team's real replies, as Wando does with AI suggestions, the greeting can be adjusted over time instead of staying frozen in a template that no one reviews.

When the real problem is something else and this symptom is just the tip

There are situations where a repeated greeting is not the underlying problem, but rather a sign that something else is poorly set up. It is worth telling them apart so you don't waste time adjusting the greeting when the cause lies elsewhere.

• The customer receives the greeting but then receives nothing else. There the problem is not the greeting: it is that the conversation is not reaching a person or the flow stopped after the first message.
• The greeting arrives but the customer says they don't see it or see it late. It may be an issue with the customer's device or notifications, not your configuration. There is nothing to adjust on your end in that case.
• The greeting is sent but you can't reply freely afterward. That can happen when you try to write outside the 24-hour window allowed by the WhatsApp API. To resume contact in that case, templates approved by Meta are used, and the approval period is up to 48 hours.
• The greeting appears only for some customers and not for others. It is usually misapplied labels or duplicate contacts in the list. Check whether the same number is loaded twice with different statuses.
• The greeting is sent but the team doesn't see it in the inbox. There the problem is internal visibility, not sending: the tool may be separating channels or the conversation may be assigned to another agent.

What to check if the greeting goes out but with the wrong text

A similar but different case: the greeting is sent only once, but the text is not the one you want. This is not a trigger problem but a content problem. If the greeting is set up as a template (HSM), the text depends on the template approved by Meta and cannot be freely edited: you have to create a new version and wait for approval, which can take up to 48 hours. If the greeting is a free auto-reply, it is edited directly in the panel. Before changing the text, check whether the greeting you see in the conversation is the one configured today or whether an old one was left saved in some flow you didn't review. It happens often when there was a campaign with similar text: the customer receives both and it seems the greeting is wrong, when in fact there are two different messages active at the same time.

Quick checklist to get it working

• I identified which tool the greeting lives in (panel, chatbot or external automation).
• The trigger condition says "first time of contact" and not "every message".
• There are no two active rules sending a greeting at the same time.
• The new contact label is removed after the first greeting.
• I tested with a clean number and the greeting appeared only once.
• I waited more than 24 hours and wrote again: the greeting did not repeat.
• I noted down what I changed and who did it, in case it happens again.

Frequently asked questions about the welcome message on WhatsApp Business API

These are the questions that come up most often when someone sets up an automatic greeting and notices that it repeats.