Repairs and warranty
Each category gets its own fields — a serial number, say, marked required to close. Until it’s filled in, the ticket can’t move to a done status.
Help desk ticketing
Help desk ticketing where every case has a number, an owner and a deadline.
A repair, a warranty claim or a billing dispute isn’t one email — it’s a case that runs for days. One click turns it into a ticket, with a number, an owner and an SLA clock. Your customer keeps writing where they always have, and sees where their case stands on a single link.
4.7 / 5 from real users14 days of full access3,000 AI credits on usNo contract — leave anytime
TicketsDue today: 2
AllMineOverdueUrgent
SV-1044Heat pump won’t start42 min
Emily CarterIn progressShared issue
SV-1045E3 error on the displayoverdue
Jason MillerNewShared issue
SV-1038Warranty card missingclock paused
Sarah JohnsonWaiting on customer
Shared issue
Inverter batch: startup fault2 tickets · 3 conversationsResolve all
- One click from the conversation and the ticket exists — AI writes the title and the summary
- An SLA clock for first reply and resolution, counted in business hours
- One cause, many customers? Link them to a shared issue and resolve them all at once
- Customers see the status without logging in — and can reply from there
- Kanban or list, snooze, merge, canned replies — all on one tab
In numbers
- to open a ticket: from a conversation, by hand, in AI chat, by the bot, from email
- 5 ways
- needed for your customer to see where their case stands
- 0 logins
- for your own statuses — each with its own customer-facing name
- 12 columns
A case starts in an email. Then it disappears.
A warranty question comes in. Someone replies and asks for a serial number, then the next email arrives. Two days later the customer asks how the repair is going — and nobody knows offhand.
You track who owns what in a spreadsheet. It’s up to date on Tuesday. By Thursday, nobody is updating it.
When one bug hits twenty customers, you answer the same thing in twenty separate threads. Once the fix ships, half of them never hear about it.
From report to resolution
1
It becomes a ticket
Hit “Ticket from this” at the top of the conversation: the AI summary fills in the title and description, and the contact is attached automatically. You can also create one by hand, with one sentence in Gammatica AI chat, or let the bot open it — with your approval.
2
It gets an owner
A number (from #1001, or with your own prefix), a category, a priority, an assignee. Assignment can follow the category or rotate among the teammates you pick.
3
The clock starts
First-reply and resolution targets per priority, in business hours. While you’re waiting on the customer, the clock pauses. The owner is alerted an hour before it runs out.
4
The customer knows where it stands
Turn it on, and they’re notified when their case status changes — on their own channel. One link shows their case; they can reply and upload a photo, and rate the outcome with one click when it’s resolved.
What it’s used for
Three situations you’ll recognize.
An outage or a batch defect
Link every affected ticket and conversation to one shared issue. When the fix is in, resolve them all with one button, and everyone gets the message on their own channel.
Small team, lots of cases
Quick filters (Mine, Unassigned, Overdue, Urgent), saved views, bulk moves with undo — and on the Reports tab, average first-reply time and the share resolved within the deadline.
Why this is different
Tickets instead of a spreadsheet and memory.
The case is the same. The difference is whether anyone knows where it stands.
Where the case stands
Someone remembers, if they’re in today
Status, owner and deadline on the ticket
Deadlines
Nobody measures them
SLA clock in business hours, alert before it runs out
Same bug, many customers
Twenty threads, twenty separate replies
One shared issue, one fix, one message to everyone
“Any update?”
Another email, another search
They check the link and reply from there
Duplicate reports
Two people working the same case
Merge them; the timelines combine
Feedback
You never ask
Three-button satisfaction on resolution
Companies that have already handed the work over
Don’t take our word for it.
4.7 / 5
real user rating
I’ve tried a lot of project management software, but finally here’s one that’s easy to use and meets high expectations.
I’ve been using Gammatica for over a month. We moved off Notion onto this platform quickly and painlessly.
We’ve tried many platforms, but I can finally see all our international campaigns in one place.
A 10/10 solution if you want to see what your team actually does each day.
Viktor and the team did excellent work rolling Gammatica out for us. Recommended.
Finally a calendar I don’t get lost in. I recommend it to everyone.
Anna
You don’t have to learn it. You have someone to ask.
Anna is the assistant built into the system. Not a generic chatbot: she knows Gammatica specifically, across about 300 topics — from credits to permissions to billing. Ask in a sentence and she answers; where it helps she shows you with a small animation and links you straight to the right screen.
- Ask in plain English, get a plain answer
- She doesn’t just describe where it is — she takes you there
- Available at night too, with no ticket to raise
AAnnaLive
What people actually ask her:
How do I link several tickets to one shared issue?
Let me open it for you
What you want to know before you commit.
The inbox is for conversations: who wrote, who replies. A ticket is for the case you follow through to resolution — repair, warranty, billing, complaint. It doesn’t replace the conversation: the customer keeps writing on the same channel (email, chat, Telegram, Slack), and the ticket shows you the status, the deadline and the owner.
No. Ticketing works without a bot: create tickets by hand, from Gammatica AI chat, from an automation, or — if you switch it on — from every new email thread sent to the support address you choose.
Only if you let it. By default it asks for approval: it collects the details first, then drops a card into the thread (Open ticket / Discard). Switch it to “Automatically” and it opens the ticket right away and tells the customer the ticket number — or set it to “Never”.
Only that one case, on a signed link that expires: the ticket number, the customer-facing status and the messages your team wrote to them. Never internal notes, internal column names or the assignee. Internally it can say “Waiting for parts” while they see “We’re on it”.
You set first-reply and resolution targets per category and priority. The defaults include Urgent: 1 hour / 1 business day and Normal: 1 business day / 5 business days. It counts business hours (default Monday–Friday, 9 to 5) and pauses while the ticket is waiting on the customer or snoozed.
There’s no customer portal with a login: customers get one link per case. Merging tickets or linking them to a shared issue notifies no one — the message to everyone affected only goes out when a teammate explicitly sends it. A reply to a resolved ticket doesn’t reopen it automatically: the owner is alerted and reopens it with one click.
Ticketing is part of your plan — no add-on fee. Only the AI work uses AI credits: the summary when a ticket is opened and the reply draft. Without credits, the email subject becomes the ticket title and everything else works the same.
Give every case a number and an owner.
One click from the conversation: a ticket with an SLA clock, a status, a link for the customer — and when many are affected, one shared fix.
P.S. The trial costs you nothing and asks for no card details. If it isn’t for you, you close the tab and we never charge you.