Support
Customers open support requests (tickets) in the portal. Your team answers them in the Helpdesk of the back office. Staff with any staff role can use the helpdesk: owner, admin, billing and support.
Email notifications#
Set a Support email under Platform settings. See Branding and access. Stacklane sends a short email to this address when:
- a customer opens a new request;
- a customer replies to a request.
The email has the subject [#<ticket number>] <subject> and contains the name of the customer, the category, the priority and a link to the request in the helpdesk.
Without a support email, Stacklane sends no notifications to your team.
The customer who opened the request gets an email when a staff member replies. Internal notes do not send an email.
Tickets#
A ticket has a subject, a category, a priority, a status and a list of messages.
Categories#
general, technical, billing, sales and abuse. The customer chooses the category. The default is general.
Priorities#
low, normal, high and urgent. The customer chooses a priority when opening the request. The default is normal. Staff can change it.
Statuses#
| Status | Customer sees | Meaning |
|---|---|---|
open | Waiting for support | The customer wrote last. Your team should reply. |
answered | Answered | Your team replied. The ticket waits for the customer. |
closed | Closed | The request is done. |
Stacklane changes the status by itself:
- a new ticket is
open; - a staff reply sets it to
answered; - a customer reply sets it to
open, also when the ticket was closed; - an internal note does not change the status.
Customers can close their own requests. Staff can set any status.
The ticket queue#
Open Helpdesk in the Support group of the back office. The queue shows the requests of all organizations, with the name of the organization.
Use the status filter to choose a view:
| View | Shows |
|---|---|
| Waiting for us | Tickets with the status open. This is the default view. |
| Open requests | All tickets that are not closed. |
| Answered | Tickets with the status answered. |
| Closed | Tickets with the status closed. |
| All requests | All tickets. |
Turn on Assigned to me to see only the tickets assigned to you.
The queue is sorted with open tickets first, then answered, then closed. Inside each group, the most recently updated tickets come first.
Answer a request#
- Click a ticket in the queue.
- Read the messages. Internal notes are marked and are only visible to staff.
- Type your reply in the text field.
- Click Send.
A message can be up to 20,000 characters.
Internal notes#
To write a note for your team only:
- Turn on Internal note, not visible to the customer.
- Type the note.
- Click Add note.
The customer never sees internal notes, and the status of the ticket does not change.
Properties#
In the Properties card of the ticket you can change:
- Status:
open,answeredorclosed; - Priority:
low,normal,highorurgent; - Assignee: any active user with a staff role, or Unassigned.
Click Save to apply the changes.
Audit events#
Stacklane writes these audit events:
| Event | When |
|---|---|
support.tickets.create | A customer opens a ticket. |
support.tickets.close | A customer closes a ticket. |
admin.support.reply | A staff member replies. |
admin.support.note | A staff member adds an internal note. |
admin.support.update | A staff member changes the status, priority or assignee. |
Limits#
An organization can open at most 20 new requests per hour. Above that, the customer gets the error throttled.
API endpoints#
| Method | Path | Description |
|---|---|---|
GET | /api/admin/support/tickets | The queue. Query: status (active, open, answered, closed), mine=true, limit, offset. |
GET | /api/admin/support/tickets/{id} | The ticket with all messages, internal notes, the organization name and the list of staff members who can be assigned. |
PUT | /api/admin/support/tickets/{id} | Change the properties. Body: {"status": "answered", "priority": "high", "assigned_to": 12}. Use null for no assignee. |
POST | /api/admin/support/tickets/{id}/replies | Reply. Body: {"body": "...", "internal": false}. |
For the customer endpoints, see API.