A support portal your end users actually like.
FlowTux is an AI-powered helpdesk for internal support. The Support Portal extends it outward: a branded helpdesk where Tux AI answers your customers first, your team handles the rest, and every conversation lands in the same queue you already run, with SLA, routing and AI triage built in.
HirePro Support
Assistant · replies right away
What Tux AI has actually handled
Why AI-first support pays
- $0.62
- avg AI resolution vs $7.40 human-handled
- McKinsey, 2026
- Up to 45%
- lift in deflection when AI resolves rather than retrieves
- McKinsey, 2026
- 55%
- faster first response with AI triage
- Freshworks, 2025
Published industry benchmarks for AI-assisted support, not FlowTux customer results. Your own deflection rate is reported per portal in the dashboard from day one.
How it works
01
End user asks
Your customer or employee opens your branded portal and describes the problem in their own words. No account to create — an email address and a sentence is the whole form.
02
Tux AI answers first
AI reads your knowledge base and answers in seconds. Routine questions close there, and the reader can ask for a person at any point.
03
Your team takes over
One tap on “Talk to a human” opens the conversation in your existing FlowTux queue as a support ticket, routed to the team you set for the portal, with the transcript as its description.
When AI hands over
The conversation becomes a ticket, not a copy-paste job.
An escalated portal chat opens in your queue as a support ticket: the transcript is the description, the requester’s email is on the ticket, and it lands with the team you routed the portal to. Your agents pick it up the way they pick up any other ticket — same statuses, same assignment, same activity timeline.
#TKT-9C42
My invoice charged the old card. How do I update it and get a corrected invoice?
Status
OpenPriority
MediumSource
PortalType
SupportDescription
Customer: Invoice charged the old card…
AI Assistant: Open Billing → Payment methods…
Customer: Reissue never arrived — talk to a human
Activity
created · Escalated from support portal chat.
What it changes for your team
Answers in seconds, at any hour
Nobody waits for business hours for a question your docs already answer.
Grounded in your docs, never improvised
Tux AI answers from your knowledge base only. When your articles do not cover it, it says so and offers a person instead of guessing.
Escalations arrive already briefed
Ask for a human at any point. The chat becomes a ticket whose description is the transcript, so your agent reads instead of interrogating.
Branded to you, embedded anywhere
Your logo, colours and welcome message, on your own domain or as a widget on your site — with signed identity if you gate it behind a login.
Not a separate tool. The same queue, opened to the outside.
Bolt a second helpdesk onto your stack and you inherit two inboxes, two backlogs and two sets of metrics. A portal conversation here becomes a ticket in your existing FlowTux workspace: your statuses, your priorities, your assignment and SLA rules, and the same Tux AI actions your team already uses on internal work. One system, internal and external.
From $49
/month, on top of your plan
Scales with the plan it sits on, and every tier includes a monthly allowance of AI-answered conversations. Agent seats are never charged.
What you can check for yourself
FlowTux is early and has no customer logos to show you. These are the claims you can open and verify instead.
Answers come only from your docs
Tux AI is instructed to answer from your knowledge base alone, and to offer a human when your articles do not cover the question.
How Tux AI works →Portal data stays in your region
Pick United States, EU or India at signup. Conversations and backups stay there, encrypted in transit and at rest.
Data residency →Your content is not training data
No personal data sold, no customer data used to train foundation models. It is in the DPA you sign.
Security posture →Metered on AI answers, not seats
The add-on carries a monthly allowance of AI-answered conversations. Putting more agents on portal chat never changes the bill.
See pricing →Turn on your support portal today.
An add-on on Pro and Enterprise. Enable it in Settings, brand it, upload your knowledge base, and embed the chat widget on your site.
Before you start a trial
What does setup actually involve?
Three steps, all in Settings: enable the Support Portal, brand it with your logo, colours and domain, and upload your knowledge base. Embedding the chat widget on your own site is one script tag. There is no workflow designer to configure and no implementation partner to hire.
How does Tux AI learn our answers?
You build the portal knowledge base from your existing material: write articles directly, import a page by URL, or upload a file. Tux AI is instructed to answer from those articles alone. When an answer is wrong you correct the article, and the next answer changes with it. You can also set the assistant persona, tone and guardrails.
What happens when the AI cannot answer?
It says the knowledge base does not cover the question and offers to bring in a person rather than improvising. The end user can also tap "Talk to a human" at any point. Either way the conversation opens in your FlowTux queue as a support ticket whose description is the full transcript, routed to the team you set for the portal.
Do end users need an account to use the portal?
No account and no password. A visitor gives an email address and describes the problem — that is the whole form, and the email is what replies and the resulting ticket are attached to. If you already log people in on your own site, you can embed the portal with a signed identity so their email is verified rather than typed.
What does the Support Portal add-on cost?
It scales with the plan it sits on. On Pro ($99/month) the add-on is +$49/month and includes 500 AI-answered conversations. On Enterprise ($199/month) it is +$99/month and includes 2,000. The portal requires Pro or Enterprise, and agent seats are never charged on either tier — you can put your whole team on portal chat without changing the bill.
What counts against the allowance, and what happens if we go over?
A conversation counts once, in the billing month it starts, when Tux AI answers it at least once. Follow-up messages in the same thread do not count again, and replies from your agents, tickets created from escalations and knowledge base article views are never metered. The allowance resets each billing period and does not roll over. Conversations above it are billed in blocks of 100 on your next invoice — $9 per 100 on Pro, $7 per 100 on Enterprise — and the portal keeps answering; nothing is cut off mid-month. Above 10,000 conversations a month we agree volume terms with you instead. The full wording is in section 6 of the Terms.
Where does our customer data go, and is it used for training?
Portal conversations live in your FlowTux workspace, in the data region you pick at signup, encrypted in transit and at rest. FlowTux does not sell personal data and does not use customer data to train foundation models; the commitment is written into the DPA.
How is this different from running Zendesk or Intercom alongside FlowTux?
A second helpdesk means a second inbox, a second backlog and a second set of metrics. The Support Portal opens the queue you already run to the outside, so customer conversations and internal tickets share one queue, one SLA model and one routing setup.