Ticket queue
A CRM helpdesk: every request in one queue, on the customer's record.
Email, your help portal and the form on your site land in one queue. Each ticket gets an owner, a priority and a clock, on the customer's record.
StripeTicket queue in practice.
Every request in one list, with an owner, a priority and a status to sort by.
One shared queue
Email to your support address, requests from the portal, and the form on your own site all land in the same list.
Assigned to an owner
Pick an agent from the ticket itself, or let a rule set the owner as the request arrives, from its group or its tags.
Priority and status, at a glance
Flag a ticket urgent, set it to open, pending, or solved, and filter the queue down to whatever you need to work on next.
A CRM and ticketing system on one record.
A request does not sit alone in a help desk.
The requester is a contact
With their open deals and open tickets on the record.
SpotifyBilling question
The company's open invoices sit on the same record.
Reply on the ticket
It goes out by email and the answer lands on the same ticket.
More in Support & Service.
Each one is its own page, on the same records.
Ticket queue, on your own data.
Bring a spreadsheet or an export to a demo and see it there.
Questions, answered
Three places, all into the same queue: email forwarded to the address Spodus gives your workspace, the customer portal, and the request form you embed on your own site behind a help button.
Yes. Filter by owner, priority or status, save the view, and each agent works from the list that fits how they triage. Each queue can also be sorted by the SLA that runs out soonest.
No. They can email your support address or use the portal, and neither gives them a Spodus account, so there is no seat to pay for.
Both, in one product. The ticket is a record on the same customer as the deal and the invoice, so the agent answering sees what sales sold and what billing sent. There is no live chat and no phone line: requests come by email, the portal and the web form.