What is your goal?
I want to be able to use the scenario I built for a WhatsApp virtual assistant with multiple business.
What is the problem & what have you tried?
I have the scenarios working already. The main scenario receives the payload from WhatsApp via WhatsApp Business API then it takes the information and communicates it to the other scenarios as needed. I use Google sheets for the business profile. That gives the scenarios the required details to work with making it multiclient.
The problem is that WhatsApp limits the use for only 2 numbers and in order to increase it to 20 you need to validate the business and that has been a nightmare. I was wondering if using WhatsApp module in MAKE can fix this and so I can use the solution with different businesses.
I know there are suppliers authorized by META to provide that “multiclient” service but wanted to use WhatsApp API to avoid going with intermediaries that increases the cost of the solution.
I would appreciate any support or guide you can provide.
What is your goal?
I want to be able to use the scenario I built for a WhatsApp virtual assistant with multiple businesses.
What is the problem & what have you tried?
I have the scenarios working already. The main scenario receives the payload from WhatsApp via the WhatsApp Business API and then communicates it to the other scenarios as needed. I use Google Sheets for the businesses’ profiles. That gives the scenarios the required details to work with, making it multi-client.
The problem is that WhatsApp limits the use to only 2 numbers, and in order to increase it to 20, you need to validate the business, which has been a nightmare. I was wondering if using the WhatsApp module in MAKE can fix this, so I can use the solution with different businesses.
I know there are suppliers authorized by META to provide that “multi-client” service, but I wanted to use the WhatsApp API to avoid going with intermediaries that increase the cost of the solution.
I would appreciate any support or guide you can provide.
I understand that phone limits are set by META and their policies. I guess my question is for those that have the experience of working scenarios that require WhatsApp communication and how they solved it. Can the WhatsApp Business module in MAKE work with multiclient scenarios?
Make’s WhatsApp module does not raise Meta’s number cap. Two numbers stays two numbers, HTTP or module.
What actually scales for multi-client is one WABA per client, or a BSP that already holds them, and Make only fans out. Are the two numbers already under one business, or two separate WABAs you are trying to drive from one scenario?
Irina,
Thank you for your response. Can you help me to understand better the difference between using WhatsApp Business module in MAKE versus the WhatsApp API that I am currently using? Here is my scenario for better reference.
About the WABAs, I have two active under my business portfolio working just fine but can’t add more. The scenario handles multi-client but every WABA needs to be added to the same account from where I run the META Developers App.
If my META Developers App could be shared to other business portfolios, then each business portfolio can have up to two WABAs without problem and that could be the solution without having to get third party services (WhatsApp vendors).
Does this make sense? Please, let me know your thoughts.
Regards,
Guillermo
The module and the Cloud API you already call are the same Meta surface. The module just wraps auth, media, and the webhook. It will not let a third WABA onto that Developer App.
Sharing one Meta app across other people’s business portfolios is Tech Provider territory. That is the intermediary you were trying to skip. Make has no toggle for it.
With two WABAs already under your portfolio, the Make-side split is one connection per WABA and a router, not a different WhatsApp module. Are you hitting a Meta portfolio cap, or is the Developer App itself refusing the third WABA?
Irina,
First let me thank you for taking the time to respond with such clear understanding of the terms and tools. It is great to have someone experienced to discuss topics.
Now, META App provides the communication between META (WhatsApp) and MAKE. It has the webhook to receive the payload in MAKE and permanent TOKEN for the HTTP modules to be able to send WhatsApp responses. The problem is that the Business Portfolios can only have two active numbers, you can have multiple WABAs but only two numbers are allowed per business portfolio unless the business is verified.
I’ve been thinking … maybe I can replicate for each customer …
- META App (TOKEN and Webhook) and Business Portfolio and WABA on customer’s account
- Customer’s Business Portfolio and WABA connected to own META App
- Have an independent main scenario in MAKE for each customer that receives the payload and then connect to the shared sub-scenarios … the problem then will be with the permanent TOKEN on each HTTP, if cannot be dynamic won’t work. And of course, the inconveniences of accessing to customer’s personal accounts.
The per-customer Meta App is the non-BSP path. One webhook and one token per client, then a parent scenario that only routes into shared subscenarios.
The HTTP token can be dynamic. Store it per client and map it into the Authorization header. A single hardcoded connection object is what breaks that design.
I would not log into the customer’s personal accounts to set this up. They create the app, they paste the token. Are you planning a one-time setup form for that, or were you hoping Make’s WhatsApp connection picker could still hold all of them?
Now that you confirm that Authorization header can be dynamic opens the chance to go around and avoid the need of third party services that increases the cost.
About the app and token. I already have a Onboarding document where I can add these steps but customer will need to get familiar with terms and all. Not impossible but may frustrate them (as frustrates me at times have to say), will look into that. Thanks
After a lot of research and troubleshooting, sharing this in case it helps someone facing the same issue.
META’s limit of 2 numbers per WABA doesn’t increase unless the company is verified and approved.
After several days, verification is still stuck “In Review” — no warnings, no request for additional documentation, just dormant.
META’s support is practically nonexistent. I couldn’t find a way to reach anyone at META to request follow-up or feedback on the verification.
Note: The company I’m trying to verify is in Spain and is not an S.L. — it’s a model available in Spain where, as an individual, you can operate a business and pay taxes (autónomo). Even though I submitted official documents, verification hasn’t gone through. It’s possible that if it were an S.L., or a US company with articles of incorporation, verification wouldn’t be an issue.
This is NOT a MAKE issue, and MAKE’s community has been very kind trying to help. I just tried this channel looking for guidance from others who’ve built WhatsApp automations in MAKE.
SOLUTIONS
Use a company that has articles of incorporation to get approved and raise your limit to 10, or become a Tech Provider in META to go even beyond 10.
Create an independent Business Portfolio, WABA, ID Number, App and permanent token for each account you want to serve with your MAKE automation.
Create a scenario that receives the payload from META/WhatsApp, then connects to the rest of your scenarios using dynamic client configuration.
Posting this in case it helps someone.
Best to all, and happy automating!
Thanks for coming back with this additional info! I will mark your last reply as solution so that the topic can be closed.
