Why does adding a second Instagram account disconnect the first in some tools?

Users of some chatbot platforms report exactly this in public reviews — adding an additional account caused the primary account to disconnect from Meta, and profiles dropping connection mid-campaign. Causes vary (permission scopes, token refreshes, account linking conflicts), but for agencies the lesson is the same: test multi-account behavior during a trial before moving client campaigns onto any platform.

Should clients give agencies their Instagram passwords for automation?

Never. Official-API automation connects through Meta's authorization flow — the client grants access from their side (via Meta Business portfolio/asset sharing or by authorizing the tool directly), and access can be revoked anytime. Password sharing breaks Instagram's terms, triggers security checkpoints that disconnect automations, and makes the agency liable for anything that goes wrong.

How does DM automation pricing work across multiple client accounts?

It depends on the pricing model, and the difference compounds: per-contact platforms charge each account by its audience size (a viral month for any client raises that bill), while DM-volume or per-account models stay predictable. Agencies should model a realistic month across their whole roster before choosing — the cheapest tool per account is not always the cheapest across ten.

What should agencies report to clients about DM automation?

Four numbers monthly: conversations started (trigger volume), response coverage, link clicks from flows (tools like ReplyRush expose this per campaign), and captured leads or booked calls. Tie each to the campaign that produced it — DM automation is one of the few agency services where value is directly countable, which makes reporting a retention weapon.

How Agencies Manage DM Automation for Multiple Client Accounts

Q: How do agencies manage DM automation for multiple client accounts?

With a four-part system: proper access through Meta's business tools (clients grant asset access — no shared passwords), a multi-account automation dashboard so campaigns run per client without login juggling, a reusable campaign template library adapted per client, and a weekly reliability routine (connection checks, live trigger tests, per-client reporting).

Sneha Arora
2 days ago
6 min read

Updated: August 2026 · 10 min read

Quick answer: Agencies that run DM automation across many clients without losing their minds all converge on the same four-part system: clean access through Meta's business tools (never passwords), one multi-account dashboard instead of login juggling, a reusable campaign template library adapted per client, and a weekly reliability routine — because in agency work, an automation that silently disconnects isn't a bug, it's a churned client. Here's the full system, including the tool-stack math most agencies get wrong.

The Multi-Client Mess (You're Not Imagining It)

Running DM automation for one account is easy. Running it for eight clients is a different job entirely, and the tooling most agencies inherit makes it worse:

The login circus. Eight clients, eight sets of credentials, browser profiles multiplying, that one client whose 2FA codes go to their personal phone in another timezone. Every campaign edit is an expedition.

The disconnect roulette. This is the one that costs clients. Public reviews of major chatbot platforms describe the failure modes plainly: users report that adding a second account disconnected the first from Meta, and that Instagram profiles drop their connection mid-campaign — silently, with leads evaporating until someone notices. For a solo creator that's annoying. For an agency, it's your name on the campaign that stopped working during the client's launch week. (If you're firefighting this right now: our disconnect troubleshooting guide.)

The pricing multiplication. Per-contact pricing looks fine for one account. Across a roster, it compounds nastily: every client's audience growth raises your software cost, a viral month for any of them spikes the bill, and suddenly the tooling line item eats the retainer margin. (The contact-tier math in detail →)

The rebuild treadmill. Without a template system, every new client means rebuilding the same lead-gen flow, the same FAQ replies, the same giveaway sequence — from scratch, in someone else's account, under deadline.

None of these are automation problems. They're operations problems — and operations is what agencies are supposed to be good at. So here's the operating system.

Part 1: Access Done Right (No Passwords, Ever)

The foundation rule of multi-client automation: you never touch a client's password. Not because of etiquette — because of physics:

Password sharing violates Instagram's terms and trips security checkpoints ("suspicious login from new device"), which are themselves a leading cause of the disconnects you're trying to avoid.
It makes you liable for everything that ever happens in that account.
Official-API tools don't need it: the client authorizes access through Meta's own login flow, granting only the permissions automation requires — and they can revoke it anytime, which is precisely what makes clients comfortable saying yes.

The clean onboarding sequence for each new client: confirm their Instagram is a Business or Creator account connected to a Facebook Page they own → have them (or you, with Business-portfolio asset access) authorize the automation tool through Meta's flow → verify the connection with a live test before any campaign goes on the calendar. Fifteen minutes, once, and your access survives staff changes, password resets, and 2FA chaos.

Write this up as a one-page client-onboarding doc with screenshots. It makes you look institutional on day one — and it's half the pitch conversation anyway.

Part 2: One Dashboard, Not Eight Logins

