One login for every client
Pick a client from the rail and the inbox, help center, boards and settings all switch together.
a browser profile per clientTore holds your agency, each client's account and every product inside it. Switch with one click and the inbox, help center, chat widget and connected code switch with you. Nothing crosses between clients.
Tore opens soon. Join the waitlist and we'll email you the day you can start.
Example: the agency Northwind Studio is signed in to Tore. It switches between its clients Beacon Data, Acme Corp and Lumen Health, and between each client's products. Every switch changes the breadcrumb, the inbox, the help center, the chat widget's brand colour and the connected repository and error project, and each client's data stays separate. You can pick a client or product yourself with the buttons in the rail.
Clients
Products in Beacon Data
Most support tools assume one company with one product. Tore is built for an agency running many clients, and a business running many products.
Pick a client from the rail and the inbox, help center, boards and settings all switch together.
a browser profile per clientEach client's data is kept apart by the database itself, not by code that remembers to filter.
hoping the filter was set rightA white-label widget and help center per client, on their own domain, with no Tore branding.
"powered by" on every client's widgetEach product gets its own queue and help center, and staff see only the products they work on.
one help desk subscription per productThree levels, each with its own job. A business with several products uses the bottom two. An agency uses all three.
One login and one place to run every client.
Each client is its own organization, sealed off from the others.
Each product inside a client keeps its own everything.
Agency console
See every client in one place: their products, their open conversations and what the AI is costing each of them. A new client is a new account, not a new system to learn.
Data isolation
Each client's data is kept apart by the database itself, inside every query, not by application code remembering to filter. A contractor scoped to one client doesn't see the others, because the query cannot return them.
Dan Okaforcontractor · NorthwindAcme Corp onlyrow policy: organization = Acme CorpWhite-label per client
Every client gets a widget, help center and portal that look like their product. Their customers never see Northwind, and never see Tore.
Multiple products
Not an agency? The same structure works for one business with several apps. Each product has its own queue, help center, roadmap and changelog, and your staff see only the products they work on.
Alex
Priya
TomSwitching in
Import a client's existing help desk from Zendesk or Intercom straight into their own account and product. Their past conversations, contacts and articles come with them.
Add the client, connect their repository and help center, and your team is working their queue under their brand.