How Do You Manage Multiple Client Support Accounts in Macha? The Org Switcher (2026)

In Macha you manage multiple client support accounts by creating one organization per client and moving between them with the org switcher in the bottom-left corner of the sidebar, with no separate logins. Each organization is a fully isolated workspace: its own connected helpdesk, its own agents, knowledge sources, schedules, Studies, team membership, plan, and ticket allowance. Nothing leaks across the boundary, and releases on April 2 and April 17, 2026 (plan badges, a full refresh on switch, a scrollable list) made running five or fifteen of them manageable.

What does "organization" mean in Macha?

In Macha, the organization is the unit of isolation. When you switch orgs, you're not filtering a shared view; you're loading an entirely different workspace. Each org owns:

• Its own helpdesk connection. One org connects to Client A's Zendesk; another to Client B's Freshdesk. Macha sits as an AI agent layer on top of whichever helpdesk that org uses. It isn't a helpdesk itself, so each org's tickets stay in that client's own system.
• Its own agents and knowledge. The Ticket Triage agent you built for one brand, the macros, the connected Notion or Confluence sources: none of it appears in another org.
• Its own team. Membership is granted per organization, with Admin and Member roles set independently in each one.
• Its own plan and allowance. Each org carries its own subscription and its own monthly ticket allowance. Tickets are billed per conversation (one thread with one person, charged once) and allowances are not pooled across orgs.
• Its own default model and settings. Even the default AI model used for new conversations is set per org.

If you've used a multi-tenant developer tool, the mental model is familiar. Datadog puts its org switcher at the bottom-left of the nav and isolates data per organization; Clerk's <OrganizationSwitcher /> is the canonical pattern for switching between organizations in a multi-tenant app. Macha follows the same well-trodden pattern (switcher in the nav, hard per-org isolation behind it) tuned for support teams rather than developers.

Where is the org switcher, and how do you use it?

The switcher sits in the bottom-left corner of the sidebar. It shows your name, the current organization, and a compact plan badge for that org. Click it and a dropdown opens listing every organization you belong to, each with its own plan badge, plus shortcuts to Settings and Log out.

Three details are worth calling out, because they came from deliberate April 2026 updates:

Plan badges, including trial status

Since the April 2, 2026 release, every organization in the switcher shows its plan as a compact tag, including trial-expiry status. (The release notes list the badges as Trial, Professional and Enterprise; Macha has since moved to one plan priced by ticket volume, so the badge mainly tells you which orgs are still on a trial.) If you manage a portfolio of client workspaces, this is the difference between guessing and knowing: you can see at a glance which orgs are on a trial and which are paid, without opening each one's billing page. For an agency onboarding clients on staggered trials, that badge is a small but real operational signal.

A full refresh on every switch

