WContacts

How to set up a shared inbox for WhatsApp and email

When customer correspondence scatters across personal phones and separate mailboxes, the history of a job lives only with the person who did it. This page covers why messaging falls apart and how it is gathered into one inbox in the WApps business management ecosystem.

Start your 30-day free trial

Web based·One WApps account·4 key outcomes·Page updated: 26 July 2026

Interface previewWContacts / WApps

Try it now:Open a conversation from the inbox, leave an internal note, and send the reply.

Inbox0/3

Select a conversation

Open a conversation on the left — WhatsApp and email share one thread.

What is a shared inbox?

A shared inbox is a workspace where customer messages from different channels collect on one screen and the whole team replies from the same place. WhatsApp and email do not live in separate apps; they accumulate as a single thread under the contact. Who replied to what, internal notes and delivery status are all on the record, and the correspondence stays with the company rather than on a personal phone.

Problem and approach

Conversations scatter across personal phones

A customer writes over WhatsApp in the morning and by email in the afternoon; the two messages reach two different people, and neither knows what the other said. The same question gets two different answers. When a team member leaves, the conversation history walks out with their phone. Because it is unclear who replied to what, some messages get answered twice and others not at all.

Target flow: organised by contact, not by channelTarget flow: correspondence stays with the companyTarget flow: internal notes never reach the customer

Impact on the workflow

Target flow: organised by contact, not by channel

WhatsApp and email merge into one thread under the same contact, so history does not break when the channel changes.

Target flow: correspondence stays with the company

Conversations are kept in the account rather than on a personal phone, so customer history survives someone leaving.

Target flow: internal notes never reach the customer

The team leaves context inside the thread before replying, instead of moving it to a separate chat app.

Target flow: delivery status is visible

Implementation notes

WContacts is built for this flow

WhatsApp and email channel connections, one conversation thread per contact, internal notes and delivery status are built into WContacts.

What should you measure?

Three numbers are enough for a shared inbox: first response time, the number of conversations left unanswered, and inbound volume split by channel. All three fall out of the conversation record and need no separate reporting work.

Work it out with your own numbers

Try it with your figures: with M messages a day and an average first response time of T, the total drag of delay is M×T. Counting the cases where two people answered the same question separately makes the time a shared inbox gives back visible. What matters is not the measurement but that every message lands in a single record.

What setup this runs on

This flow is built with WContacts. WhatsApp and email accounts are connected, and each channel is authorised for sending, receiving or both. Channel connections run through the messaging layer beneath the product — credentials are stored encrypted and are never exposed to team members. WLeads or WSupport records in the same account share the customer as a single record.

Continue exploring

Next step