SOC 2 Type II audit in progress · EU, US and India data residency · a DPA you can sign
Trust Center →For MSPs
Your technicians are the constraint. Not your ticket queue.
An MSP measures its business in tickets per technician, which means every routine ticket a technician never has to open goes straight to margin. FlowTux runs one isolated workspace per client, answers the routine tickets in your client’s own branding, and does not charge you per technician for the privilege.
What you get per client
One workspace per client, isolated
Each client gets its own workspace with its own data, integrations, and allow-list. Data is logically isolated and access-scoped per organization — a technician sees only the clients they are assigned to.
A support portal in your client’s brand
The FlowTux support portal is the piece that matters most here: your client’s employees see your client’s branding, not ours. AI answers from that client’s knowledge base, and escalations arrive with the full transcript attached.
AI takes the first pass on every client
Password resets, access requests, and known errors close themselves on the categories each client has allow-listed. Your technicians pick up the tickets that actually need judgment, already triaged and deduplicated.
Priced per company, not per technician
Adding technicians does not change the bill, which is what makes a per-client rollout viable at all. Per-agent pricing is what makes most helpdesk tooling unusable across thirty tenants.
Every automated action is logged
Each fix runs as a tracked job against a named target and is written to an append-only audit trail — the record you need when a client asks what touched their machine.
Data residency per deployment
United States, European Union, or India, chosen at workspace creation. Clients with residency obligations stay in region, with a DPA you can sign.
The technician-hours arithmetic
Work it out with your own numbers rather than ours. The shape is what matters: auto-resolution compounds across tenants, because the same routine categories recur in every client you manage.
- Clients managed
- 30
- Tickets per client per week
- 40
- Weekly ticket volume
- 1,200
- Minutes saved per auto-resolved ticket
- 12
At those inputs, every 10 percentage points of auto-resolution returns roughly 24 technician-hours a week across the book. What your own rate turns out to be depends on how much each client allows you to allow-list — how we count an auto-resolution.
Reseller and margin terms
Multi-tenant billing, reseller pricing, and margin terms are handled case by case rather than published as a fixed rate card — the shape of the deal depends on how many tenants you run and whether you want FlowTux invisible to your clients or co-branded. The MSP multi-tenant dashboard is on the roadmap; the per-client workspace model works today.