Ticket operational context
Use Tickets to connect support requests to people, companies, activity, priority, and resolution work.
Inspect the customer memory that work depends on: record identity, relationships, activity, ownership, and recent context.
What a Ticket record contains
A Ticket holds the request subject, status, priority, assigned owner, linked person and company, conversation history, and resolution activity.
Max reads ticket context to understand what a customer needs, what priority it carries, and what has already been tried. Studio workflows use ticket fields to route, escalate, or update status automatically.
Connecting Tickets to the full relationship
A ticket that links only to an email address without a connected person or company record is an isolated task — it gives AI no account context.
Link each ticket to the person who submitted it and to their company. This lets Max understand whether the issue is from a high-value account, whether the same company has open deals, and whether a similar ticket was resolved recently.
How workflows use Ticket context
Studio can trigger on ticket creation, read its fields, and decide how to handle it: assign to the right team based on category, escalate based on priority or account tier, or notify an owner when status changes.
Ticket stage updates — from Open to In Progress to Resolved — are the signals that drive workflow execution. If stage is never updated, workflows that depend on it will not fire correctly.
Resolution and follow-up
When a ticket resolves, the activity log should reflect what happened: what the issue was, how it was fixed, and whether follow-up is needed.
Max can generate a resolution summary from this history and suggest a follow-up task for the owner. For this to work, resolution activity needs to be logged in Frontline — not just closed in a separate tool.
How to use Tickets in support workflows
Use Ticket status, owner, customer, priority, and recent activity to decide whether support work needs reply, escalation, or waiting state.
A ticket without person or company context is hard for Max to summarize and risky for Studio to route automatically.
FAQs
What is a Ticket for?
A Ticket is the support work record. It tracks the request, status, owner, priority, related customer, and resolution activity.
What should I check before automating ticket routing?
Confirm the ticket has a clear category or status, owner rule, related person or company, and a safe escalation path for urgent or ambiguous cases.
How do CRM records improve AI workflows?
CRM records give Max and Studio shared customer memory: identity, relationships, deals, tickets, activity, and context that workflows can retrieve, summarize, update, or route around.
When should I create a relationship between records?
Create relationships when context should travel together: a person belongs to a company, a deal depends on contacts, a ticket affects customer health, or a workflow needs related records.
What should I check before changing the data model?
Check which workflows, summaries, views, and teammates rely on the field or relationship. Schema changes should preserve operational context and avoid breaking automation.
How should teams handle duplicate or incomplete records?
Prioritize records that affect active work. Merge or clean duplicates when they confuse ownership, customer context, workflow routing, or AI-generated summaries.
What makes CRM context trustworthy?
Trust comes from clear ownership, current activity, useful relationships, well-defined fields, and visible history. AI suggestions should point back to this structured context.