Overview

The Customer Support Tickets area manages support tickets. Two distinct sub-queues handle different audiences: one for tickets submitted by end users through the member app, and a separate internal backlog for system and matchmaker (SME) tickets raised by your own team.

Member-app tickets

End users submit these through the app. Each ticket links to the submitting user's profile so agents have full context while helping them.

Internal backlog

System and SME tickets created by backoffice or bo-mobile users. The backlog view groups tickets by app version for development tracking. Requires SManager role to see internal columns.

SLA tracking

Each topic can have a first-response and completion SLA configured in Customer Support Settings. A traffic-light indicator shows hours remaining on the list and detail views.

Three ticket queues

QueueWho submitsReached at
Customer Support TicketsEnd users via member appSupport → Customer Support
Matchmakers via bo-mobile appSupport → SME Tickets
(backlog)Backoffice staff (Admin Panel)Support → System Tickets

Ticket list columns

ColumnMeaningWhen shown
IDUnique ticket numberAlways
BrandBrand logo of the ticket's brandMaster-admin view only (brand ID 100)
CreatedDate the ticket was submittedAlways
UpdateDate or time of the last activityAlways
PriorityShowStopper → Feedback (see Priorities below)System and SME queues; hidden on member-app queue
PlatformSub-topic / platform categorySystem and SME queues; hidden on member-app queue
CategoryTopic category for the ticketAlways
TitleTicket subject or first line of contentAlways
App VersionColored badge showing app version this issue targetsSystem / backlog queue only
ReporterWho submitted the ticket; links to end-user profile for member-app ticketsAlways
Hours remaining before SLA deadline; traffic-light color (see SLA section)System and SME queues when a topic SLA is configured
Assigned ToSupport agents currently handling the ticketAlways
StatusCurrent ticket state (see Ticket statuses)Always
InternalWhether the ticket is flagged as internal (Yes / No)SManager role only
BillableWhether development hours on this ticket count toward billing totalsSManager role only

Filters

  • Search — search by user name, email, or keyword
  • Assignee — show only tickets assigned to one or more specific agents (multi-select)
  • Category — narrow to a specific topic category
  • Status — filter to one or more statuses (multi-select)
  • My Tickets — when switched on (default), shows only tickets assigned to you

The stats bar above the list (visible to admins on the member-app queue) shows the current Tickets count, On-Time Rate, Tickets Per Assignee, and SLA Expired count. Clicking a stat filters the table to that group.

From End User profile (CS Tickets chips)

On View End User → CS Tickets, agents with Customer Support access see summary chips — not the full ticket list:

  • Open — count of this member’s tickets in status New (1) or Open (2).
  • One chip per topic — total tickets per topic name from your brand’s ticket-topic general codes (includes closed history, not only open).

verified — Workflow when a chip is non-zero:

  1. Copy the member’s Profile ID from the End User header (UUID).
  2. Open this page (Support → Customer Support, member-app queue).
  3. Paste the UUID into Search — the backend matches profileId exactly. Name, email, #ticketId, and title/content keyword search also work.
  4. Optionally apply the Category filter that matches the elevated chip on the profile.
  5. Open the ticket row → reply on Single's Conversation or change status.

The Reporter column links member-app tickets back to the End User profile. Delivery of assignment/reply emails may show on the profile under Profile comm logs.

Working with tickets

Click any row to open the ticket detail view. The header shows the ticket number, creation date, assigned agents, last update, topic, sub-topic, SLA remaining, priority, and (for backlog tickets) an app-version badge or a Backlog indicator.

Ticket detail sections

SectionWhat it containsShown when
Reporter Reportee Avatar and profile link for the submitter; a second card for the reportee (the person the ticket is about) when applicable Always
Package details Membership package information for the end user Only when brand has the premium feature enabled
Ticket Content Full ticket text; Translate button (SManager) sends the content for AI translation Always
Single's Conversation Conversation thread visible to the end user; agents type replies here to communicate with the member Member-app tickets only
Inner Conversation Internal notes thread — visible to support staff only, never to end users Always
Development conversation Development-team thread for backlog tickets; split layout alongside Inner Conversation SManager role on Admin Panel (backlog) tickets
Ticket Management Internal ticket fields: Topic, Sub-Topic, Dev Hours (0.5–12 h steps), Dev Priority (P0–P5), App Version or Target Version, Developer Instructions, Approved By, Billable toggle; also Fork, Mark Duplicate, Make Internal/Public, Change Request, Send to AI (Cursor agent) actions System tickets with a valid profile, non-guest only; all fields require SManager role to edit
Reporter Device Device/OS information from the ticket's user-agent string When present in the ticket data

Actions

ActionWhat it doesWho can use it
Opens the reassign dialog to add or change the assigned agentsAll agents with view access
Re assign backRemoves you from the assignees list and navigates back to the queueOnly shown when you are one of the assignees
Change statusUpdates the ticket status (see Ticket statuses below)Edit permission required; BManager required for status change
Delete TicketPermanently deletes the ticket after confirmationDelete permission only
Reply (end-user thread)Sends a message to the end user on their member-app conversationEdit permission on member-app tickets
Add internal noteAppends a note to the inner-conversation log visible to staff onlyEdit permission
TranslateAI-translates the ticket content in placeSManager role
Draft reply with AIGenerates a suggested reply for the end-user thread or internal thread using AISManager role
Send to AI (Cursor agent)Launches a Cursor Cloud Agent for the ticket using the Developer Instructions field; link appears once agent is runningSManager role on system tickets

Ticket statuses

StatusMeaning
NewFreshly submitted; no agent has responded yet. SLA first-response clock is running.
OpenA first response has been sent; the issue is being worked. SLA completion clock is running.
On HoldWaiting for information from the user or a third party; SLA clock may be paused (per your brand's configuration).
SolvedThe issue is resolved from the agent's side. The ticket re-opens automatically when the user replies.
ClosedTicket is permanently closed. New replies do not re-open it. Further conversation requires opening a new ticket.
CanceledTicket was withdrawn or determined invalid before resolution.
Has To ApprovePending approval from the client (e.g. approving a resolution or a quoted scope for backlog work) before further action.

Priorities

Applies to system and SME tickets. Not shown on member-app tickets.

PriorityMeaning
ShowStopperCritical: the app or a key workflow is completely broken. Highlighted in red on the list. Requires immediate attention.
HighSignificant issue affecting many users or key functionality. Also highlighted in red.
DefaultStandard ticket priority; most tickets fall here.
LowMinor issue or nice-to-have improvement; can be addressed in regular cycles.
FeedbackUser or team feedback, feature request, or observation — not an active defect.

Backlog (system) tickets also have a separate Development Priority (P0–P5) for engineering sprint planning. P0 is the highest engineering urgency.

SLA indicator

Each topic can have two SLA windows configured in Customer Support Settings:

  • SLA First (hours) — how long the team has to send a first response after the ticket is created (clock runs while status is New).
  • SLA Completion (hours) — how long the team has to fully resolve the ticket (clock runs while status is Open).

The column on the list shows a colored bar reflecting remaining hours as a proportion of the total window. The admin stats bar shows the count of tickets where the deadline has already passed (SLA Expired).

SLA deadlines use business hours as configured in brand settings. Public holidays and out-of-hours time do not count toward the SLA window.

See also: Customer Support Settings — configure topic SLA windows and default assignees.