Also shipped April 2: switching organizations fully reloads the page. This is intentional. Because an org swap changes everything (connectors, agents, usage, team, settings), Macha does a hard reload to guarantee that every panel reflects the new context, rather than risk a stale agent list or a usage counter from the previous org bleeding through. It's a fraction slower than an instant in-app swap, and that's the trade Macha made on purpose: correctness over a flashy transition. (If you've ever seen a dashboard show one tenant's data under another tenant's header, you know why.)

Built to scale to many orgs

A follow-up on April 17, 2026 made the switcher scrollable: when you belong to a long list of organizations, the dropdown scrolls internally while keeping Settings and Log out visible. That's the small fix that turns the switcher from "fine for two orgs" into "usable when you're running fifteen."

What settings are scoped to each organization?

The clearest way to understand isolation is to look at the per-org Settings. Open Settings from the switcher and you land in a workspace whose every tab is scoped to the current organization.

Organization

The Organization tab holds the workspace's identity: its name, a URL slug, and the default AI model used for new conversations in that org. Two practical notes from the live UI:

• The organization name cannot be changed after creation. Name it deliberately: Acme Production, not test.
• The default model is per org, so one client workspace can default to a faster model and another to a stronger one, with no global setting forcing them to match. The model doesn't change what a ticket costs; Macha charges the same per ticket whichever model runs.

Team

Membership is granted per organization on the Team tab. You invite a colleague by email, and they're added to that org only; being an Admin in one workspace gives them nothing in another. Roles are Admin and Member, and you can promote a member with Make Admin or Remove them inline. Seats are unlimited, so adding a client's in-house lead costs nothing. For an agency, this is how you give Client A's lead access to their own org without exposing any other client.

Billing

Each org has its own subscription and ticket allowance on the Billing tab, and the dashboard home surfaces a per-org Current Plan card with live usage and a reset date. There's no shared pool: each org picks its own volume tier (from $299 a month for 750 tickets up to $3,999 for 10,000), and topping up one org doesn't touch another. For agencies this is usually a feature, since you can bill each client's usage cleanly, but it's worth understanding before you assume usage is global.

Privacy and data

The Privacy tab carries each org's data controls. Macha's GDPR work shipped scheduled deletion for organizations as well as accounts: an admin can schedule an org's deletion, cancel it any time within 30 days, and after that grace period the org's agents, connectors, conversations, documents, triggers and custom tools are removed, with cascade cleanup of files, database collections and memberships. So an org isn't just isolated while it's live; it has a clean, auditable offboarding path when a client relationship ends.

How does this compare to managing client accounts in your helpdesk?

If you run an agency or BPO, you've probably already wrestled with multi-client setups inside a helpdesk. It's worth being precise about what Macha does and doesn't replace here, because the two layers solve different halves of the problem.

Helpdesks tackle multi-client at the ticketing layer. Freshservice gives MSPs a multi-account experience with the Freshworks Switcher (the grid in the bottom-left that hops between customer accounts); Freshdesk lets you run separate branded portals per product from one helpdesk; Jitbit auto-groups users by company and reports per organization. Those are real, mature features, and Macha doesn't compete with them. Macha is an AI agent layer that sits on top of whichever helpdesk each client already runs, so the question isn't "Macha or Freshservice"; it's "how do I keep the AI agents, knowledge, and usage for each client just as cleanly separated as their tickets already are?"

That's the gap the org model fills. Where a helpdesk isolates tickets and portals, a Macha organization additionally isolates the things the AI layer introduces:

The practical upshot for an agency: each client keeps their own helpdesk login and their own Macha org, and the org switcher becomes your roster across both. You're not consolidating clients into one shared AI workspace (that would pool knowledge and usage you need kept apart); you're giving each one a walled garden and a one-click door between them.

Who actually needs multiple organizations?

You don't need more than one organization to run Macha well. Reach for multiple orgs when isolation is the point:

• Agencies and BPOs. One org per client, each wired to that client's own Zendesk or Freshdesk, each billed and staffed separately. The switcher is your client roster.
• Multi-brand companies. Separate brands or regions that run distinct helpdesks (and distinct knowledge) get one org each, so an agent for Brand A never answers with Brand B's policies.
• Staging vs production. Keep a throwaway org for testing agents, prompts, and connectors, so experiments never run against the live ticket queue.
• Clean separation of budgets. When two teams must not share a ticket allowance, two orgs enforce it structurally.

If instead you want several people collaborating in one shared workspace, that's not multiple orgs; that's one org with multiple team members. Don't split into separate organizations just to add colleagues; you'll fragment your knowledge and allowance for nothing.

What are the limits of running multiple orgs?

Multiple orgs is a clean abstraction, but it isn't free. Plan around these:

• No single cross-org pane. Macha shows you one org at a time. There's no consolidated dashboard that rolls up metrics, usage, or ticket volume across all your orgs at once; you switch and read each individually. If you manage many clients and need portfolio-level reporting, you'll be assembling that yourself for now.
• Allowances don't pool. Each org bills and uses its ticket allowance on its own. Plan the spend per workspace; you can't lend tickets from a quiet org to a busy one.
• Switching is a full reload. By design (see above), so it's a beat slower than an instant swap, and anything unsaved in the org you're leaving should be saved first.
• Org name is permanent. You can't rename an organization after creation; only the slug is editable. Name it for the long term.
• Membership and welcome chats are per org. Inviting someone to one org doesn't add them elsewhere, and the free post-onboarding welcome chat is one per organization: a new client org gets its own, but it isn't a recurring perk.

None of these are blockers; they're the predictable cost of true isolation. The teams that are happiest with multi-org are the ones that want hard walls between workspaces, and for them "no shared anything" is exactly the point.

FAQ

How do I manage multiple client support accounts in Macha? Create one organization per client. Each org connects to that client's own helpdesk (Zendesk, Freshdesk, Gorgias, Front, HubSpot or Intercom) and holds its own agents, knowledge, team, plan, and ticket allowance. You move between them with the org switcher in the bottom-left of the sidebar: no separate logins, no shared data.

How do I switch between organizations in Macha? Click the org switcher in the bottom-left of the sidebar. It shows your name, the current org, and its plan badge. The dropdown lists every organization you belong to (with plan badges) plus Settings and Log out. Pick one and the page reloads into that workspace.

Is data shared between my organizations? No. Each organization is fully isolated: its own helpdesk connection, agents, knowledge sources, schedules, Studies, team, plan, and ticket allowance. Nothing crosses the boundary.

Do organizations share a ticket allowance? No. Every org has its own subscription and its own monthly allowance, billed per ticket. There's no shared pool, so plan spend per workspace. See the pricing page for current volume tiers.

Can I rename an organization later? The organization name is fixed after creation; only the slug is editable. Name each org deliberately when you create it.

Why does the page fully reload when I switch orgs? By design. A switch changes connectors, agents, usage, team, and settings all at once, so Macha does a full refresh to guarantee every panel reflects the new org: correctness over a faster but riskier in-app swap.

Is there a limit to how many organizations I can join? Macha doesn't publish one, and the switcher is built to scale: since April 17, 2026 the dropdown scrolls when you belong to many orgs, keeping Settings and Log out visible.

How do you set up your first client organizations?

If you're managing multiple client support accounts across agencies, BPOs, or your own portfolio of brands, Macha organizations keep each one clean, isolated, and separately billed, with a one-click switcher tying them together on top of whatever helpdesk each client already uses. Start a free trial ($50 of usage, no credit card required), connect your first helpdesk, and read the docs or browse the blog for how to build agents inside each org.

Written by Abbas (Customer Support & AI, Macha) · Reviewed by Ankeet Guha (Co-founder & CTO) · Published 2026-06-24 · Last updated 2026-09-24.