The unified inbox

The Inbox is where the day happens. Every message from every connected Channel (WhatsApp first, plus Messenger, Instagram, Telegram, Live Chat, SMS and the rest) arrives in one list, and you reply from the same place. Behind each conversation is a Contact record: workspace-owned, and able to hold identities on more than one channel. It won’t stitch channels together on its own, though: the person who WhatsApps you today and comments on your Facebook post tomorrow arrives as two contacts, and stays that way until you merge them by hand. That’s what View full profile & merge is for. It is called Unified Inbox in the sidebar and just Inbox once you open it. Same thing. Prefer to watch first? This walkthrough covers working the Inbox end to end.

​

The active channel does not scope the Inbox

This is the one that catches people, so read it before anything else. Most of DMLY works on the channel you have selected: Bot Setup, Broadcasts and Growth Tools all act on that one channel, and switching profiles changes what they show you. The Inbox does not work that way. It has no channel picker of its own and it ignores the one you set elsewhere. The Inbox always spans every channel you have connected. If your sidebar shows WhatsApp selected, the Inbox still lists your Instagram DMs and your Live Chat threads alongside your WhatsApp chats.

​

How you work in it

Three panes, left to right: the conversation list, the open thread, and a details panel for the contact. On a phone you see one at a time: open a conversation to read it, and use the back arrow to return to the list. The details panel is hidden on narrower screens. The rhythm is: pick a conversation from the list, read and reply in the middle, and use the details panel on the right for everything about the person: Assigned to, Pipeline stage, Tags, Internal notes, upcoming appointments, and View full profile & merge if you need the whole client record. Opening a conversation marks it read and drops its unread count straight away.

​

Folders

The list has four folders: An archived conversation only shows under Archive; All won’t surface it. Two things worth knowing on day one:

• Nothing closes itself on a timer. There is no auto-close after a quiet period. A conversation becomes Done when someone selects Mark as done in the details panel, or when an automation you built does it: the Close conversation step in a flow, or an AI assistant you connected over MCP.
• A reply from the contact reopens it. If a done conversation gets a new inbound message, it flips back to Open and un-archives itself, so you can’t miss a follow-up. That is the default: an admin can restrict reopening to a time window, or turn it off, in Conversation settings.

Marking done takes you out of the thread and back to the list, keeping your folder and filters, which is what you want when you’re clearing a queue. See conversation status.

​

Narrowing the list

Search conversations at the top of the list is the fastest tool you have, and you’ll need it more than you expect: the list shows the 100 most recent conversations and there is no paging or infinite scroll. Anything older is reachable by search, not by scrolling. Alongside search:

• DMs / Comments: a toggle directly under the search box that picks which kind of thread the list shows. It starts on DMs and there is no All, so it is the one control you have to switch rather than clear. See one contact, two threads.
• Channel pills across the top of the list: WhatsApp, Facebook, Instagram and SMS, plus All. Telegram, Live Chat, TikTok and Google Business Profile reviews are all in the list; they just don’t have a pill.
• All channels: a picker in the extra filters that narrows to one specific connected profile, including the channels with no pill. Use this if you run two WhatsApp numbers and only want one of them.
• Anyone / Unassigned: filter by who owns the conversation.
• Unread only: what it says.

​

Tags

The details panel’s Tags section is how you colour-code what a conversation is about: VIP, Complaint, Wholesale. One thing to understand first: a tag here is a contact tag, the same object on the same record, not a second inbox-only set. Tagging a conversation tags the person, not just this thread, and a tag added anywhere else shows up here. To apply one, open the conversation and select Add under Tags in the details panel, then pick from the list. Applied tags sit there as coloured pills; remove one with its ×. Until you add any, the section reads No tags yet. Two practical points:

• The Add list only offers tags that already exist. There’s no way to create one from the details panel. Set them up (name and colour) with Manage tags on the Contacts page first.
• Filter the list by tag. Open the extra filters (the funnel by the folder pills) and pick one from the All tags picker to narrow the conversation list to that tag; the active tag shows as a chip you can clear with its ×. A conversation row also shows up to two of its tag pills. Because these are contact tags, they drive more than the inbox filter too: they build segments for broadcasts, the Has tag condition in a flow, and the Tag Action step that applies or removes them automatically.

​

One contact, two threads

A contact is one CRM record but can have up to two separate conversation threads: DMs and Comments. Someone who both messages your Facebook page and comments on a post has a row on each tab: one conversation under DMs, one under Comments, because a public comment and a private DM are answered differently. The list shows one kind at a time. The DMs / Comments toggle sits directly under Search conversations, above the channel pills, and it’s always visible. DMs is selected by default and there is no All, so the two kinds never appear in the same list. If you’re hunting a comment you replied to and can’t find it, switch to Comments. They stay separate throughout. Archiving or deleting one thread leaves the other untouched.

​

Choosing where your reply goes

