Which number does the automation send WhatsApp from?
Every WhatsApp message step has a Sending number field. It takes two answers: From the conversation context, which replies from the same number that received the trigger, or one of your connected numbers, pinned so the step always sends from it.
Role: any member with edit access to the workspace.
Before you start: at least one connected WhatsApp number. See how to connect WhatsApp.
Choose the number for the step
- Open the automation and click the WhatsApp message step.
- In Sending number, pick one option:
- From the conversation context — the message goes out from the same number the contact wrote to. This only works when the automation trigger is a WhatsApp one, because that is what carries the source conversation.
- Responsible attendant number — the message goes out from the WhatsApp number linked to the attendant who owns the lead opportunity, resolved at send time. Works with any trigger.
- A number from the list — the message always goes out from that number, whatever the trigger is.
- If you pick Responsible attendant number, a second field appears, If there is no attendant number: choose Do not send (the automation ends with an error for that contact) or a fallback number used whenever the attendant number cannot be used.
- If the automation uses a template, pick it after the number — the number decides which templates show up:
- With a fixed number, the list shows the approved templates for that number.
- Under Responsible attendant number, the list shows the templates of all your numbers, one per name. That is how you pick a paid template that only exists in one attendant's business account: the automation stores the template name and, at send time, looks that same name up on the number the attendant uses.
- Each template in that list shows how many numbers it is approved on. When it is not on all of them, the editor names the numbers that have it — contacts handled by the other numbers use the fallback number.
- When you change the number, the configured template is dropped and you pick a new one — what gets stored changes along with the mode.
The same field appears on the step card in the canvas and inside the Write message screen — both edit the same setting.
How the attendant number is resolved
Under Responsible attendant number, every send follows this order:
- The automation finds the lead's opportunity — the one that fired the trigger or, when the trigger is not about an opportunity, the lead's most recent open opportunity.
- From the opportunity, it reaches the responsible attendant.
- From the attendant, it reaches the WhatsApp number linked to them in the workspace. If the attendant has more than one linked number, the oldest link wins.
If any link in that chain is missing — the lead has no opportunity, the opportunity has no owner, the attendant has no linked and connected number, or the chosen template is not approved on their number — that contact is sent from the fallback number. With no fallback set, only that contact ends with an error; the rest of the batch goes out normally. The error shows up in the automation execution history.
When the number changes on its own
From the conversation context depends on a WhatsApp trigger. If you swap the automation trigger for one that opens no conversation — a tag applied, a purchase, a scheduled date — the step has nowhere to inherit the number from. Rather than leaving the automation impossible to publish, the editor pins the first connected number and says so right below the field:
The new trigger has no source conversation, so we set a fixed number.
When there is no connected number to pick from, the warning asks you to choose:
The new trigger has no source conversation. Pick a sending number.
Always check when that warning shows up. The number the editor picked may not be the one you would use for that message. Just open the field and select the right number — the warning clears as soon as you choose. It also clears on its own if you go back to a WhatsApp trigger, because From the conversation context becomes valid again.
Related
- Automations — every automation in the workspace.
- Connect WhatsApp — a prerequisite for any send.
- Create your first recovery automation — the WhatsApp step inside a full flow.
- Channel settings in automations — picking the channel for each step.
If it did not work
- The From the conversation context option is missing: the automation trigger is not a WhatsApp one. Change the trigger or pick a fixed number.
- The template disappeared after changing the number: it belonged to the previous number. Pick a template from the new number — see WhatsApp templates.
- The template is missing from the list: with a fixed number, only that number's templates show up; switch to Responsible attendant number to see every number's templates, or create the template on the number that will send it.
- Some contacts did not get the template: it is not approved on every number. The editor shows how many numbers have the template — set a fallback number, or get the same template approved on the missing numbers.
- The template buttons do not branch the flow: quick-reply buttons keep working when the same template exists on several numbers, as long as the button text is identical on all of them. A button renamed on one number stops matching the step outlet.
- The message never arrives: it may be the Meta sending limit. See the Meta limit.