Every request, tracked to the person who closes it.
A ticket queue for support and internal requests, with an owner, a status and a history on each one. Comsky Tickets is in design. Comsky Chat already runs customer conversations — WhatsApp, groups and website chat — and raises tickets from them today.
In design · Nothing to sign into yet · No date · Comsky Chat already raises tickets from customer conversations today
Requests that currently arrive as a tap on the shoulder.
Inside most companies, a request is a WhatsApp message to whoever is nearest. It gets done or it does not, and nobody can say which without asking. This is being designed for that: a queue, an owner, and a record of what happened.
One queue, not six inboxes
A place a request goes that is not a person. Everything in one list is the difference between a backlog you can see and a backlog you can only feel.
An owner on every item
A ticket that belongs to everybody belongs to nobody. The name on it is what makes the queue move.
What was asked, and what was done
The history on the ticket rather than in somebody’s chat history — so the second time it happens, there is something to read.
If the requests come from your customers, the product you want is already live.
Comsky Chat is running today with customers on it. It puts several agents behind one WhatsApp number, keeps WhatsApp groups and website chat in the same inbox, and raises customer, internal and tracker tickets off those conversations with assignment and response targets. If that is your problem, there is no reason to be on a waiting list.
Comsky Tickets is being designed for the requests that are not customer conversations — internal IT, facilities, HR and operations — which arrive by a different route and are worked by different people.
Comsky Tickets is in design. This page is the brief, not the product.
There is nothing to sign into, no trial, no price and no date. We would rather this page said so in its own words than leave you to work it out from the absence of a Sign up button. It is being designed as a queue for support and internal requests, with an owner, a status and a history on each ticket — and it is aimed at the requests that are not customer conversations, because Comsky Chat already handles those today.
What is settled
It is being designed as a queue for support and internal requests, with an owner, a status and a history on each ticket — and it is aimed at the requests that are not customer conversations, because Comsky Chat already handles those today.
Anything beyond that — on this page or from anyone who works here — is a design intention and should be read as one.
What is not settled
- Where tickets come in from — email, a portal, a form, all three
- Response targets, escalation and working hours
- Categories, approvals and an asset or knowledge base
- Whether it shares a queue with Comsky Chat or sits beside it
- Reporting, and what a sensible first report would be
- Pricing, and any date at all
The interface shown on this page is a drawing of the design, not a screenshot of a running product. When there is a build to photograph, the drawing comes down.
Tell us roughly how many requests you get.
Five a week and five hundred a week are different products. Knowing which end you are at is what makes this worth building.
Honest answers, including the unsatisfying ones.
Can I use Comsky Tickets today?
No. It is in design — no build, no beta, nothing to sign into.
I need ticketing for customer support. What should I do?
Use Comsky Chat, which is live. It runs WhatsApp, WhatsApp groups and website chat in one shared inbox and raises customer, internal and tracker tickets from those conversations, with assignment and response targets. Do not wait for this page.
Then what is this for?
The requests that are not customer conversations: internal IT, facilities, HR and operations. They arrive by a different route, from your own colleagues, and are worked by different people.
Will it share a queue with Comsky Chat?
Not decided. It is the main open question about the product, and we would rather leave it open on this page than answer it with an architecture diagram we have not built.
Will it have SLAs and escalation?
Unspecified here. Comsky Chat has response targets and SLA sorting today, and that is a thing you can go and use rather than wait for.
When will it ship, and what will it cost?
No date and no price. The early-access list hears first on both.
Start with Comsky Tickets.
Grow into the ecosystem.
One account opens every Comsky product — and one invoice covers them, however many you run.