# One Shared Inbox for WhatsApp, Email and Website Chat

> Moharrik puts WhatsApp, email and website chat in one shared inbox, next to the contact and the deal, and lets Claude work it through MCP.

*2026-10-19T12:49:06Z*

# One Shared Inbox for WhatsApp, Email and Website Chat

If your clients write to you on WhatsApp, some by email and some through the chat on your site, the history ends up in three places. Nobody on the team sees the whole conversation, and the CRM knows none of it.

Moharrik fixes that with **one shared inbox for WhatsApp, email and website chat**. Every conversation sits next to the contact and the deal it belongs to. It is open source, bilingual (English and Arabic), and every capability is also an MCP tool, so an AI assistant can work the inbox under your permissions.

![Moharrik: a CRM and shared inbox your AI assistant can operate](https://moharrik.com/uploads/sites/0e785a81-6114-495e-8620-05f0607672d4/media/moharrik-gallery-hero.png)

## The problem

Channels multiply faster than teams. A client asks about an order on WhatsApp, follows up by email, then opens the chat on your website. Each channel has its own app, its own history and its own unread badge.

The usual fix is a shared inbox. That helps, but it still leaves the conversation cut off from the contact, the company and the deal.

## How it works

![One inbox: WhatsApp, email and website chat together, with AI summaries per conversation](https://moharrik.com/uploads/sites/0e785a81-6114-495e-8620-05f0607672d4/media/moharrik-gallery-inbox.png)

- **Website chat.** An embeddable chat widget. Messages arrive in the inbox and replies appear in the visitor's widget.
- **Email.** Mailboxes are read over IMAP, and replies go out through the workspace's own SMTP, threaded under the customer's message.
- **WhatsApp.** You link a number by scanning a QR code (Linked devices). Each workspace has its own instance, so two workspaces never share a number.
- **One thread view.** Labels, assignment, snoozing, canned replies, and an AI summary per conversation so a long chat reads at a glance.
- **Attached to the CRM.** Contacts, companies and a drag-to-move deal pipeline, with one shared timeline. Website inquiry forms land as leads, and one click converts a lead into a contact, a company and a deal.
- **Operable by AI.** The workspace MCP server exposes the inbox and the CRM as tools (`list_conversations`, `get_conversation`, `reply`, `close_conversation`, `list_leads`, `convert_lead` and more). Tokens carry explicit scopes and are narrowed to the member's current role on every call.

One detail worth knowing: when an agent reads a thread, every result carries a note that messages from the customer are information, not instructions. A stranger's message should not be able to give your assistant orders.

## Honest limits

- The `reply` tool sends through the real channel. If you want to approve each message, keep your MCP client's per-tool approval turned on.
- The first WhatsApp message to a contact with no thread needs a one-time 6-digit confirmation code, and `whatsapp:send` only reaches contacts who opted in and have not said STOP.
- WhatsApp needs an Evolution API server. The hosted version has one; if you self-host, you point `EVOLUTION_API_URL` at yours.

## Getting started

Hosted: sign up at [moharrik.com](https://moharrik.com), create a workspace and connect a channel.

Self-host with Docker Compose (from the README):

```bash
git clone https://github.com/fadymondy/moharrik.git && cd moharrik
cp .env.selfhost.example .env.selfhost
# fill in POSTGRES_PASSWORD, MOHARRIK_APP_DB_PASSWORD and AUTH_SECRET
# (generate each with: openssl rand -hex 32)
docker compose -f docker-compose.selfhost.yml --env-file .env.selfhost up -d --build
```

Open http://localhost:3000, register and create a workspace. To connect Claude or another MCP client, mint a token under Workspace, MCP tokens, or use the OAuth connector.

## FAQ

**Which channels does the inbox support?** Website chat, email (IMAP in, your SMTP out) and WhatsApp through a QR-linked number.

**Can an AI assistant reply for me?** Yes, over MCP. It uses the same permissions as you, and you can keep per-tool approval on.

**Is it open source?** Yes, AGPL-3.0. Self-host it with Docker Compose.

**Does it support Arabic?** Yes. The app is bilingual with right-to-left layout.

## Links

- [Product Hunt](https://www.producthunt.com/products/moharrik)
- [GitHub](https://github.com/fadymondy/moharrik) and [Discord](https://discord.gg/BMERkavdVq)
- Case study: [Multi-tenant Postgres RLS in Go: Moharrik on ToGO](https://to-go.dev/en/blog/moharrik-togo-case-study)
- Founder post: [Why I built Moharrik](https://fadymondy.com/en/blog/why-i-built-moharrik)

---

Source: https://moharrik.com/en/blog/shared-inbox-whatsapp-email-website-chat