Configuring Custom Conversation Views in HighLevel for Teams
Learn how to build saved conversation views, use dynamic user assignments, and organize team communication workflows inside HighLevel sub-accounts.
By Nexus Hub editorial · 5 min read

As sub-accounts scale, the standard Conversations inbox quickly turns into an operational bottleneck. When inbound SMS messages, webchat inquiries, automated appointment confirmations, and marketing emails share a single timeline, reps spend unnecessary time sorting through noise to locate qualified opportunities.
Relying on individual team members to manually construct inbox filters during each shift creates inconsistency and introduces human error. HighLevel addresses this friction through Conversation Views, a feature that allows administrators to save, configure, and distribute targeted views across the entire team.
The Purpose of Custom Views in HighLevel
A Conversation View functions as a filtered, saved segment of your primary inbox. Instead of presenting all communications in one chronological list, views isolate threads based on predefined parameters such as channel, tags, or message history.
Separating operational traffic from sales conversations protects response times on high-intent inbound inquiries. Typical applications include:
- Separating automated system alerts from manual prospect responses.
- Isolating SMS communications requiring immediate attention from long-form email threads.
- Creating dedicated holding queues for unassigned leads awaiting triage.
- Monitoring conversations where an SLA threshold is approaching or has lapsed.
Step-by-Step Configuration of a Custom View
Setting up a custom view takes only a few minutes within the sub-account dashboard. Follow these steps to establish a clean workflow:
- Open the sub-account and navigate to the Conversations tab in the left-hand navigation menu.
- Locate the Views selector at the top of the interface and click the Create View button.
- Assign a practical name to the view. Use direct labels like 'Open SMS Leads' or 'Urgent Support' rather than vague titles.
- Define your filtering criteria by combining conditions using AND/OR rules.
- Review the preview pane to confirm the data matches your expectations, then save the view.
When building filters, combine channel parameters with contact tags. For instance, filtering by the SMS channel alongside a tag indicating high purchase intent creates an inbox dedicated exclusively to prospects ready for direct sales interaction.
Filter rules evaluate incoming messages in real time. As contacts meet or drop outside the assigned criteria, threads will automatically appear or disappear from the view without requiring a manual page refresh.
Leveraging Dynamic User Filtering
Creating separate static views for every rep on a roster introduces administrative clutter. If an agency employs five sales representatives, creating five identical inboxes filtered by individual names creates unnecessary maintenance when staff changes occur.
HighLevel solves this through dynamic assignment filtering. When building a view, set the 'Assigned To' condition to 'Logged In User' instead of selecting a specific staff member. This single configuration alters the display based on who is viewing the dashboard.
- Representative A sees only the conversations assigned directly to their profile.
- Representative B opens the exact same view and sees their assigned pipeline.
- Account administrators can still toggle between specific assignees when conducting pipeline reviews.
This practice allows you to maintain one centralized set of operational standards that functions universally across your entire team.
Deploying and Managing Shared Views Across Teams
Once a view is configured, administrators have control over its visibility. By default, newly created views may be private to the user who built them. To make a view functional across an agency, open the settings menu alongside the view title and select the sharing preferences.
When managing shared views, establish a baseline structure that every sub-account adheres to. A standard deployment usually includes three primary views:
- Triage Queue: All unassigned incoming conversations across every channel, filtered to manual inbound messages only.
- Active Assigned: All open threads where the assigned user matches the logged-in user, filtered for unread or pending responses.
- Escalations: Contacts tagged for management review or conversations exceeding your target response window.
Conduct regular audits of your saved views. Remove redundant presets, verify that user assignments remain dynamic, and update tag criteria whenever sub-account automation logic changes.
Need help applying this to your account?
Ask inside Nexus Hub — Charles is live Mon, Wed and Fri.
How to Configure and Manage SMS Group Chats in HighLevel
How to Configure Automated Instagram DM Workflows in HighLevel
Syncing External Dialer Call Records into HighLevel Conversations
Nexus Hub editorial
How this was researched, tested, and corrected: Nexus Hub editorial standards. Spotted an error? Report it and we will check it.
Nexus Hub is an independent community and educational resource. It is not affiliated with, endorsed by, or sponsored by HighLevel.