Kernlift

Support tickets

Take support requests from signed-in customers, triage them against an SLA and reply from the admin console.

A customer opens a ticket from /app/tickets. The ticket appears in /admin/support with a status, a priority and an SLA flag, and every reply is written to the same conversation. No third-party helpdesk is needed. Tickets, conversations and messages are rows in your own database.

Before you begin

  • An account that can reach the console, with the support.read permission to read tickets and support.write to reply or reassign. See Roles and permissions.
  • Email is optional. Tickets work without it. Connect a provider from Send transactional email if you want the customer notified off-site.

Set it up

Give an operator the permissions

Open /admin/roles, pick the role your support staff hold and add support.read and support.write. A role with only support.read sees the queue and the conversation but cannot reply or reassign, which suits an analyst.

Open a ticket as a customer

Sign in as an ordinary account, go to /app/tickets and submit one. The server takes the requester's e-mail from the session, not from the form, so a customer cannot submit a ticket under another address.

A new ticket arrives as triage, priority normal, SLA within_sla, assigned to support.

Work the queue

/admin/support lists every ticket with its requester, priority, SLA state and assignee. Open one to read the conversation, reply, and set status, priority, assignee and SLA state together.

A reply from an operator moves the ticket to waiting. A reply from the customer moves it back to triage. Closing a ticket also marks its conversation resolved, and /app/tickets/closed lists conversations with that status.

Customer data isolation

The server reads the customer's identity from the session, not from a form field. Before every reply, the server reloads the ticket using both its ID and the requester's email, so another customer's ticket is not returned. Ticket status changes are covered in the steps above.

Conversations, tickets and ticket messages are written in one transaction. Admin changes also create audit entries. See Audit log.

Verify

  1. Open a ticket from /app/tickets. It appears in /admin/support with status triage.
  2. Reply as an operator. The customer's view shows the reply and the ticket reads waiting.
  3. Sign in as a different customer and open the first customer's ticket id directly. The page does not show the conversation.
  4. Close the ticket. It moves to /app/tickets/closed for the customer.

Reference

Next steps