WhatsApp in a Shared Customer Inbox | Nuxbe [ Skip to content ](#main-content) [ Nuxbe ](https://nuxbe.com/en) [ Home ](https://nuxbe.com/en) [ Flexible ](https://nuxbe.com/en/features/flexible) [ Open Source ](https://nuxbe.com/en/features/open-source) [ Industries ](https://nuxbe.com/en/industries) [ Modules ](https://nuxbe.com/en/modules) [ Premium ](https://nuxbe.com/en/premium) [ FAQ ](https://nuxbe.com/en/faq) [ Partners ](https://nuxbe.com/en/partners) [ Contact ](https://nuxbe.com/en/contact) EN DE [ Home ](https://nuxbe.com/en) [ Flexible ](https://nuxbe.com/en/features/flexible) [ Open Source ](https://nuxbe.com/en/features/open-source) [ Industries ](https://nuxbe.com/en/industries) [ Modules ](https://nuxbe.com/en/modules) [ Premium ](https://nuxbe.com/en/premium) [ FAQ ](https://nuxbe.com/en/faq) [ Partners ](https://nuxbe.com/en/partners) [ Contact ](https://nuxbe.com/en/contact) Omnichannel WhatsApp Integration ==================== Customers message you on WhatsApp, your team answers from the same inbox as the internal chat [ Contact ](https://nuxbe.com/en/contact) Meet Customers Where They Are ----------------------------- The WhatsApp integration brings customer conversations into Nuxbe. Inbound and outbound messages, media and delivery receipts all live in the omnichannel chat core, right next to your internal team chat. Agents read and reply without leaving the ERP, so customer requests stay connected to orders, tickets and contacts. ### Shared Inbox WhatsApp messages land in the same chat inbox your team already uses. Agents answer customer and colleague alike from one place, with full context from the linked contact. ### Media & Receipts Send and receive images, documents and voice messages. Delivery and read receipts are tracked per message, so you always know whether a customer has seen your reply. ### Linked to Your Data Every conversation connects to the matching contact, order or ticket. Customer history stays in one thread instead of scattered across phones and apps. In practiceWhat the inbox is good for day to day ------------------------------------- ### A number that does not live on one person's phone The company number belongs to the team, not to a colleague's device. When somebody is away, their cover reads the same thread, and when somebody leaves, the customer history stays with the company rather than on a private handset. ### Questions about a running order When a message comes from a known number, the conversation hangs on the contact and therefore on their orders and tickets. If the number is new, the chat stays unlinked until somebody attaches it to a contact or creates one from it. ### Replies with AI support With the AI package installed, an assistant can read and answer the same conversations a human can, under the same permissions and the same validation on send. It gets no access to numbers the user behind it is not cleared for either. SetupOne service, one connection, one QR code ---------------------------------------- A small service runs alongside Nuxbe and holds the connection to WhatsApp. It can sit on the same server or run through the Nuxbe gateway, and it needs persistent storage for the session so a restart does not force a fresh pairing. In Nuxbe you create a connection pointing at that service: address, key and a shared secret for inbound events. Without that secret Nuxbe accepts no message. Finally the number is paired once by QR code, the way WhatsApp Web works. After that you decide which users are allowed to work with it. ### Requirements - A reachable connection service with persistent storage - A phone number enabled for WhatsApp - The chat package as the shared inbox - A list of the users allowed to operate that number LimitsWhat to know before you decide ------------------------------ The integration rides on a paired WhatsApp session rather than Meta's official cloud access. That makes setup simple and running it cheap, but it also means a dropped session calls for a fresh QR code, and what WhatsApp itself tolerates sets the ceiling, not a contracted allowance. Templates, buttons, lists and catalogues, as the official business access knows them, are not available here. What is supported is text, media, reactions and delivery and read receipts. Group chats are not catered for; the integration is built around the conversation with a single number. Attachments are size limited, inbound at twenty-five megabytes. Anyone who has to exchange larger files stays with email or the customer portal. All packages included --------------------- All premium packages are included in the Nuxbe license. Contact us for more information. [ Contact ](https://nuxbe.com/en/contact) Related pages --------------- [### Office 365 Synchronization with Microsoft Office 365 for calendars, contacts, and more ](https://nuxbe.com/en/premium/office365) [### IDS Connect Connection to the IDS Connect API for dental trade ](https://nuxbe.com/en/premium/ids-connect) [### Office 365 Mail Email sending via Microsoft Graph API with OAuth 2.0 authentication ](https://nuxbe.com/en/premium/o365-mail) [### Chat Integrated team chat for internal communication ](https://nuxbe.com/en/premium/chat) Nuxbe Open Source ERP system for modern businesses. ### Links [ GitHub ](https://github.com/Team-Nifty-GmbH/flux-core) [ Contact ](https://nuxbe.com/en/contact) ### Mobile App [ App Store ](https://apps.apple.com/de/app/nuxbe/id6754884170) [ Google Play ](https://play.google.com/store/apps/details?id=com.teamnifty.nuxbe) ### Legal [ Imprint ](https://nuxbe.com/en/imprint) [ Privacy Policy ](https://nuxbe.com/en/privacy) [ Terms and Conditions ](https://nuxbe.com/en/terms) [ Cookie Policy ](https://nuxbe.com/en/cookie-policy) © 2026 Nuxbe. All rights reserved.