How to Manage Multiple Client Support Accounts with the Macha Org Switcher

In Macha, the answer is the organization — and the org switcher that ties them together. This deep-dive shows exactly how to manage multiple client support accounts inside Macha: what an org isolates, how switching works, what the April 2026 updates changed, how the model compares to how helpdesks themselves handle multi-client setups, and — honestly — where the edges are.

An organization in Macha is a fully isolated workspace: its own connected helpdesk, its own agents, knowledge sources, schedules, Studies, team membership, plan, and credit balance. Nothing leaks across the boundary. The org switcher — the control in the bottom-left of your sidebar — is how you hop between client accounts without logging out, and recent updates (plan badges, a full refresh on switch, a scrollable list) make running five or fifteen of them genuinely manageable.

What "organization" means 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/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 credits. Each org carries its own subscription and its own credit balance. Credits are consumed per AI action (roughly 0.5–9 credits by model, with the default GPT-5.4 Mini at 1) and 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 the switcher lives, and how to 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.

Two design choices are worth calling out, because they reflect deliberate April 2026 updates:

Plan badges, including trial status

As of the April 2, 2026 release, every organization in the switcher shows its plan — Trial, Professional, or Enterprise — as a compact tag, including trial-expiry status. 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 still on a trial that's about to lapse and which are on a paid plan, 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 now fully reloads the page. This is intentional. Because an org swap changes everything — connectors, agents, credits, 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 credit 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 23, 2026 made the switcher scrollable: when you belong to a long list of organizations, the dropdown scrolls internally while keeping Settings and Log out pinned and reachable. That's the small fix that turns the switcher from "fine for two orgs" into "usable when you're running fifteen."

What's scoped per org: the four settings tabs

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 a cost-sensitive client workspace can default to a cheaper model while a premium one defaults to a stronger model, with no global setting forcing them to match.

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. For an agency, this is how you give Client A's in-house lead access to their own org without exposing any other client.

Billing

Each org has its own subscription and credit balance on the Billing tab, and the dashboard home surfaces a per-org Current Plan card with live credit usage and a reset date. There's no shared pool: an org on Professional draws from its own monthly credits, and topping up one org doesn't touch another. For agencies this is usually a feature — you can bill each client's usage cleanly — but it's worth understanding before you assume credits are global.

Privacy and data

The Privacy tab carries each org's data controls. Notably, Macha's GDPR work shipped scheduled deletion for organizations as well as accounts — a 30-day scheduled deletion with cascade cleanup of the org's 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 this compares 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 credits 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 credits you need kept apart) — you're giving each one a walled garden and a one-click door between them.

Who actually needs multiple orgs

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 credit budgets. When two teams must not share a credit pool, 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 credits for nothing.

Watch-outs: where the model has edges

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, credits, 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.
• Credits don't pool. Each org bills and burns credits on its own. Plan the spend per workspace; you can't lend credits 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, or Front) and holds its own agents, knowledge, team, plan, and credit balance. 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 credits. Nothing crosses the boundary.

Do organizations share a credit balance? No. Every org has its own subscription and its own credit balance, and credits are consumed per AI action. There's no shared pool, so plan spend per workspace. See the pricing page for current plans.

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, credits, 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? The switcher is built to scale — as of April 2026 the dropdown scrolls when you belong to many orgs, keeping Settings and Log out reachable. Agencies routinely run a long list of client workspaces.

Try it

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 7-day free trial, 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-06-24.