GoHighLevel Conversations Inbox: Team Management (2026)

By Dr Priya Jaganathan, GoHighLevel Certified Admin · HL Growth Partner, Australia · Updated 3 October 2026 · 10 min read

Some links below are affiliate links — if you sign up through them, HL Growth Partner may earn a commission at no extra cost to you. It never changes what we recommend.

The GoHighLevel Conversations inbox pulls every SMS, email, DM, chat and call into one place, which is brilliant until three people are working it and nobody is sure who should reply. Most "lost leads" we find in audits are sitting in a shared inbox everyone assumed someone else had handled.

This guide shows you how to run the HighLevel unified inbox for teams: who owns which conversation, how to see only your own work, how to collaborate without the customer seeing it, where AI fits, and the daily triage SOP we install for clients so no message goes unanswered.

What the GoHighLevel Conversations inbox actually does for a team

Every message from a contact lands on that contact's thread, regardless of channel. A lead who comments on Instagram, then texts, then emails a quote request shows up as one continuous conversation rather than three disconnected ones.

HighLevel's redesigned Conversations experience uses a multi-panel layout and upgraded filtering, including tag filters with AND/OR logic. If you are still getting used to the basics of replying by text, start with our walkthrough of two-way SMS conversations in GoHighLevel before layering on team rules.

The inbox is a shared workspace, not a personal one. That is the mindset shift. Once you have more than one person replying, you need rules for ownership, visibility and handoffs, or the speed advantage disappears.

The four tabs your team will live in

• Unread shows only conversations with new or unread messages. This is the queue.
• Recents shows the most recent activity, read or not.
• Starred holds conversations someone flagged as important.
• All is everything, which is useful for searching but useless for triage.

Assigning conversations so every lead has one owner

Ownership in HighLevel follows the contact's assigned user. When a contact is assigned to a team member, the Conversations filter for assigned user shows that person every thread they are responsible for.

Automatic assignment with Workflows

The Assign to User Workflow action is how you take the human out of routing. Select one user for direct assignment, or several users to rotate new contacts round robin, and choose whether traffic is split equally or with custom weightings.

There is also an option to apply the action only to unassigned contacts. Turn it on, otherwise a returning customer could be reassigned away from the person who already knows them.

A typical setup is a Workflow triggered by an inbound message or form submission, filtered by source or channel, that assigns the contact and notifies the owner. Pair it with internal team notifications so the assigned user hears about it immediately rather than at their next inbox check.

Filters that make ownership visible

• Assigned to a specific user, or "Logged In User" so every teammate can save a personal view.
• Unassigned conversations, which is the triage owner's most important view.
• Follower, for conversations someone is watching without owning.
• Mention, for threads where a teammate has been @mentioned.

Bulk actions let you mark conversations read or unread and add or remove stars in one pass.

The "Only Assigned Data" permission: privacy versus coverage

HighLevel's Only Assigned Data user permission limits a user to their own data. With it switched on, the user sees only contacts assigned to them and the corresponding conversations, plus opportunities they own and tasks or appointments linked to them.

This is the right choice for commission-based sales teams where reps should not see each other's leads. It is the wrong choice for a front-desk or support team that needs to cover each other's shifts.

Plan cover before switching it on: if a rep is sick, someone with full access must step in. We cover the full role design in sub-account permissions and user roles, including how to keep a manager seat that sees everything.

Internal comments and @mentions: talk about the lead, not to the lead

Internal Comments let your team discuss a conversation inside the thread without the contact seeing it. In a conversation, use the channel switcher to choose Internal Comment, type your note and @mention a teammate.

Mentioning a user adds them as a follower of the conversation and gives them access to that contact and conversation. They are notified of the mention and of new messages on that thread. HighLevel documents the steps in its help article on adding internal comments and mentioning users.

Use internal comments for every handoff. "@Sam, quote request for a 3-bedroom clean, wants Saturday, I've sent pricing" saves the next person from scrolling back through 20 messages.

Snippets: consistent replies without sounding robotic

Snippets are saved Text or Email replies your team can drop into a conversation. You create them under Conversations or Marketing, add custom values for personalisation, and organise them into folders such as "Bookings" or "Pricing".

Build snippets for the ten questions you answer every week: hours, service areas, pricing ranges, booking links, what happens next. Then coach the team to edit the first line so it reads as a reply, not a form letter.

Not on HighLevel yet? Start with a free 30-day trial here — long enough to build everything in this guide before you pay a cent.

Manual replies versus Conversation AI in a team inbox

Conversation AI has two modes that matter for teams. In Suggestive mode, the AI drafts reply options that a team member reviews, edits and sends; nothing goes out automatically. In Auto-Pilot mode, the bot replies on supported channels by itself after a configurable delay.

