company logo

Help Center

Go to Aesthetix CRM
Terms & ConditionsPrivacy Policy
All collectionsTicketingTicketing Setup and EmailCreate Tickets and Connect Email Integrations in Ticketing

Create Tickets and Connect Email Integrations in Ticketing

Create tickets manually or from a contact record, connect the default email system or Gmail so patient emails become tickets, block senders, and verify email threading.

Create a ticket by hand when your team records a request, or connect a support email address so incoming emails become tickets automatically. Everything here starts from Tickets in the left sidebar, and email setup lives under Tickets > Settings > Integrations.

Before you begin

Use a user with permission to manage tickets. An administrator should configure email integrations and the ticket form. If you need to change the fields, order, or required information on the creation form, see Getting Started with Ticketing and Ticketing Settings first. The fields in your account may differ from the examples here.

Create a ticket manually

Use this for requests received by phone, in person, or through another channel.

  1. Open Tickets.

  2. Select New ticket.

  3. Enter a clear Ticket name that describes the request, for example "Question about membership billing date".

  4. Under Raised by, select the contact.

  5. Add the description and complete the fields on your form, such as status, priority, category, assignee, and due date.

  6. Use Attachment to add supporting files, if that field is on your form.

  7. Select Create ticket, or Create & add new to save this ticket and start another.

Ticket name and Raised by are required, along with any field marked required. The form preselects the defaults you configured, so review them before saving. If the contact does not exist and the picker does not offer contact creation, create the contact in Contacts and return to the form. Select Cancel to close an unused form. If you entered information, review the discard prompt.

Creating a ticket manually does not email the patient. Use the public reply composer when you want to contact them.

Create a ticket from a contact record

  1. Open the contact.

  2. Select the Tickets icon in the record's right-side toolbar.

  3. Select Add.

The ticket is created for that contact. The same panel lists the contact's existing tickets, which you can search or open.

Create tickets with workflows

The Create ticket workflow action opens a ticket as part of an automation, for example when a form submission needs follow-up. See Automate Ticketing with Workflows.

Choose your email provider

Open Tickets > Settings > Integrations. The built-in email service appears under Default email system, and Gmail appears under Additional providers.

Option

What you need

How it is used

Default email system

A dedicated domain you own and have verified in Email services

Set up support addresses on the domain to receive requests and send ticket replies.

Gmail

A supported Google Workspace account and permission to authorize it

Connect the mailbox through Google's authorization flow.

While the default email system is active, the Gmail controls can be disabled with a message explaining that you must disconnect the current provider to switch. Follow what your account shows. Do not assume both provider types can be active at the same time.

Connect the default email system and add support addresses

Select a verified domain

  1. Open Settings > Integrations.

  2. In Default email system, review the dedicated-domain configuration.

  3. Choose your domain under Verified domain.

  4. If no suitable domain is available, select Add a domain in Email services and complete that service's domain setup and verification.

  5. Return to Ticketing and check the connection state.

Add a support address

  1. Select Add support address.

  2. Confirm the displayed domain.

  3. Enter the first part of the Support email address, such as support or billing. The form adds the domain.

  4. Enter a recognizable Display name, such as "Your Practice Support".

  5. Select Save address, or Save and add another to continue.

Review the address list and the Replies go out as information. The default support address is the sender used for manually created and workflow-created tickets. Tickets created from an email keep the mailbox that received it for replies. You can add multiple addresses on the selected domain, for example separate billing and front desk addresses.

Connect or reconnect Gmail

  1. Open Settings > Integrations and expand Additional providers.

  2. Review the Gmail, Google Workspace, OAuth option and any provider-switching message.

  3. If available, select Add and follow Google's sign-in and authorization steps for the support account you want to use.

  4. Return to Ticketing and confirm the connection is active.

  5. If a connection has expired, select Reconnect when available and authorize again.

Choose the support mailbox deliberately during authorization. If the control is disabled, resolve the reason shown on the integration screen before repeating the sign-in. Reconnecting does not necessarily import the mailbox's older emails.

Block unwanted senders

  1. In Integrations, find Configuration > Blocked senders.

  2. Enter an email address or a domain in the format the field shows, such as [email protected] or @example.com.

  3. Select Add and review the entry.

Blocked senders do not create tickets. Blocking a domain affects all mail from it, so use an individual address if that is your intent. The integration also filters automated replies, spam, and mail loops, so not every email that reaches a mailbox produces a ticket.

How email-created tickets work

When an eligible new email arrives at a connected support address, its subject becomes the ticket name and its content becomes part of the ticket history. The sender's email address links the ticket to an existing contact, or creates a contact when needed. The ticket also records its source and the receiving mailbox, which is worth checking when you have several support addresses.

Situation

What happens

A patient emails a connected support address

An eligible new request can create a ticket.

An agent replies to an email-created ticket

The reply continues the patient's original email thread.

An agent sends the first reply from a manually created ticket

A new outbound email thread begins. Later matching replies stay with the ticket.

An existing ticket is renamed

The internal name changes. The established email subject does not.

A message matches an existing ticket thread

It is added to that ticket instead of becoming a new request.

Keep replying from the ticket so the history stays together. Different requests from the same person can have separate tickets.

HIPAA note

Emails that create tickets, and replies sent from tickets, travel as regular email and can contain patient health details. Tell patients not to send clinical information, photos, or medical history to your support address. Keep clinical conversations in your EMR or another secure channel, limit which staff can view tickets, and avoid placing PHI in ticket names, replies, and attachments.

Confirm your setup works

  1. Send a test request from an outside email address to your support address.

  2. Confirm that a ticket appears, linked to the correct contact, with the expected subject and source.

  3. Open the ticket and send a test reply only to your test recipient.

  4. Check the From address, then reply from the test address and confirm the reply lands on the same ticket.

Repeat this check after setting up or reconnecting a mailbox.

Troubleshooting

Issue

What to check

A new ticket cannot be saved

Complete the name, contact, and other required fields. Read the validation messages beside the fields.

A custom field is missing

Review the saved layout in Settings > Ticket configuration.

An incoming email does not create a ticket

Confirm the exact destination address, the provider connection, blocked senders, and whether the message belongs to an existing thread or is automated or filtered mail.

Gmail Add or Reconnect is disabled

Read the provider-switching message and connection state. Repeating authorization will not fix a disabled control.

Replies use an unexpected sender

Check the ticket's source mailbox and the default support address for manually created tickets.

Older emails are missing after reconnecting

Verify the mailbox and received dates. Reconnecting does not import the whole mailbox history.

Frequently Asked Questions

Can I create tickets without an email integration?

Yes. Manual creation works on its own. Set up a sending integration before relying on public email replies.

Can I have more than one support address?

Yes. On the default email system, use Add support address to add multiple addresses on your verified domain.

Does creating a manual ticket send an email?

No. Use the public reply composer when you want to contact the patient. Also check your workflows for any automatic acknowledgments.

Can I use Gmail and the default email system together?

Plan on one provider at a time. Your account may disable the other provider until you disconnect the current one.

Can I import old tickets?

Ticket import is not part of the documented creation screens, and connecting email is not a historical migration.

Why did an email not become a ticket?

It may be from a blocked sender, filtered as automated mail, spam, or a loop, or it may match an existing ticket thread.

Does renaming a ticket change the email subject?

No. Renaming is internal and keeps the established subject so replies stay in the same thread.

Is it safe to email health details through a ticket?

Avoid it. Ticket emails are regular email. Keep clinical details in your EMR and share only what is needed.

Did this answer your question?
😞
😐
😁