Ticketing automation runs on the same Workflows engine as the rest of Aesthetix CRM. Ticket triggers and actions let you build processes around a specific support request. Ticketing's own automation page is at Tickets > Settings > Automation, and workflows can also be managed from Marketing > Workflows. For the full trigger and action catalog, see Triggers: Master Index and Actions: Master Index in Workflows & Automation.
Go to Tickets > Settings > Automation. The page lists workflows that start from or act on tickets, with their publication state and enrollment information. Select Create workflow to start one, or open an existing workflow to inspect its trigger and actions.

A ticket-triggered workflow carries the ticket that caused the enrollment, and ticket actions and ticket custom values use that ticket as their context. If a contact has a billing ticket and a membership ticket, each can enter a workflow separately, and an update applies to the ticket tied to that enrollment, not every ticket the patient has.
The Find ticket action changes which ticket later actions use. Handle its found and not-found branches deliberately so updates and replies go to the intended request.
Trigger | Use it when | Configuration |
|---|---|---|
Ticket Created | A new request needs assignment, acknowledgment, or routing. | Filter by priority, category, status, assignee, or ticket name. |
Ticket Updated | A change needs follow-up. | Use change conditions such as has changed or has changed to where offered, then filter the resulting state. |
Customer Replied (Ticket channel) | A patient adds a reply to a ticket. | Select the Ticket channel and apply ticket filters as needed. |
SLA Warning | A target is approaching its deadline. | Choose the target and conditions. Match your SLA warning setting. |
SLA Breached | A target was missed. | Filter by target or policy, then choose the escalation action. |
For Ticket Updated, decide whether you mean "priority is Urgent" (a state) or "priority changed to Urgent" (a change). The second prevents unrelated edits from starting the same process. Triggers do not replace the underlying SLA policy, so configure the policy and warning first (see Configure Ticketing SLAs and Business Hours).
Search for ticket in the action picker.
Action | What it does |
|---|---|
Create ticket | Creates a request with the configured fields and contact. Needs a contact in the enrollment. |
Find ticket | Locates a ticket by conditions, with found and not-found paths. If several could match, choose the supported preference such as the most recently created. |
Update ticket | Changes properties on the ticket in context. |
Assign ticket | Routes the ticket to selected users using the action's assignment options. |
Add internal note to ticket | Records team-only information. Does not email the patient. |
Send email reply to ticket | Sends a customer-facing reply on the ticket's email thread. |
Use the ticket-specific email reply action when the message should be a reply on the ticket. Before publishing a workflow that emails patients, review the source mailbox, recipients, and custom values, and keep PHI out of automated messages.
Open Settings > Automation > Create workflow.
Name it for its outcome, such as "Assign new billing tickets".
Add the ticket trigger and its filters.
Add a ticket action, notification, or condition.
Configure the action fields. Use the custom-value picker for values from the ticket or contact.
Review branches, contact context, and ticket context.
Save and test with a controlled example. Check the execution history and the resulting ticket.
Publish when it behaves as intended.
For workflows that begin outside Ticketing, use Find ticket before updating a ticket, or Create ticket when the process should open a new one.
Use If/Else to branch on ticket properties, for example sending Billing requests to the front desk and Post-Treatment Questions to a nurse. Use the custom-value picker to insert ticket fields such as name, ID, priority, or link into replies and notifications. Pick values from the picker instead of typing an assumed name.
From a ticket: open it, select Ticket actions in the top panel, choose Add to workflow, search for and select the published workflow(s), then select Add.

From the list: tick the tickets, choose Add to workflow in the bulk toolbar, review the count and workflows, and confirm.
Each ticket supplies its own context. Check the workflow's re-entry settings and execution records when one patient has several tickets. Only published workflows appear in the picker.
Goal | Workflow |
|---|---|
Route billing questions | Ticket Created, Category is Billing, then Assign ticket to the billing owner. |
Highlight urgent post-treatment questions | Ticket Created, Priority is Urgent, then send an internal notification with ticket details. |
Alert staff to a patient reply | Customer Replied (Ticket channel), then notify the assignee or team. |
Escalate a missed target | SLA Breached, then notify the practice manager with ticket name, priority, and link. |
Hand off between teams | Ticket Updated (status changed to a handoff status), then Add internal note and Assign ticket to the next owner. |
Open a ticket from another process | A form or tag trigger, then Create ticket for follow-up. |
Choose real recipients, conditions, and commitments before publishing.
Use narrow trigger filters and check the ticket's current state before sending an escalation or reply.
Ticket Updated triggers caused by a workflow's own updates are suppressed to help prevent loops, but do not rely on that instead of explicit logic.
An SLA warning or breach is an event. A later status change does not necessarily remove an existing enrollment, so use conditions to decide whether a later action still applies.
Issue | What to check |
|---|---|
A workflow is missing from Add to workflow | It must be published and in your account. |
A ticket event does not start the workflow | Publication state, trigger filters, event type, and re-entry settings. |
An action hits an unexpected ticket | The triggering ticket, and whether Find ticket changed the context. |
Create ticket is skipped | The enrollment needs a contact. Check the execution log. |
A reply is not sent | The email integration, ticket context, recipient, required inputs, and execution result. |
An SLA notification is missing | The policy, target, warning or breach event, and notification action together. |
Do I need a separate Ticketing automation tool?
No. Ticketing automation uses Workflows.
Can I start a workflow for an existing ticket?
Yes. Use Add to workflow from the ticket or from a selection on the list.
Can one patient's tickets be handled differently?
Yes. Each ticket's properties and enrollment context route it separately.
Does the internal note action email the patient?
No. Use Send email reply to ticket for a customer-facing reply.
How do I notify a manager when an SLA is missed?
Create a workflow with the SLA Breached trigger and a notification action.
What is the difference between "is" and "has changed to" on Ticket Updated?
"Is" checks the current state. "Has changed to" fires only when the value changes to that value.
Should automated replies include health information?
No. Keep automated emails general and keep clinical details in your EMR.
Can a workflow create tickets?
Yes, with Create ticket, as long as the enrollment has a contact.