Isolated data per customer, multiple brands per tenant, a portal and sending identity per brand, and a feature registry that lets you turn any capability on or off per tenant — enforced on the server, not hidden in the UI.
Logo, colours, domain, portal, support numbers, ticket signature, and outbound sender per brand — and a brand that defines its own values replaces the parent's wholesale, so a white-labelled customer never sees your details.
One registry governs every navigable and gateable surface. Turn a capability off for a tenant and it disappears from web and mobile alike — and the API rejects it too, so a bookmark or a direct call cannot get it back.
Welcome sequences, guided agent enrolment, portal setup, and a migration engine that pulls customers, contracts, and tickets out of the system you are leaving.
A branded end-user portal per brand or customer: custom domain, logo, colour, ticket form, and knowledge base.
Every navigable surface and gateable action is switchable per tenant, defaulting on, honoured identically on web and mobile, and enforced server-side.
Granular role-based access over data and actions, team routing, partner technicians, and per-customer portal administrators.
Connect the system you are leaving, dry-run the import, review the diff, and cut over — customers, contacts, contracts, and ticket history.
Automated welcome sequences and a guided agent enrolment flow so a new customer is live the same day it is signed.
Bring your own domain for the portal and support address, and sign in with Microsoft Entra, magic link, or password plus MFA.
Modern ticketing with custom workflows, saved views, and a white-label client portal.
See HelpdeskTenant-branded outbound mail through one dispatcher, with a full audit row for every inbound and outbound message.
See Email & ComplianceA full wiki with spaces, templates, versions, comments, labels, and search — plus AI authoring and a customer-facing knowledge base.
See DocumentationYes. Brands carry their own portal, domain, sender identity, support numbers, signature, and intake numbers — and each brand replaces the tenant defaults wholesale rather than merging into them.
It disappears from their navigation on web and mobile, and the backend rejects the routes it owns. Hiding is never the enforcement mechanism.
The built-in migration engine connects to the source system, imports customers, contacts, contracts, and tickets, and supports a dry run before cutover — so you can rehearse the move before you commit to it.
Deploy your first agent in minutes. See the platform in action — book a walkthrough or kick the tires on a free trial.