Our recommendation is to start in Suggestive mode, review a few weeks of drafts, then move specific channels or after-hours periods to Auto-Pilot. Decide in advance when the AI stops and a human takes over, and build that into a Workflow; our guide to Conversation AI human handoff shows how.

Response-time habits and SLA reporting

Conversation SLAs let you set a response-time goal that counts down on each incoming message. Timers change from grey (on track) to orange (due soon) to red (overdue), so the team can see what's urgent at a glance.

To switch them on, open Conversations in the sub-account, go to the Settings tab and turn on SLA Settings. You can use one target across the board or set different targets for channels such as Email, SMS, Facebook and WhatsApp. HighLevel's article on how to set up Conversation SLAs has the current steps.

The SLA Performance Dashboard then shows how many messages met or breached the target, average response times and trends by user and channel. HighLevel notes its data is available from 23 May 2026, so older periods won't appear.

A breach shows as a visual flag, not an automatic rescue, so habits matter more than the dashboard. For the first-touch automation that buys your team time, see our speed-to-lead 5-minute response workflow.

Habits that keep response times tight

• Check Unread at set times, not "when I get a minute".
• Reply first, then do the admin. An acknowledgement within minutes beats a perfect answer tomorrow.
• Star anything waiting on someone else and review Starred at end of day.
• Never leave Unassigned non-empty at close of business.

Inbox triage SOP with an example roles table

Here is the SOP we install for a five-person service business. Keep the structure: one triage owner at any time, and a named owner for every channel.

The daily routine

• Start of day: triage lead clears Unassigned, assigns overnight messages and reviews AI replies sent after hours.
• Every hour: each owner clears their own Unread view and checks for orange or red SLA timers.
• Handoffs: always via an internal comment with an @mention, never by a verbal "can you grab that one".
• End of day: owners review Starred, the triage lead confirms Unassigned is empty, and a manager glances at the SLA dashboard.

Common mistakes to avoid

• Leaving conversations unassigned and relying on "whoever sees it first".
• Switching on Only Assigned Data for everyone, then discovering nobody can cover a sick day.
• Typing internal notes in the reply box and accidentally sending them to the contact.
• Running Conversation AI on Auto-Pilot with no handoff rule, so the bot and a human reply over each other.
• Marking messages read to clear the badge without actually replying.
• Assigning by Workflow without "only apply to unassigned contacts", so loyal customers get bounced to new reps.

If you want a Conversations inbox set up with routing, permissions, SLAs and a triage SOP your team will actually follow, book a strategy call with the HL Growth Partner team.

Book Your Strategy Call →

Or if you just need the software first: grab the 30-day HighLevel trial and book us when you're ready to scale it.

Frequently asked questions

Which channels does the GoHighLevel Conversations inbox include?

The Conversations inbox brings together email, SMS, Google Business Profile messages, website live chat, WhatsApp, Facebook Messenger, Instagram DMs, and phone calls and voicemails. Each channel needs to be connected in the sub-account before its messages appear. Everything for a contact shows on one thread.

How do I see only the conversations assigned to me?

Use the assigned-user filter in Conversations and choose "Logged In User". That view updates for whoever is signed in, so every teammate gets a personal queue from the same setting. It is a view, not a restriction: unless the Only Assigned Data permission is on, the user can still open other conversations.

What does the Only Assigned Data permission do?

It restricts a user to the contacts assigned to them and the conversations for those contacts, along with opportunities they own and their own tasks and appointments. It suits sales teams where reps shouldn't see each other's leads. Make sure someone with full access can cover when that user is away.

Can customers see internal comments?

No. Internal Comments are private to your team and are not sent to the contact. Choose Internal Comment in the channel switcher before typing, and @mention a teammate to notify them and add them as a follower.

Should Conversation AI run in Suggestive or Auto-Pilot mode?

Start in Suggestive mode, where the AI drafts replies and a person reviews and sends them. Once the drafts are reliably accurate, move after-hours or FAQ-heavy channels to Auto-Pilot. Always set a clear rule for when a human takes over.

How do I track team response times in HighLevel?

Turn on Conversation SLAs from the Settings tab in Conversations and set a response-time target for all channels or per channel. The SLA Performance Dashboard then reports on met and breached messages, average response times and trends by user and channel. Its data starts from 23 May 2026.

How can I automatically share new conversations across my team?

Use a Workflow with the Assign to User action and select several users to rotate new contacts round robin. You can split traffic equally or by custom weightings. Enable the option to apply only to unassigned contacts so existing customers keep their current owner.

Related Articles on HL Growth Partner

Connecting more channels

• GoHighLevel Instagram DM automation
• WhatsApp integration setup and pricing
• Chat widget setup guide

Routing and team workload

• Territory routing and lead assignment
• Tasks and team workload management

Never missing a follow-up

• Missed call text back setup
• Contact timeline and activity history