Features / Platform
For agencies
Many clients, one account, nothing leaking
Run support for several client products from one login, each with its own branding, its own portal and its own data, which cannot cross between them.
What it does
- One account holding many client organizations
- Separate branding, domain and portal per client
- Staff scoped to the clients they actually work on
- Billing at the agency level or per client
Without it
One tool per client is how agencies end up with eleven logins
Four clients, four browser profiles
You run support for four products that are not yours. Every one of them has its own login, its own help desk, its own help center, and your morning starts by working out which tab is which.
Putting them in one inbox is worse
You try to consolidate, and within a week someone replies to a customer of client A signed off as client B. The signature was right for the last conversation. It was not right for this one.
The contractor for one account can see all of them
You bring someone on to cover a single client for six weeks. To do the job at all, they need a login, and the login shows them every other client's conversations, contacts and revenue complaints.
How it works
One organization per client
Each client is its own organization with its own name, address, logo, brand color and typeface. Conversations, contacts, articles and boards belong to that organization and do not exist outside it.
What that includes
- address
- logo
- brand color
- typeface
You switch clients from the rail
Your login carries your memberships. Picking a client changes the inbox, the help center, the boards and the settings together, so there is no half-switched state where the queue moved and the branding did not.
What that includes
- the help center
- the boards
- the settings together
- the branding did not
Inside a client, products separate again
A client with three products gets three. Every conversation, article, roadmap item and changelog entry belongs to exactly one product, and the switcher at the top of the rail narrows the whole app to it.
What that includes
- Every conversation
- article
- roadmap item
Staff are scoped to what they work on
A member is either on every product or on a named list of them, and changing that is written to a scope audit with the previous and next access. Per-product scoping is a Scale plan feature.
The separation is the database's job
Client data is kept apart by row-level security inside a transaction, not by application code remembering to filter. The contractor does not see the other clients because the query cannot return them.
What it means for you
You can hire for one account.
Bringing in help for a single client stops being a trust exercise. You scope them, they see that client, and you do not spend the first week explaining what not to click.
Nothing goes out with the wrong name on it
The brand, the help center and the sender are attached to the client, not to your memory. The reply that leaves looks like it came from them, because as far as the customer is concerned it did.
A new client is a new organization, not a new system
You are not standing up another help desk, another knowledge base and another board. You add the client and the tooling you already know is waiting there.
The honest limit: Each client organization is billed and configured on its own today. The agency layer above them, one bill and one view across every client, and a separate custom domain per client portal, are designed and not yet built.