I am opening this feature request to address a recent and highly crucial update from Meta’s WhatsApp Business Platform ecosystem: the official support for WhatsApp Coexistence.
During my interactions with the Intercom support team, there seems to be a misconception that using the WhatsApp Business App and the Cloud API simultaneously on the same phone number is either unofficial or a workaround. I want to clarify that this is now a fully official feature documented and supported by Meta, and having Intercom support it natively would be a massive game-changer for many businesses.
What is WhatsApp Coexistence?
Meta now officially allows businesses to register and use the same phone number concurrently across the WhatsApp Business App (mobile/web) and the WhatsApp Business Platform (Cloud API).
When configured correctly via Cloud API, this setup enables:
The Best of Both Worlds: Centralized multi-agent support inside Intercom via the API, while maintaining the ability to make/receive voice calls and perform quick mobile checks via the native WhatsApp Business mobile app.
Official Implementation: It is not a gray-market hack or a standard session-cloning method. It relies entirely on Meta's official routing architecture.
Why Intercom Needs to Support This
Many small and medium-sized businesses, as well as B2B platforms, rely on WhatsApp voice calls or need their field teams to have mobile app access while the core customer service/support operations happen seamlessly inside Intercom. Currently, Intercom’s onboarding or connection flow completely overrides or blocks this coexistence capability due to outdated validation parameters.
You can verify the official documentation and Meta's technical guidelines regarding this architecture here:
Please pass this request to the Product and Engineering teams responsible for the WhatsApp Integration. Updating Intercom’s WhatsApp integration schema to recognize and support Meta's Coexistence feature would drastically improve the onboarding experience and prevent businesses from having to choose between a robust CRM/Helpdesk like Intercom and basic mobile functionality.
Looking forward to hearing from the community and the product team on this.
Best regards,
Naur Souto
Best answer by Sean Meade Forum Support Lead
Hi @naur.souto, Seán here from the Fin technical support team 👋
Thanks for raising this thoughtful write-up and providing the direct link to Meta's developer documentation.
You are completely correct: Meta does now officially document an onboarding path for businesses to use an existing WhatsApp Business App number alongside the Cloud API—commonly referred to as "Coexistence." It is no longer an unofficial workaround or a gray-market hack.
However, as we look at this from an engineering standpoint, there are a few technical nuances and architectural constraints worth clarifying for the community:
It isn't a full "everything works everywhere" sync: Meta’s coexistence architecture keeps certain features strictly isolated. For instance, while Cloud API can handle the centralized text conversations, native functions like voice/video calls and group chats remain restricted to the mobile app and will not natively stream data or sync states back into Intercom.
It requires a completely different integration flow: Supporting this is significantly more complex than simply relaxing or updating a validation parameter in Intercom’s current schema. To support Meta's newer flow, a partner integration has to fundamentally alter the onboarding pipeline. This requires a specific Embedded Signup setup, unique webhook subscriptions, skipping standard API phone-number registration steps, and executing a distinct historical contact/message sync.
That being said, you are entirely spot-on that our public documentation and current onboarding flows still mandate that a number be deleted from the WhatsApp Business mobile app before connecting to Intercom. Our current setup does not yet reflect Meta's newer coexistence capabilities.
While I can’t make any roadmap commitments or timeline promises regarding if or when our integration architecture will change, I completely understand how the current messaging from our team caused confusion. To address this immediately, we will update our support staff on the proper phrasing and technical distinction moving forward so that everyone is aligned on Meta's official documentation versus Intercom's current integration limitations.
Thank you again for bringing this up and helping us keep our community informed on these ecosystem updates!
Hi @naur.souto, Seán here from the Fin technical support team 👋
Thanks for raising this thoughtful write-up and providing the direct link to Meta's developer documentation.
You are completely correct: Meta does now officially document an onboarding path for businesses to use an existing WhatsApp Business App number alongside the Cloud API—commonly referred to as "Coexistence." It is no longer an unofficial workaround or a gray-market hack.
However, as we look at this from an engineering standpoint, there are a few technical nuances and architectural constraints worth clarifying for the community:
It isn't a full "everything works everywhere" sync: Meta’s coexistence architecture keeps certain features strictly isolated. For instance, while Cloud API can handle the centralized text conversations, native functions like voice/video calls and group chats remain restricted to the mobile app and will not natively stream data or sync states back into Intercom.
It requires a completely different integration flow: Supporting this is significantly more complex than simply relaxing or updating a validation parameter in Intercom’s current schema. To support Meta's newer flow, a partner integration has to fundamentally alter the onboarding pipeline. This requires a specific Embedded Signup setup, unique webhook subscriptions, skipping standard API phone-number registration steps, and executing a distinct historical contact/message sync.
That being said, you are entirely spot-on that our public documentation and current onboarding flows still mandate that a number be deleted from the WhatsApp Business mobile app before connecting to Intercom. Our current setup does not yet reflect Meta's newer coexistence capabilities.
While I can’t make any roadmap commitments or timeline promises regarding if or when our integration architecture will change, I completely understand how the current messaging from our team caused confusion. To address this immediately, we will update our support staff on the proper phrasing and technical distinction moving forward so that everyone is aligned on Meta's official documentation versus Intercom's current integration limitations.
Thank you again for bringing this up and helping us keep our community informed on these ecosystem updates!
