Comments and direct messages from your connected Instagram, Facebook, and Threads accounts arrive in one queue, with the account, message type, and status clear before you open anything. Read the exchange, keep the post beside it, reply, leave a note for the next person, and mark the work resolved when it is actually finished.
3 days free. Cancel anytime.
A comment makes more sense when the post is still in sight. Maeve keeps the message thread in the middle and puts the connected post beside it on wide screens, with the media and caption right there. You can see what the person saw, which account answered, and which comment the reply belongs under.
The conversation header holds the work around the reply too: assignment, inbox tags, read state, resolution, the private Notes view, and a link back to the post.
Opening a conversation can clear its unread state, but that says nothing about whether someone still needs an answer. Needs Action and Resolved keep the work separate from the notification. Resolve one message, resolve the whole conversation, or clear the visible filtered batch when the queue is under control.
If the customer comes back or the issue was closed too soon, reopen the message or conversation and it returns to the work queue with its history intact.
Switch from Messages to Notes and leave the handoff beside the conversation. The customer never sees it. Your teammate does, along with who wrote it and when. Notes can be removed when they go stale, and quick emoji reactions let someone acknowledge the handoff without adding another paragraph.
The queue is built for the whole pass through a conversation, from finding the right thread to leaving it in a state the rest of the team can trust.
The inbox keeps the response close to the post, the schedule, and the workspace vocabulary around it.
One queue for the comments and direct messages that come back to your connected Instagram, Facebook, and Threads accounts. Open a conversation, read the thread in order, see the post beside it when one is attached, and reply from your laptop.
The inbox has channel filters for Instagram, Facebook, and Threads. It handles comments across those connected accounts, with direct messages where the platform connection supports them.
Yes. They share one queue, with separate filters for Comments and DMs. The filter bar also has Reviews and Mentions, plus status filters for All, Unread, Needs Action, and Resolved.
Yes. A customer message lands in the queue, a teammate can take the conversation, add tags, reply, and leave an internal note for whoever handles it next. It is built around activity on your connected accounts rather than broad social listening across the web.
New activity from connected accounts is collected in the shared queue. The unread count and conversation list update as inbox data changes, so the team works from the same current view without checking each social app in turn.
Where the platform allows it, yes. The reply composer can upload an attachment and shows its progress before sending. It also enforces platform rules, including Instagram's restriction on mixing text and media in the same direct message.
An optional five-second hold on an outgoing reply. Turn it on, press send, and an Undo button counts down before Maeve sends the message. The setting is off by default and stays set in that browser.
Yes. Every conversation has an Internal Notes view. Teammates with write access can add and delete notes, and react to a note with an emoji. Notes stay inside Maeve and never become part of the public conversation.
When the connected platform allows it, the message menu shows the moderation actions available for that message, including hide, unhide, or delete. Maeve also checks the workspace role before showing write controls.
Instagram and Facebook can close a direct-message reply window after the customer's last message. Maeve shows when the window has expired and locks the composer, so you can see the restriction before writing a reply the platform will reject.
Yes. A reply can target a specific comment, and the composer shows who you are replying to. The conversation keeps replies under their parent so a busy comment thread still makes sense.
Yes. Assign a conversation to a workspace teammate and add inbox tags for the client, issue, campaign, or follow-up you use internally. You can then filter the queue by tag, account, channel, message type, status, or search text.
When Maeve can connect a comment to its post, the conversation shows that post beside the messages with its media and caption. It is the same content you planned in the Calendar and wrote in the Composer, so the reply has its context without sending you back through the schedule.
Yes. Resolve one incoming message or the whole conversation, then reopen it if the work is not finished. Needs Action and Resolved filters keep that workflow separate from read and unread state, and Resolve Visible handles a filtered batch.