Give every request a clear owner.
Assign tickets to people or agent groups. Set priorities, use saved views and track the status of each request without stitching together a spreadsheet.
Assignment · Saved views · Priority · StatusEvery request has a customer, a history and a next step. Bring them together so your team can spend its attention on the answer.
Maya Chen · Northstar Studio
Roles are the right place to start. I have attached the setup guide.
Alex · Support teamAssign tickets to people or agent groups. Set priorities, use saved views and track the status of each request without stitching together a spreadsheet.
Assignment · Saved views · Priority · StatusContacts and companies put the person behind the message in context. See recent requests, company details and VIP markers while your team works through the conversation.
Contacts · Companies · Customer historyAdd internal notes, attach files and bring colleagues into the work with watchers. SLA policies and escalation rules give the team a shared view of what needs attention.
Internal notes · Watchers · Attachments · SLAsBuild ticket forms with custom fields and conditional sections. Keep extra records such as devices or contracts in custom objects, so your support process can reflect the service you actually provide.
Custom fields · Conditional forms · Custom objectsConnect your inbound email configuration. Incoming messages become tickets, with the sender linked to a contact. Replies can remain attached to the same conversation.
Internal notes are for your team. The ticket composer distinguishes them from customer-facing replies so that your handoff context stays inside the workspace.
Yes. Agent groups, assignments, roles and saved ticket views help organise the work. Workspace permissions determine what each member can access.
Bring the rest of your support work along.