Answer support requests
from one place.

See every customer request in a single list. The portal, email, live chat and the requests your own team opens all queue up together, and each row says where it came from. No request is forgotten on some other screen.

Every request opens with a six-character code. The code is not sequential, so nobody outside can guess your total request count; the customer uses the same code when searching. Your workload cannot be read off the code.

You get a ready-made support page for your customers. They open a request there, then follow its status from the same page with the code and their email. The customer follows their own request themselves.

Mark a connected email account as a support inbox. Every customer mail that arrives at that address becomes a request; a continuation of the same exchange does not open a new one, it is added to the existing request. The customer keeps writing to the address they know.

If a visitor asks for an agent in chat and nobody answers, the conversation becomes a request. The chat transcript becomes the first message of the request and the two records point at each other, so the trail is not lost. The customer does not have to explain it all over again.

Paste the code from the settings onto your site. A support button appears at the bottom right and the visitor leaves a request without leaving the site. The visitor leaves the request without leaving the site.

For a customer who calls on the phone, you open the request yourself. The record joins the same queue, and its source shows that your team started it. Work that arrives by phone runs through the same queue.

Assign a request to one person. The "My requests" filter separates out your own work, while the inbox shows the ones still without an owner. Two people never answer the same request.

A request opens as new, then moves through in progress, waiting for the customer, resolved and closed. If a customer writes again on a closed request, it reopens. The customer's second question is not lost.

On every request, when the first reply, the resolution and the closing happened is recorded. It sits in the list as a column, so you see which requests are waiting. You do not hear about a late request from the customer.

Three ready categories arrive when you turn the module on. You add your own; if you delete a category the requests are left without one rather than being deleted. The classification is built around your work.

If the email that opened the request matches your customer record, the request is linked to that card. The support history becomes part of the customer's timeline. Who asked what before is plain on the card.

The customer attaches a screenshot or a document to the request. Attachments sit under the request, so you do not have to go looking for them. The document stays inside the request.

When a new request opens and when a customer replies, the team gets a notification inside the app. You do not have to refresh the list by hand. You never see a new request late.

When the queue grows, search by code, by subject or by customer name. You can narrow it down by category too. You find what you are after from a single box.

Seeing, replying, assigning, resolving, deleting and managing settings are separate permissions. A new colleague can write replies but cannot delete a request. Growing the team brings no risk of losing records.