HomeFeaturesSupport and tickets
Support and tickets

Support in the same panel you already work in.

You send a ticket from the panel, with a single form. The system attaches the view address, browser, role and app version on its own — everything that an email report would take three messages to pin down.

  • Form in the panel
  • Automatic context
  • Statuses and priorities
  • Case history

A ticket that needs no follow-up questions

The longest part of handling a ticket is usually working out what actually happened: on which screen, in which browser, with which permissions. The system already knows this and attaches it itself the moment the form is sent.

The person reporting describes only what they saw. The rest is already in the ticket.

View addressThe screen the ticket was sent from
BrowserFull user-agent string, including the version
Window sizeTells a phone problem apart from a desktop one
RoleThe permissions of the person reporting
PlanThe company's subscription
App versionThe release on which the problem occurred

You can see whose court the case is in

Five statuses instead of a single “in progress”. The most important is Waiting for you — it says plainly that the case is on hold because we need an answer from your side.

New

Ticket received, waiting for the team to review it.

In progress

Someone is on it. The case is being worked on.

Waiting for you

We need an answer or more detail — the ball is in your court.

Resolved

Case closed. The history stays available.

Rejected

Ticket closed without a change — always with a reason.

The team sets the priority, not the reporter

Four levels — low, normal, high, critical — set by the person who takes the ticket, after reading it. If the reporter chose the priority, everything would be critical and the levels would stop meaning anything.

Response time depends on your plan

A guaranteed response time is part of the subscription — from standard on the Start plan to round-the-clock on Enterprise. You'll find the full breakdown, along with the other differences between plans, on the pricing page.

Compare plans
Why we do it this way

A ticket sent by email stops existing.
It gets lost in an inbox nobody is watching.

The message goes to one person, they reply from their own address, the thread splits, and two weeks later nobody knows whether the case was dealt with. A ticket in the system has a number, a status and one place where the conversation happens — visible to the whole company, not just whoever happened to write.

Everything in-panel support gives you

Raise a ticket without leaving the system

The form is in the panel, under Help. No need to look up an email address, create an account in a ticketing system or explain who you are.

Technical context attached automatically

View address, browser, window size, role, plan and app version are added to the ticket automatically. Nobody has to screenshot the address bar.

Categories that match the documentation

The category list mirrors the documentation sections — customers, quotes, contracts, billing, security. A ticket lands in the right area straight away.

Five statuses, one view

New, In progress, Waiting for you, Resolved, Rejected. You can see whether the case is waiting on us or on you — no chasing for updates.

Conversation on the ticket

Comments are saved on the case, in order. All the correspondence is in one place, not scattered across several people's inboxes.

Attachments

Add a screenshot or a file to the ticket. For display bugs it is usually the quickest way to understand the problem.

Replies in your in-app inbox

Notifications arrive where you work. They don't get lost in spam or land in the inbox of someone who happens to be on holiday.

Cases from outside the panel get a number too

A ticket sent by email is registered on your behalf — with a note of who took it. No case exists only in someone's memory.

The case history stays

Closed tickets don't disappear. When a problem comes back six months later, you can see what was agreed then and why.

Documentation first

Most answers are already there.

The ticket form suggests articles from the section the case is about. Some questions get solved before a ticket is even created.

Open the documentation
Before you buy

Sales and onboarding questions.

Tickets in the panel are for customers. If you are still considering the system, write to us through the contact form.

Contact form