The operational unlock is running client accounts from a single automation workspace — one login, per-client campaign views, no browser-profile archaeology.

Concretely with ReplyRush: one dashboard manages up to 3 Instagram accounts, with each account's triggers, flows, and analytics kept separate. For a freelancer or boutique agency with a 2–3 client automation roster, that's the whole problem solved on one screen — and the free plan's 1,500 DMs/month lets you prove the service on your first client before anyone pays for anything.

Honest scaling note, because agencies smell overclaiming: a bigger roster means multiple workspaces (e.g., one per client pod), organized under your agency's master email convention. Many agencies actually prefer that isolation — one client's workspace can be handed over cleanly if they leave, and no client's data lives beside another's. But model it before you commit: your roster size, your DM volumes, workspace count, total cost. That math — across ReplyRush, per-contact platforms, and white-label options — is exactly what our agency tool comparison works through. And whichever tool you pick: test the multi-account behavior during the trial. Connect two accounts. Disconnect one. Watch what happens to the other. Reviews suggest not every platform passes this test.

Part 3: The Campaign Template Library (Build Once, Deploy Everywhere)

Here's where multi-client work flips from burden to advantage: you get to amortize every campaign you've ever built. Maintain a library of your proven flows as internal templates:

The lead-gen engine — comment-keyword → delivery → email capture (the pattern)
The FAQ layer — the 7 keyword replies every business needs, restyled per client voice (the pattern)
The launch sequence — phase keywords for drops and promos (the pattern)
The giveaway flow — entry confirmation + capture + consolation (the pattern)
The booking funnel — qualify → calendar, for service clients (the pattern)

Deploying a "new" campaign for a client becomes: pick template → rewrite messages in their voice (this is the billable craft — never ship your template's voice) → swap links and keywords → test live → launch. An afternoon, not a sprint. Ten clients deep, your library is a genuine moat: you're not selling setup hours anymore, you're selling outcomes from proven systems — price accordingly.

Part 4: The Reliability Routine (Where Retainers Are Defended)

Agency automation has a harsher SLA than creator automation: the client is paying you specifically so this never silently breaks. The weekly routine, 20 minutes across a small roster:

Connection check — every account showing connected, every flow showing active. (After any client-side event — password reset, page admin change, new phone — recheck immediately; those are the classic disconnect triggers.)
One live trigger test per client — comment the keyword from a test account, confirm the DM lands. Dashboards can say "active" while a permission quietly expired; the live test is the only truth.
Analytics skim — trigger volume and link clicks per client vs. last week. A sudden zero is a disconnect you're catching before the client does; a sudden spike is an upsell conversation.
The monthly client report — four countable numbers: conversations started, response coverage, link clicks per campaign, leads/bookings captured. DM automation is one of the few agency services where value arrives pre-quantified — report it relentlessly and renewals defend themselves.

The Compliance Layer (Your Name Is on Every Campaign)

One agency-specific caution: you're operating other people's accounts, so the rules carry double weight. Official-API tools only, user-triggered flows only (no cold-DM "growth hacks," whatever the client asks for — it's their account that gets restricted and your reputation that travels), and put both points in your service agreement. The agencies that survive platform-policy waves are the ones that were never near the line.

FAQ

How do agencies manage DM automation for multiple clients? Four parts: password-free access via Meta's business tools, a multi-account dashboard, a reusable template library re-voiced per client, and a weekly reliability routine with live trigger tests and countable client reporting.

Why did adding a second account disconnect the first in my current tool? You're not alone — public reviews of major platforms report exactly that behavior, along with mid-campaign profile drops. Test multi-account connect/disconnect behavior during any trial before trusting it with client campaigns.

Should clients share their Instagram passwords with us? Never — it breaks Instagram's terms, causes security-checkpoint disconnects, and transfers all liability to you. Official-API authorization through Meta's flow is the only professional setup.

How many accounts can ReplyRush manage? Up to 3 Instagram accounts per dashboard — ideal for freelancers and boutique rosters; larger agencies run multiple workspaces (which also gives clean per-client isolation and handover).

What do we report to clients? Conversations started, response coverage, link clicks per campaign, and leads/bookings captured — monthly, tied to the campaigns that produced them.

The Bottom Line

Multi-client DM automation breaks agencies through operations, not automation: shared passwords, silent disconnects, compounding per-contact bills, and rebuilt-from-scratch campaigns. The four-part system — clean access, one dashboard, a template library, a reliability routine — turns the same service into the most countable, most defensible retainer line you sell.

Start with one client on the free plan, prove the numbers, then template everything.

Run your client campaigns on ReplyRush — 1,500 free DMs/month, no credit card →