Keep customer requests in a queue, not in a chat app

“Can you take a look?” stays ownerless. A request record wants a subject, priority, and assignee. Ontra’s queue requires them; a closed ticket is archived, not deleted. A starred Slack message is nobody’s job three days later. The client says “I wrote yesterday”; if the timestamp is not on the queue, the argument starts. The queue timestamp ends the claim.

Response time for high-priority tickets should sit on the report. SLA is not a separate product; it is writing the queue’s age onto the report. A separate Zendesk is only needed when volume truly becomes an external call center. For ten people, three clients, and support buried in Slack, a second tool splits the record again. The same access model protects the queue. A client lead can be a viewer; they do not see the internal spec.

A repeating request becomes a feature. Do not keep the queue and the roadmap in separate worlds. The sentence “this is the third time” is written on the card, then a feature opens, then it enters a sprint. Support should not shout at product through Slack; the record already shares the workspace. Forms (`forms.read` / `forms.create`) standardize repeating intake. Free text leaves a missing field every time.

The request queue also uses views: arrived today, high priority, waiting on approval. Ten shortcuts are clutter again. Three are enough. In the field a request sometimes carries a location; the map shows the same record. Photos land on the card. A separate “service app” is not born.

An external call center, a phone queue, a public SLA contract, thousands of tickets — those warrant a separate support product. Ten people and three clients do not. Multiplying tools is not professionalism; it is splitting the record. Keep the threshold explicit: if volume occupies one person full-time, talk. Until then the Ontra queue is enough.

“Can you take a look?” is ownerless. The queue wants subject, priority, assignee. The timestamp ends “I wrote yesterday.” A closed ticket is archived, not deleted. A form standardizes repeating intake; free text leaves a field every time. High-priority response time sits on the report. SLA is not a separate product; it is writing the queue’s age.

A third-time ask is written on the card, a feature opens, it enters a sprint. Support should not shout at product through Slack; the record shares the workspace. The same access model protects the queue. A client lead is a viewer and does not see the internal spec. A field request may carry a location; the map shows the same record. Photos land on the card.

A separate Zendesk exists for thousands of tickets, a phone queue, a public SLA. It does not exist for ten people and three clients. Multiplying tools is not professionalism; it is splitting the record. Threshold: if volume occupies one person full-time, talk. Until then the Ontra queue is enough. Three views are enough: arrived today, high priority, waiting on a reply.

Can you take a look is ownerless. The queue wants subject, priority, assignee. The timestamp ends I wrote yesterday. Closed is archived. A form standardizes fields. High-priority response time sits on the report. SLA is writing queue age. A third-time ask becomes a feature and enters a sprint. Support should not shout through Slack. The same access model protects. The client is a viewer and does not see the internal spec.

A field request carries location. The map shows the same record. Photos land on the card. Three views are enough: today, high priority, waiting on a reply. Ten shortcuts are clutter. A separate Zendesk is for thousands of tickets. For ten people and three clients it splits the record. Threshold: volume that occupies one person full-time. Until then the Ontra queue is enough.

Do not keep the queue and the roadmap in separate worlds. A repeating fault is product work. Form plus queue plus feature line sit in the same workspace. A separate field app, support, and billing Excel split it three ways.

In week one pour Slack stars into the queue. An ownerless message becomes a card. Week two require the form. Week three turn three repeating asks into a feature. Week four look at the SLA number. This order comes before a second support product.

Response time for high-priority tickets should sit on the report. “I wrote yesterday” is settled by the queue timestamp. A separate Zendesk is only needed when volume truly becomes an external call center.