The support desk
How portals, the inbox, tickets, SLAs and help articles fit together, who works them, and which plan each part needs.
Team plan and aboveFor owners, admins and support agents
The support desk keeps your customers’ questions next to the work that answers them. A project gets its own support portal, customers raise tickets there, and every ticket lands in one inbox with a named person to triage it. From a ticket you can reply, keep notes the customer never sees, and make a task in the project it’s about.
How it fits together#
- A portal for a project. Turn on a support portal in a project’s settings and it gets its own address, such as
support.projik.com/bms/, with your name, logo and colour. The project is usually the product your customers use. See Set up a support portal. - Customers. You invite the people you support, or open the portal so anyone can sign up with their email address. Customers aren’t workspace members and don’t count as people on your plan. See Customers and What your customers see.
- One inbox. Tickets from every portal arrive in Support › Inbox. Each new ticket is assigned to its project’s triage owner, who is told about it straight away. See The inbox and tickets.
- Replies and internal notes. Everything you write on a ticket starts as an internal note. Replying to the customer, and emailing them that reply, are choices you make each time.
- Tasks. A ticket that needs work becomes a task in a project, linked both ways, with no customer details copied across. See Turn a ticket into a task.
- SLAs. First-response and resolution targets by priority, counted in business hours, with a warning before one is missed. See SLAs.
- Help articles. The knowledge base drafts articles from your own documents. Once someone on your team publishes one, customers read it in the portal. See Help articles.
Who works the support desk#
| Who | What they can do |
|---|---|
| Owners and admins | See every ticket. Use the inbox, Customers and the SLA report. Set up portals and SLA targets. |
| Support agents | See every ticket. Use the inbox, Customers and the SLA report, invite and block customers, assign and move tickets. They can read a project’s portal settings but not change them. |
| Other members | See only the tickets assigned to them, on My Work under Tickets assigned to me. |
| Customers | See only the tickets they raised themselves, in the portal. |
A support agent is a member with Customer support ticked. An owner or admin sets it by opening the person in People & AI. Owners and admins already see every ticket, so the box is ticked for them. See People and roles.
An assignee who isn’t on the support desk#
You can assign a ticket to any active member, for example the developer who knows the area. While it’s theirs they can read the whole thread, add notes, reply to the customer, change the status, priority and category, and create or link tasks.
They don’t get the Requester card with the customer’s email and company, and they can’t reassign the ticket or move it to another project. When the ticket is assigned to someone else, they lose access to it.
What each part needs#
| Part | Plan |
|---|---|
| A support portal, with the inbox, customers and ticket tasks | Team includes one portal. Business has no limit. |
| A shared support address for a project | Business |
| A portal on your own domain | Team |
| SLAs and SLA warnings | Business |
| Knowledge base sources and Ask | Team |
| Published help articles in the portal | Business |
Free has no support portals. Enterprise includes everything in Business.
A new workspace’s 30-day trial runs on Business, so you can try all of it. While you use a Business-only part during the trial, owners and admins see a banner saying so.
Changing plan never takes a portal away from your customers. A portal that’s on stays on, and published help articles stay readable. What stops is adding: another portal, a new SLA policy, a newly published article. See Plans and billing.