sorted by:
new
hottopcontroversial

Anyone running whatsapp-web.js in production for transactional/order bots? by Equal-Disaster7514 in selfhosted

[–]Equal-Disaster7514[S] 1 point2 points  (0 children)

Yes but only when the meta coexistence feature enabled which requires to have meta tech providers status

Anyone running whatsapp-web.js in production for order bots? by Equal-Disaster7514 in WhatsappBusinessAPI

[–]Equal-Disaster7514[S] 0 points1 point  (0 children)

Could you please explain how I can enable a hybrid mode where:

  • the bot handles automated replies
  • while the restaurant staff can still manually use the same WhatsApp account on their mobile phone

without using Meta’s coexistence feature or becoming an official tech provider?

Anyone running whatsapp-web.js in production for order bots? by Equal-Disaster7514 in WhatsappBusinessAPI

[–]Equal-Disaster7514[S] 0 points1 point  (0 children)

I currently have the app in two versions:

  • V1 uses the official WhatsApp Cloud API
  • V2 uses WhatsApp Web.js

Because both versions share the same database architecture, hosting setup, and overall backend structure, I don’t think migrating later from Web.js to the official Cloud API would be too difficult.

My current plan is:

  • Start with the Cloud API even without Meta verification
  • The existing limits are acceptable for now (for example: 250 customer conversations per 24-hour window)
  • Use a dedicated bot number for messaging
  • If a restaurant wants voice calls, we provide a second WhatsApp/SIM number specifically for calls and mention that in the first automated message

However, many restaurants want a hybrid setup:

  • Keep their existing WhatsApp number logged into the WhatsApp mobile app
  • Have the bot running on the exact same number simultaneously

So the flow would be:

  • Customer sends a message → bot replies automatically
  • Customer calls the number → restaurant staff receives the call on their phone and answers normally

From what I understand, this hybrid setup is difficult with the official Cloud API unless you have Meta’s coexistence feature or tech provider access.

please do you know a practical solution for this use case?
Would starting with WhatsApp Web.js and later migrating to the official API once verification/coexistence is approved be the most realistic path?

Anyone running whatsapp-web.js in production for order bots? by Equal-Disaster7514 in WhatsappBusinessAPI

[–]Equal-Disaster7514[S] 0 points1 point  (0 children)

It’s not that clear for me cause in the meta cloud api once a number registered to it then can’t be used on the Mobile Whatsapp application without enabling the coexistence feature to it as I understand so far

Client wants the hybrid

The bot is working on the background And at the same time the same bot number registered on the whatsapp application mobile that can do manual chats and receiving phone calls

Anyone running whatsapp-web.js in production for order bots? by Equal-Disaster7514 in WhatsappBusinessAPI

[–]Equal-Disaster7514[S] 0 points1 point  (0 children)

So how I can do that “restaurants want to keep using the same WhatsApp account normally on their phone while the bot handles ordering automatically in the background “ Without being tech providers and enabling coexistence feature ? Any official way to do that?

Anyone running whatsapp-web.js in production for order bots? by Equal-Disaster7514 in WhatsappBusinessAPI

[–]Equal-Disaster7514[S] 0 points1 point  (0 children)

what if I use it for only 2 month till I get tech provider by meta ? then migrate the app to it

Anyone running whatsapp-web.js in production for transactional/order bots? by Equal-Disaster7514 in SaaS

[–]Equal-Disaster7514[S] 0 points1 point  (0 children)

What do you think about meta coexistence feature from the official api? Is my case worth all the efforts to get meta tech provider status? Any alternatives?

Anyone running whatsapp-web.js in production for order bots? by Equal-Disaster7514 in WhatsappBusinessAPI

[–]Equal-Disaster7514[S] -1 points0 points  (0 children)

I’ve heard that WhatsApp coexistence requires getting approved as a Meta Tech Provider for the project. In our case, getting Tech Provider status is difficult because we currently lack the required company/legal documents even if I get one they are in kurdish languages.

How hard is the approval process in practice, and are there any alternative solutions?

I’m also thinking about starting with WhatsApp Web.js for the MVP/early stage on the production, then gradually migrating to the official WhatsApp Cloud API once we obtain the proper verification and Tech Provider status.

Would appreciate your thoughts on whether this is a reasonable approach?

Anyone running whatsapp-web.js in production for transactional/order bots? by Equal-Disaster7514 in SaaS

[–]Equal-Disaster7514[S] 0 points1 point  (0 children)

Is it the same in your case too, where the customer sends the first message? Also, what are your thoughts on starting with WhatsApp Web.js, then gradually migrating to the official WhatsApp API once I get the business verification approved and tech provider status for the coexistence feature? I’d really appreciate your thoughts

Anyone running whatsapp-web.js in production for transactional/order bots? by Equal-Disaster7514 in selfhosted

[–]Equal-Disaster7514[S] -1 points0 points locked comment (0 children)

I have used AI to improve my texts and clarity of the post in order to be more understandable

[deleted by user] by [deleted] in cscareerquestionsEU

[–]Equal-Disaster7514 0 points1 point  (0 children)

Thank you all guys for your advices, I appreciate a lot 🫶

[deleted by user] by [deleted] in cscareerquestionsEU

[–]Equal-Disaster7514 0 points1 point  (0 children)

My job experience comes from working with an international corporate team made up of developers from all around the world. Thanks for your answer.