The inbox and tickets
Find the tickets waiting on your team, then assign, reply, keep internal notes and close them, and see who gets emailed.
Team plan and aboveFor owners, admins and support agents
Tickets from every support portal arrive in one place: Support › Inbox. Owners, admins and support agents work them there. Anyone else reaches the tickets assigned to them from My Work, under Tickets assigned to me.
The inbox#
The inbox opens on what needs your team: tickets Waiting on us, longest waiting first. The line under the title counts those and the unassigned ones.
- Projects: tick as many projects as you like, or All projects for everything.
- Unassigned, Mine, All: who the ticket is assigned to.
- Search: a ticket key such as
SUP-0042finds that ticket. Anything else searches subjects and original requests. - Status chips: turn on as many as you like. With none on, you see everything except closed tickets.
| Chip | Shows |
|---|---|
| Waiting on us | New and open tickets where the customer wrote last. |
| Waiting on customer | Tickets with that status, and new or open tickets you’ve replied to since the customer last wrote. |
| On hold, Resolved, Closed | Tickets with that status. |
Each row shows the key, project, subject, requester, assignee and status, with URGENT or HIGH beside the status for those priorities. Waiting is how long since the customer last wrote without a public reply from you. SLA is the next deadline. See SLAs.
Your filters are kept in the page’s address, so going back from a ticket returns you to the same list.
Statuses#
| Status | Use it when | The customer sees |
|---|---|---|
| New | The ticket has arrived and nobody has moved it yet. | Received |
| Open | Someone is working on it. | Open |
| On hold | It’s parked on your side, for example until a fix ships. | On hold |
| Waiting on customer | You need something from them before you can go on. | Waiting on you |
| Resolved | You believe it’s sorted. | Resolved |
| Closed | It’s finished for good. | Closed |
Change it with Status on the ticket. The list offers only the moves allowed from where the ticket is.
- Replying doesn’t change the status. A new ticket you’ve answered stays New until you move it.
- When a customer replies on a ticket that’s Waiting on customer or Resolved, it goes back to Open. You can reopen a resolved ticket yourself by setting it to Open.
- Closed is final: it can’t be moved again. Nobody can add a public reply, and the customer is told to open a new ticket and mention the old one. Your team can still add internal notes.
- Customers can mark their own ticket resolved, and close it once it’s resolved.
Work a ticket#
Priority and category#
Priority is Low, Normal, High or Urgent. The customer picks it when they raise the ticket, and you can change it. It decides which SLA targets apply. Category is free text, with suggestions.
Assign and move#
Owners, admins and support agents can do both.
- Assignee: choose any active member, or Unassign. The new assignee is told, unless they took it themselves. A member who isn’t on the support desk can open a ticket only while it’s assigned to them.
- Move: put the ticket under another project, even one with no portal. The customer keeps their ticket.
Both leave an internal note saying who did it.
Reply to the customer#
The reply box starts as an Internal note every time, so nothing reaches a customer by accident.
- Choose Reply to customer. The box says who will see what you write.
- Write the reply, and attach files if you need to.
- To send it by email as well, tick Email the customer. It’s never ticked for you.
- Choose Post reply, or Post & email.
A reply you didn’t email shows in the portal only. To email it later, choose Email to customer on that message. You see the email exactly as it will be sent, then choose Send email. If sending fails, the message offers Retry email. Once a message has been emailed it’s locked.
Internal notes#
Internal notes are for your team. They never appear in the portal and can’t be emailed. The notes Projik adds, such as “Assigned to” and “Moved from”, are internal too.
To show a note to the customer after all, choose Share with customer on it. It becomes a public reply, along with its files. Sharing doesn’t email it: that’s a separate step.
Attachments#
Use Attach, drop files on the reply box, or paste a screenshot. A file is as visible as the message it’s attached to, so files on an internal note stay internal.
Images can be up to 10 MB and other files up to 25 MB, ten at a time: images, PDFs, Word, Excel and PowerPoint files, zip, video and text files.
What the customer is emailed#
| When | |
|---|---|
| “We’ve received your ticket” | A ticket is raised, by them or for them. |
| “Waiting on you” | Your team sets Waiting on customer. |
| “Resolved” | Your team sets Resolved. |
| A reply | Only when someone ticks Email the customer or uses Email to customer. |
The first three are status emails. They contain no staff-written text, and go out only while the project’s Automatic status emails is on and the customer hasn’t turned off updates for that ticket. The Emails row on the ticket shows which. A reply you choose to email is sent either way.
Every email links to the ticket in the portal, and customers reply there. Replying to the email doesn’t reach your team.
Nothing is emailed to a blocked customer, or to one who has no portal where they could read the ticket. The preview tells you when that’s the case.
What your team is told#
- The triage owner hears about each new ticket for their project.
- The assignee hears when a ticket is assigned to them, when the customer replies, when a linked task is done, and before an SLA deadline is missed.
- A project’s support email address, if it has one, gets an email about each new ticket.
People are told by email, in the bell and on My Work. None of these carries the customer’s message, only the ticket’s key, subject and project and the customer’s name. To turn them off for yourself, see Notifications.
A customer’s reply on an unassigned ticket notifies nobody, so keep an eye on Unassigned.
Raise a ticket for a customer#
When a customer phones or emails instead, choose New ticket in the inbox.
- Find the Customer. They must already be on the Customers page and not blocked.
- Choose the Project and Priority.
- Fill in Subject and What they need, and a Category if you like.
- Choose Open ticket.
The ticket is assigned to the project’s triage owner. The customer sees it in the portal with their other tickets, and gets “We’ve received your ticket” if status emails are on.
Add a new customer as you go#
When the project’s portal is Open, the customer doesn’t have to be on the Customers page first. Under the customer list, choose + Add a new customer and enter their Email, First name and Last name, then fill in the rest and choose Open ticket.
No invitation is sent. The customer is added to that project’s portal, shows on the Customers page as Invited, and the next time they sign in to the portal with that address they see this ticket and any others you’ve opened for them. If the address already belongs to one of your customers, the ticket goes to them and the project is added to their portals.
For a portal set to Invite only, invite the customer from the Customers page first. An address that belongs to an active member of your own workspace can’t be added as a customer; a member of another workspace can.