When a conversation spans more than one channel, a Reply on strip sits above the thread with a pill per channel, each carrying its own unread count. Pick one and your reply, the messaging-window countdown and the template picker all follow it. Two pills on the same platform are labelled with the customer’s address on it, so you can tell them apart. DMLY preselects where the customer last wrote to you, and falls back to WhatsApp when nobody has written in yet or two channels tie. Arriving from a Message on WhatsApp button preselects WhatsApp instead. Your own pick sticks for that conversation. A contact you have a phone number for but no WhatsApp history with also gets a WhatsApp pill, so you can start there. It shows as template-required, because there is no open window yet, and the WhatsApp identity is only created when the message actually sends. On that first WhatsApp message, if you have more than one WhatsApp number connected, a Send from picker appears above the thread. It starts on your Default WhatsApp number and it narrows the template picker to that number’s templates. A WhatsApp conversation that is already running has no picker; it always replies on the number it is already on.

​

What you can send

From the reply box: A few rules that shape what you’ll actually see:

• SMS is text only. The media, file and microphone buttons are hidden on SMS conversations.
• Templates are WhatsApp only, and the picker only lists templates Meta has approved. You fill in each placeholder before it sends; a template with an empty {{1}} is rejected rather than sent with a gap showing.
• Booking links and payment links send as ordinary text. They’re a link in a normal message, not a special card. Request a payment creates the payment link for you and sends it; the booking picker only appears if you have active meeting types with a public booking page.
• Forms are WhatsApp only, and they are not templates. The picker lists your draft and published forms. The form is the whole message, so you don’t type anything alongside it, and the icon greys out once the 24-hour window closes. See WhatsApp Flows.
• Suggest a reply with AI appears only when AI is set up for your workspace and your plan includes it.

​

When a message won’t send

WhatsApp: the 24-hour window has closed

WhatsApp allows free-form replies only for 24 hours after the contact’s last message. Once it closes, DMLY blocks the send. This is Meta’s rule, enforced on our side too, so there’s no workaround in the reply box. To re-engage, send an approved template. See WhatsApp limits.

Messenger or Instagram: the 7-day window has closed

You can reply for 7 days after the contact’s last message. After that, you can only message again once they send something new. Replying to a public Comment is not subject to this; the window applies to DMs.

TikTok: the 48-hour window has closed

TikTok allows replies for 48 hours after the contact’s last message, and DMLY enforces it on the server for people as well as bots. There are no templates and no extended allowance for a human agent, so 48 hours is the whole of it: the contact has to message you again before you can reply. A contact you’ve never had a message from has no open window at all. The countdown chip in the conversation header names the window on hover. See TikTok.

The contact is blocked

Blocked contacts hide the reply box entirely and the block is enforced on the server, so nothing gets through. Use Unblock contact in the details panel to message again.

None of these windows apply to a public Comment reply, on any platform. They govern DMs only, which is why the countdown chip doesn’t appear on a comment thread. A block is the exception: blocking someone closes their comment thread to you as well.

​

Working as a team

The Inbox assumes several people are in it at once, so a few things happen without you asking:

• Replying assigns the conversation to you. By default the conversation follows whoever answered it last, so if a teammate replies to a chat assigned to you, it becomes theirs, quietly. Worth knowing before you wonder where your queue went. An admin can change that rule, and can have new conversations shared out round-robin, in Conversation settings. See assigning chats.
• You can see when a teammate is typing. Above the reply box you’ll see <name> is typing… on every channel, so two people don’t answer the same message. If the contact is typing, that takes precedence in the display.
• Notes and @mentions are for the team. Internal notes in the details panel are never sent to the contact, and mentioning a teammate pings them. See notes and collaboration.

​

Taking over from the bot

If an automation is handling a conversation and you want to step in, just reply: by default a teammate’s reply is the takeover. It stops every automated reply on that conversation (flows, sequences, AI, auto-replies) while leaving you free to type normally. Pause bot (human takeover) in the details panel does the same thing deliberately, and Resume bot hands it back. Some things pause the bot for you too: an AI agent handing over to a human, a flow with a handover step, and blocking a contact all set it. If the contact was part-way through a flow when you took over, that run is parked rather than cancelled: it keeps its step, the answers already given, and the remainder of any wait. A banner in the details panel names it and offers Resume, Skip this step and End automation, and Mark as done asks what should happen to it before it closes the conversation. See notes and collaboration. Whether a reply takes over, when the bot may have the conversation back, who owns a chat after a reply, whether new chats are shared out round-robin, when a closed conversation reopens, and whether the AI may answer at all are all workspace-wide settings an admin sets once, on the Conversation settings tab.

​

New messages and sound

A chime plays for each new inbound message while the DMLY tab is open and in focus. It’s on by default and you can mute it from the Inbox; the setting is per browser, so muting on your laptop doesn’t mute your colleague’s. The Inbox updates live when real-time delivery is available, and falls back to refreshing every few seconds when it isn’t. Either way, new messages still arrive without you reloading the page. The chime now fires from both paths too, so a dropped real-time connection doesn’t leave you with a silent inbox. If you switch away from the DMLY tab, there’s no chime to hear, so the first time you click or type anywhere in the Inbox, your browser asks permission to show desktop notifications. Grant it, and a new message from a contact while you’re on another tab pops a system notification naming the contact with a preview of the message; select it to bring DMLY to the front and jump straight into that conversation. Decline, and background messages get no sound at all; nothing plays while the tab is hidden. The chime just resumes for whatever arrives next once the tab is focused again. The same mute setting silences both.

​

Who can see the Inbox

The Inbox is a permission-gated area: a role without the Inbox module doesn’t see it in the sidebar at all. A teammate may also see a contact’s phone number and email masked rather than in full, so what they see may be less than what you see.

​

Related