Customer support for hosting: tickets, live chat and a status page in the panel
Clients write from the panel, by email or in live chat, and your staff answer from the panel or straight from Discord. Add a knowledge base in 5 languages, ticket translation, on-call duty with escalation and a public status page on your own domain.
The client's case
a ticket or a chat conversation, with a category and its full history
The client's case
a ticket or a chat conversation, with a category and its full history
- knowledge base languages from day one
- 5
- notification channels
- 6
- of history on the status page
- 90 days
Tickets clients can write and staff can close quickly
The client picks a category, describes the problem and attaches a screenshot or a log. Before they send it, the panel suggests knowledge base articles that match what they are typing, so some questions are answered before they are asked.
A reseller's client writes to the reseller's desk. When the case needs you, the reseller hands it up with a note and the client stays in the same conversation.
Live chat with a queue, and a ticket when nobody can answer
Chat is the fast lane for a client who is watching something fail right now. The conversation waits in a queue, someone takes it and sees the client's services and invoices beside it. Canned replies and opening hours are set in the panel.
- The client's services and invoices
- Canned replies
- Chat opening hours
- A queue with assignment to a person
Waiting in the queueIn conversationClosed
- The client's services and invoices
- Canned replies
- Chat opening hours
- A queue with assignment to a person
The whole conversation moves into the ticket in order, every line signed by whoever wrote it. The chat history keeps a link to the ticket, so the conversation never just vanishes.
Ticket translation and first-line AI, on the operator's own model
A client writes in Czech, staff read and answer in Polish, and the client gets the answer in Czech. The translation runs on a model hosted on your side, so ticket content stays with you.
- A button next to the message
- Staff click "show translation" and read the message in their own language, with the original kept beside it.
- Hundreds of languages
- The local model translates from hundreds of languages, not only the 5 panel languages.
- First-line AI
- You switch it on as an option. The assistant answers the first questions and hands anything it cannot solve to a person.

A knowledge base in 5 languages, ready on day one
You start with 15 articles on 5 shelves, each one in Polish, English, German, Czech and Ukrainian. You write more in the editor, and clients find them with full-text search.
- articles to start with
- 15
- shelves
- 5
- languages for every article
- 5
Written in English only: a reader using Polish gets the English version with a note about which language it is in.
- A missing translation does not hide an article
- An article that only exists in English still turns up in a search in Polish, and the panel tells the reader which language they are getting.
- Reseller articles
- Resellers write their own articles for their clients. A reader only sees the articles of the brand they came in through.
- Three places, one base
- The public help pages, the signed-in panel and the suggestions in the ticket form all use the same articles.
- A new language
- You can add another panel language. Texts you have not translated yet show in English until you do.
Every ticket as a thread on your Discord
A new ticket opens a thread in a channel on your Discord server, and every later message goes into it. A reply typed in Discord comes back to the ticket, so the client gets it in the panel.
- A ticket is never lost
- If the webhook stops working, the client can still send the ticket. The bridge error is saved in its settings, so your screen says plainly that the bridge is down.
- No loops
- A message that came from Discord is never posted back to Discord a second time.
- Roles on your server
- The bot hands out roles: client, former client, active client, service type and node. A client with a node role gets notices about maintenance on their node in Discord.
- A bot under your brand
- The bot runs as your own Discord application: live server status, crash alerts and orders in the support channel.
Announcements that only reach the people they concern
An announcement goes to everyone or only to the owners of selected services. Before publishing, the panel shows how many people it will reach, and the same number comes out in the preview, in the channels and in the mailing.
- Planincluding every copy of the plan a reseller sells under their own name
- Gamethe game the server runs right now
- Nodethe node the service runs on today, not the one it was first placed on
- Service typegame server, VPS, website and the rest
Within one dimension the values are alternatives, across dimensions all of them have to match. Paper servers on one node means the game and the node at once.
- In the panel
- Discord
- Push
- SMS
- Telegram
- Newsletter with consent
- Announcements and the newsletter go out on every channel. Only clients who agreed to it get the newsletter, and email goes out in batches of 200 people.
- Delivery log
- Every send attempt is recorded, failed ones are retried, and a target that keeps failing is switched off with the reason given.
- Client preferences
- Clients pick their own categories and channels, test a channel and confirm the address.
- Asking for a review
- Staff send it with a button to selected clients after a case went well. Nothing goes to everyone automatically.
A rating after every conversation and statistics for every agent
After a closed ticket and after a chat, the client rates the help from 1 to 5. They can change the rating for 7 days, and every case keeps one rating.
- Agent statistics
- Ratings for every agent separately, readable in the admin panel and on the ticket itself.
- Tickets by category
- How many tickets of each category came in over a chosen period, counted straight from the tickets, with no stored totals that could disagree between screens.
- Ratings for resellers
- Resellers see the ratings their clients gave.
Viewing an account as the client: 30 minutes, read-only, recorded
When a client writes that they cannot see something, staff open the panel exactly as the client sees it, without learning their password. The client always gets a notice in the panel, and an email by default.
30 minutes of preview
ends without extension
- Start: who is viewing and whose account
- Every request during the preview
- End: by hand or after 30 minutes
- A separate session with a hard end
- The preview has its own 30-minute session that cannot be extended. An ended preview stops working on the very next click.
- Read-only
- Every change is blocked, and so is reading sensitive data. A new panel screen stays blocked in the preview until someone deliberately allows it.
- Full record
- The audit log records the start, the end and every request: who was viewing and whose account it was.
- Who can do it
- Staff with a separate permission, or a reseller for their own clients. Nobody can view a staff, reseller or administrator account this way.
Moving a service to another account
When a client wants to give a server to someone else, they open a ticket and staff move the service to the chosen account. Clients do not do this themselves.
On-call with escalation: an alert climbs when nobody answers
An alert goes first to whoever is on call according to the rota. If they do not acknowledge it in time, it moves to the next person on the ladder, rung by rung, until someone takes it.

