GoHighLevel Parallel Dialer Setup: Smart Lists, Notes & Callbacks

To set up a Trellus power or parallel dialer in GoHighLevel, start with one location and a Contacts Smart List. Confirm the calling mode and numbers available to the rep, then follow a controlled call through to its contact note, selected tag and callback task. That gives you a working calling process before you add the rest of the team.

This guide covers the desktop Chrome-extension workflow in Trellus for GoHighLevel. A configured Opportunity pipeline or stage can also be a starting point. If you are still choosing a provider, use the separate HighLevel native calling, WAVV and Trellus comparison.

Explore the GoHighLevel demo to follow the Smart List, dialing and call-review story before setting up your location.

Before you start: one location, one list, one test contact

Choose a HighLevel location the rep can access, a small contact list and a phone number your team controls for the setup call. Give the test contact a clear name so the resulting note and callback are easy to find. Keep it out of customer campaigns and automated follow-up sequences.

• Access: Trellus installed in Chrome, the rep signed in, and the required site permission for the HighLevel domain.
• Calling: the Trellus plan and dialing mode you intend to use, a working microphone/headset and the approved calling numbers.
• Contact data: a valid primary or additional phone number on the HighLevel contact.
• Follow-up: the outcome, optional tag and callback task you expect to save.

For an agency-branded HighLevel domain, enable the required Activate Everywhere site access and confirm the exact domain during setup. Opening a different client location is a separate context check; a working list in one location does not establish the setup for every client.

1. Open the HighLevel Smart List you actually want to call

Open the intended location, then go to Contacts and choose the Smart List. Check the audience, active filters and sort order before opening the calling queue. Trellus starts from that current Contacts view, so you do not need to export the list into a separate CSV.

For a first pilot, use one clear audience: for example, inquiries assigned to one rep that still need an initial conversation. Confirm a few visible contacts match that definition. HighLevel’s Smart Lists documentation explains how contacts enter and leave a list as its conditions change.

Trellus reads valid primary and additional phone options from the linked contact. If a person has no callable number, fix the contact’s phone data first. A number written only inside a note or an arbitrary custom field is not the same as a supported phone option.

2. Start Trellus and check the location and contacts

Open Trellus alongside the Contacts view. Check that the queue belongs to the correct HighLevel location and contains the contacts you expect. Inspect the linked person and available phone choices before starting.

If your team works from Opportunities, use the pipeline or stage view confirmed during setup. Verify the linked contact and phone options there too. Treat that as its own acceptance check rather than assuming every Opportunity screen behaves like a Contacts Smart List.

When switching lists or client locations, pause and verify the new context before continuing. The rep should be able to explain which audience they are calling without relying on a previous browser tab’s state.

3. Choose power or parallel dialing and the calling number

Power dialing works one contact at a time. Parallel dialing makes multiple outbound attempts while the rep takes a live conversation. Use the mode available to your account and suitable for the list; the power-versus-parallel guide explains the workflow difference.

Confirm the calling-number setup with your administrator. A HighLevel location having a number does not automatically make it available in every Trellus calling configuration. Check the number the rep will present, inbound callback handling and the plan or account access required for that path.

Smart caller ID selects an available calling number using destination matching and recent use. Auto-rotate is a separate number strategy. Review the number-management guide when configuring the pool; phone-number rotation and a contact’s pickup-likelihood estimate solve different parts of the calling process.

For eligible parallel calls using the Trellus calling setup, select your saved voicemail and separate phone-screener introduction before calling. A screener introduction plays a recording when prompted and waits for a person; it does not hold an AI conversation on the rep’s behalf. Confirm these features in the exact number and calling setup you are launching.

4. Complete a controlled call and inspect what HighLevel receives

Call the test number your team controls. After the conversation, review the call notes or summary, choose the outcome and finish the result. Reopen that same HighLevel contact and inspect the saved information.

• Contact note: the selected outcome and available call detail, such as purpose, summary and transcript link.
• Selected tag: applied when call tagging is enabled and the rep completes the relevant result.
• Call context: the information belongs to the contact and location you started from.

For example, use a test conversation in which the contact asks for a product discussion next week. The note should describe that agreed next step. Check the saved note itself; seeing text in the Trellus review panel is only the first half of the handoff.

Agree with the team which tags should be used. A saved outcome in a note and a HighLevel tag are separate records. Selecting an outcome does not mean every similarly named tag or workflow has been configured.

5. Create the callback and check its owner

Schedule the callback in Trellus, then inspect the contact-linked Trellus Callback Task in HighLevel. Confirm its due date, time, contact and assigned rep. Trellus can assign the task to the creating rep when their HighLevel identity is available; verify the owner instead of assuming it.

Ask the rep to find that callback from the place they normally manage their next work. This catches a common setup gap: a task exists, but the person responsible for calling does not see it in their routine.

A promised callback for next Tuesday is different from handling two people answering a parallel call block at once. If simultaneous answers matter to your workflow, test that case separately with controlled numbers and inspect what each person hears.

6. Check the team experience around the call

Once the HighLevel handoff works, add the team features you plan to use. Evaluate live coaching during a supported call in a coaching-enabled workspace. Use practice bots to rehearse an objection before the next block, or a Salesfloor room for a shared calling session.

For reporting, count attempts, connected calls and booked meetings separately. The Trellus MCP documentation explains how an authorized AI assistant can read call metrics and selected sessions. MCP access follows the signed-in person’s permissions; it does not automatically grant a client access to another client’s calls.

Agency setup: branded HighLevel domain or branded dialer?

These are different projects. Running Trellus on a compatible agency-branded HighLevel domain means confirming site access and the calling workflow on that domain. Offering the dialer under your own product name means scoping a white-label Trellus workspace, its branding, domain, sign-in, support responsibilities and product features.

For an agency pilot, check one representative client location from the rep’s account as well as the administrator’s. Record who manages users, calling numbers, support and billing. Repeat the saved-note, selected-tag and callback checks before expanding to another client configuration.

Troubleshoot the part that failed

• Trellus does not appear on the branded domain: check the extension is enabled, the exact domain has the required site access and the supported HighLevel view is open. Confirm the domain with Trellus if it still does not activate.
• The queue shows the wrong audience: verify the location, Smart List and filters. Return to the intended list and let its current contacts load before restarting the call block.
• A contact has no phone choice: inspect the primary and additional phone fields for a valid number. Check the linked contact when starting from an Opportunity.
• A saved note or tag is missing: confirm the result was completed, the rep is still signed in to the right location and call tagging is enabled if you expect a tag. Inspect the note and tag separately before retrying.
• The callback is hard to find: check its contact, due date and owner in HighLevel. Confirm the creating rep’s identity is available and the rep is looking at the right location.
• A number strategy or screener option is unavailable: check the plan, account access and calling-number path. Bring that configuration to support rather than assuming a feature shown in another setup is enabled in yours.

Your rollout acceptance note

Copy this checklist into your team’s rollout document. Use internal record links for the test contact and call instead of copying private conversation details into a shared public document.

Location and exact domain: ____
Rep and Trellus access checked: ____
Contacts Smart List or confirmed Opportunity view: ____
Calling mode and number setup: ____
Controlled test call and contact record: ____
Saved note and available transcript link checked: ____
Selected tag checked, if used: ____
Callback due date, contact and owner checked: ____
Rep can find the next callback: ____
Manager can review the call and reporting: ____
Setup owner and next rollout decision: ____

A completed setup means the rep can start from the right list, finish the call and leave the next person a usable record. Use the GoHighLevel integration page to plan that walkthrough with Trellus, or compare HighLevel calling options before choosing the configuration.