Home/HighLevel/Features/Integrations/How HighLevel creates tickets and connects email inboxes

Agency, Settings and Integrations

How HighLevel creates tickets and connects email inboxes

In short

HighLevel lets you open support tickets by hand or automatically from incoming emails. You can link a verified domain or a Gmail mailbox, add multiple support addresses, block unwanted senders, and test that replies stay attached to the right ticket.

AreaIntegrations · Ticketing
Used forDigital marketing agency, Ecommerce store, Consulting firm
Setup steps36 steps in 6 tasks
Last updatedNovember 17, 2026

01Who this is for

  • Support managers can record requests right away when callers call in, ensuring every issue has a ticket.
  • Small business owners can route customer emails to tickets, keeping their support inbox organized.
  • Administrators can control which email addresses create tickets and prevent spam from opening new requests.

02Tickets and email integrations, explained

The ticket feature records support requests inside HighLevel. A ticket can be entered manually or generated when a customer emails a connected address. The system links the email thread to the ticket, so all replies stay in one place.

Ticket creation screens use the subaccount’s saved ticket form, which defines fields such as status, priority, and assignee. Email integrations live under Tickets > Settings > Integrations, where you choose either a default domain or Gmail as the provider. Blocked senders are managed in the same integration area to stop unwanted mail from turning into tickets.

03How businesses use tickets and email integrations

  • Digital marketing agency. The agency creates tickets manually for client specific requests that come in via phone. It also connects its agency domain so client emails automatically become tickets, letting the team track all communication in one view.
  • Ecommerce store. The store links a Gmail mailbox that handles order related questions. Incoming order emails generate tickets, and the store blocks generic spam domains to keep the ticket list clean.
  • Consulting firm. The firm adds several support addresses, support@consult.com, billing@consult.com, on its verified domain. Each address routes different request types to separate tickets, allowing specialists to own the right queue.

04Before you start

  • Use a user account that has permission to manage tickets.
  • An administrator must set up email integrations and configure the ticket form before creating tickets.

05How to set up and use tickets and email integrations in HighLevel

Create a ticket manually

  1. Open Tickets in the subaccount.
  2. Select New ticket.
  3. Enter a clear Ticket name that describes the request.
  4. Choose the customer contact under Raised by.
  5. Fill the description and any required fields such as status, priority, category, assignee, and due date.
  6. Add supporting files using the Attachment field if it is shown.
  7. Click Create ticket or Create & add new.
  8. If the contact does not exist, create the contact in Contacts then return to the form.
  9. If you need to cancel, click Cancel and respond to the discard prompt.

Choose your email provider

  1. Open Tickets > Settings > Integrations.
  2. Find the Default email system and the Gmail option under Additional providers.
  3. Read any provider switching message to see which provider is currently active.

Connect the default email system and add support addresses

  1. Open Settings > Integrations.
  2. In Default email system, view the dedicated domain configuration.
  3. Select your domain from Verified domain.
  4. If no domain is listed, click Add a domain in Email services and complete its verification.
  5. Return to Ticketing and verify the connection state.
  6. Click Add support address.
  7. Confirm the displayed domain.
  8. Enter the local part of the address (for example, support).
  9. Provide a recognizable Display name.
  10. Choose Save address or Save and add another.
  11. Review the resulting address list to ensure the new address appears.

Connect or reconnect Gmail

  1. Open Settings > Integrations and expand Additional providers.
  2. Review the Gmail, Google Workspace · OAuth option and any provider switching notice.
  3. If Add is shown, click Add and follow Google’s sign in and authorization flow for the support mailbox.
  4. If the control is disabled, resolve the reason shown in the integration screen before repeating the sign in flow.
  5. Return to Ticketing and confirm the connection is active.
  6. If the connection has expired, click Reconnect and repeat the authorization steps.

Block unwanted senders

  1. In Integrations, locate Configuration > Blocked senders.
  2. Enter an email address or a domain (for example, name@example.com or @example.com).
  3. Click Add and verify the entry appears in the list.

Confirm that your setup works

  1. Send a test email from a customer side address to the configured support address.
  2. Check that a ticket appears, is linked to the correct contact, and shows the expected subject and source.
  3. Open the ticket and send a reply only to the test recipient.
  4. Verify the From address and that a customer reply returns to the same ticket.

06What it looks like in HighLevel

07Settings that matter

  • Default email system. Determines which verified domain receives support emails and which address is used for outbound ticket replies.
  • Additional providers. Holds the Gmail integration option and shows its connection status or any provider switching messages.
  • Blocked senders. Lists email addresses or domains that are prevented from creating tickets.

08Things to know before you rely on it

  • Only one email provider can be active at a time; Gmail controls are disabled while the default email system is connected.
  • Blocking a domain stops all mail from that domain from generating tickets; use a single address if you only want to block one sender.
  • Email created tickets are generated only from eligible support addresses; automated, spam or looped messages are filtered out.

09If something goes wrong

  • New ticket cannot be saved. Make sure the name, contact, and any other required fields are filled. Look for validation messages next to the fields.
  • A custom field is missing. Check the saved ticket form layout for the missing field.
  • An incoming email does not create a ticket. Confirm the exact destination address, provider connection, blocked senders list, and whether the message belongs to an existing thread or is filtered as spam.
  • Gmail Add or Reconnect is disabled. Read the provider switching message and connection state; a disabled control cannot be fixed by repeating authorization.
  • Replies use an unexpected sender. Review the ticket’s source mailbox and the default support address used for manually created tickets.
  • Older emails are missing after reconnection. Verify the mailbox and received dates with your administrator; reconnection does not automatically import the full mailbox history.

10How it connects to the rest of HighLevel

Michael's take

Michael Reimer
Michael ReimerFounder of CRM Pros, HighLevel Commander and Certified Admin

Most people try to add a support address before they verify a domain. Verify the domain first, then add the address so the system can link the mailbox correctly.

If I were setting this up, I would start with a quick test email after connecting the inbox. Seeing the ticket appear and the reply stay in the same thread gives confidence that the whole flow works.

Get More InformationOpens on HighLevelPublished November 11, 2026 · Updated November 17, 2026

Common questions

Common questions about tickets and email integrations.

Can I create tickets without an email integration?

Yes. Manual ticket creation works independently of any connected inbox. You can add an email integration later if you need public replies.

Can I have more than one support address on the default email system?

The integration lets you add multiple support addresses on the selected domain using the Add support address button.

Does creating a manual ticket itself send an email?

A manual ticket does not automatically send an email. Use the public reply composer or a workflow triggered email if you need to contact the customer.

Can I import old tickets in this workflow?

CSV import is outside the scope of this guide and not part of the documented creation screens. Connecting email does not migrate historical tickets.

Next step

Pick the features that matter. Then get the plan that unlocks them.

Explore the features you want, start with the five at the top, and upgrade through my link when you are ready. The bonuses and the team come with it.

The features directory explains every HighLevel feature in plain English. Browse it to see what the platform can do.

Back to the FeaturesSee the full details
⌃

Site preview

Explore the next page

This destination is reserved in the page inventory and is not built yet.