Shared inbox
Connect your numbers and let the team work from the same list, with each row showing who is handling that customer.
When numbers live on separate phones, nobody knows who is looking after which customer. One person replies, a colleague answers the same question again, and a third chat sits unopened for days. The shared inbox puts the chats from every connected number into one list and lets you give each chat an owner.
Telegram is the channel available today: personal numbers, groups, channels and bots. WhatsApp is in development (coming soon), with Instagram after that.
New messages, assignee changes and notes appear without reloading the page.
| Filter | What it shows |
|---|---|
| Number | Only the chats of the selected number; with a number selected, that account's chat folders become filters too |
| Unread | Chats with unread messages |
| Assignee | Assigned to me, unassigned, or a specific teammate's chats |
| Stage | Chats in the selected pipeline stage; chats without a stage can be filtered separately |
| Label | Chats carrying the selected label |
| Type | Private chats, groups or channels |
| Search | By chat name or username |
Filters combine: "assigned to me, unread, in the Proposal stage" is a single list. Save a combination you use often as a view and reopen it in one click.
Internal notes sit in the panel beside the conversation and are never sent to the customer. Each note shows who wrote it and when. The author or a manager can delete it.
Saved replies are written once in Settings. A button next to the composer opens the list; the text you pick is inserted into the composer, so you can edit it before sending. Saved replies do not fill in variables automatically: you type the customer's name yourself.
Owners and admins see every number. An agent sees only the chats of the numbers assigned to them. On each number, a manager can make the agent read-only, hide groups or private chats, or limit the agent to the chats they are assigned to. Live updates follow the same rules: a message in a chat the agent cannot see is not pushed to that agent's screen. The details are on the team permissions page.
To try it, create an account. The Telegram-specific details are on telegram.mycrm.sh.
Is message history stored on MyCRM servers? No. Message bodies are not stored; when you open a chat, the history is read live from the connected account. The database keeps only a preview of the last message and a log of message events for reports.
Can two people write in the same chat at the same time? Yes, the panel does not lock a chat. What prevents collisions is the assignment: the assignee's name is visible on the chat's row. For a stricter setup, give agents the "assigned chats only" rule.
Can we keep using the app on the phone? Yes, the number stays logged in on the phone. But a message sent from the phone cannot be attributed to a team member, so per-agent reports count only messages sent from the panel.
Will WhatsApp and Instagram chats appear in this list? Today only Telegram can be connected. WhatsApp is coming soon, and Instagram will follow.
Related: Team permissions · Support tickets · CRM for support teams