- A rota with overrides
- You set up duty as a rotation, and cover for a single night goes in without rebuilding the rota.
- A rung is a role, not a name
- A rung points at whoever is on call that night. Every rung has its own time to acknowledge.
- Reseller brands
- An alert about a reseller wakes their own on-call first. When their ladder runs out, it comes to you, never to another reseller.
- One incident instead of a storm
- A failing node opens many alerts at once: the node, stuck provisioning, failed backups. Alerts with a shared cause fold into one incident, and clients hear about it once.
- Planned maintenance
- During a maintenance window the alerts you expect are counted and silenced instead of waking the on-call person.
- The panel in your pocket
- The installed panel opens on the on-call screen: alerts, queue, nodes, tickets and delivery. Offline, it shows the last known state with actions disabled.
A public status page on your own installation
The status page runs on your server, under your domain. It shows 7 ready-made components, their live state and a 90-day availability bar, and visitors subscribe to updates by email.

- An incident starts as a draft
- Including the ones the panel creates by itself after a node failure. You publish it once you know what to say, with its impact and the affected components.
- Planned maintenance
- With a title, public or hidden.
- A banner for the client
- A signed-in client sees a banner in the panel when an incident affects their services.
- Bars from real events
- A component measured by samples gets a bar from those measurements. Payments and email, which nothing polls, get a bar from the published incidents, weighted by the impact you gave them.
For comparison: in HostBill the status page, the Status Updates app, comes with the Data Center edition at 1599 USD one-off. According to the vendor's price list: hostbillapp.com/pricing
Questions about customer support in Flaem
Tickets, chat, translation, Discord and the status page.
Yes. Every ticket has a thread on your Discord server, and a reply typed in the thread goes back to the ticket, where the client sees it in the panel.
No. A local model running on your side does the translation.
Only if you switch it on. First-line AI is an operator option, and it hands anything it cannot solve to a person.
A notice in the panel, always, and an email by default. The preview lasts at most 30 minutes, is read-only, and the audit log records every request.
On your Flaem installation, under your domain. Flaem does not host status pages or panels on its own domain.
Yes. They have their own help desk, knowledge base, message templates and support contact. A case that needs you is handed up to you with a note.
Polish, English, German, Czech and Ukrainian to start with. You can add another language, and articles without a translation show with a note about which language they are in.
Read next
See Flaem customer support in a demo
Tell us how many tickets you handle a month and where you talk to clients today. We will show tickets, chat, the Discord bridge and the status page, then work out your licence from the price list.