Instagram comment-to-DM for social media managers

The mechanic is the same one every account on this site runs: comment, public reply, DM with the asset. What's different for an agency is the plural. You aren't managing your own comments, you're managing several clients' at once, and each connected account keeps its own campaigns, its own keywords, and its own leads inside the one workspace you log into.

Be clear on what "one workspace" means, because it's the honest boundary here. There aren't separate walled sub-accounts per client; there's one workspace with several connected Instagram accounts, and you keep clients apart by which account a campaign runs on and how you name it. The white-label pages and per-client CRM routing further down are what make that single workspace feel client-by-client to the people on the other end.

The account limit is the number that decides an agency's plan, and it's enforced the moment you connect: try to add an account past your plan's cap and the connect is refused with a clear message, not silently. So the plan follows the roster. Two or three clients fit Pro; a growing book of them is what Agency's ten accounts are for.

This is also the honest ceiling to plan around. If you're on Pro with three clients connected and you sign a fourth, that fourth account won't connect until you move up to Agency, so it's worth matching the plan to where the roster is heading rather than getting caught mid-onboarding. Reconnecting an account you already had doesn't count against the cap again; it's new accounts that meet the limit.

The person commenting under a client's post thinks they're dealing with that client, and the delivery should keep it that way. White-label capture pages, a Pro-and-above feature, let the page a lead lands on carry the client's look instead of an obvious third-party tool, so the hand-off from comment to download feels like it stayed inside the client's own world.

Keep the boundary honest with clients, though. The white-label part is the page, not the DM: there's no automatic client logo dropped into the message. The DM is the copy you write for that campaign, so if a client wants their voice in it, that's a matter of writing it that way per account, not a branding toggle. Sold accurately, page branding plus per-account DM copy is usually enough to make each client's flow read as theirs.

Leads all land in the one workspace, but a client usually wants them in their own system, and that's what the outbound webhook is for. On Pro and up, each captured lead is posted, signed with the X-Magnet-Signature header, to a URL you set. There's no native Salesforce, HubSpot, or Klaviyo connection to assume here; the webhook into Zapier or Make is the path to any of them.

The routing detail is what makes this work across a roster, and it hangs on how you name campaigns. Every lead event names the campaign that produced it, so if each client's campaigns are named for that client, a single Zapier or Make scenario can read the campaign field and fork: this client's leads into their CRM, that client's into theirs. The payload identifies the campaign, not the connected account, so client-by-client routing rides on that naming rather than on any account field. Email capture also syncs directly into Mailchimp or Kit on Pro, tagged by campaign, which covers clients who run their list on one of those. Everything else routes through the webhook, and naming that plainly to a client up front saves a "why isn't this in our CRM yet" conversation later.

The shared parts are worth knowing before a client roster leans on them. Engagement quota belongs to the workspace, not the account, so Agency's 100,000 monthly engagements are a pool every connected client draws from together. A client whose reel takes off can use a large share of that month's allowance, and while nothing gets dropped when the pool runs low, the overflow queue holding the excess is shared too, so pacing across clients is your call, not the tool's.

The reporting is shared in the same honest way. There's one Leads list and one activity feed for the workspace, and you tell clients apart by the campaign name and the connected account on each row, not by a separate login per client. For most agencies that's fine, since you're the one reading it and the client sees their own branded pages and their own CRM. If a client specifically wants their own isolated dashboard login, that's the one thing this setup doesn't hand them, and it's better said at the start than discovered later.

The account cap is the one that bites during growth. Sign a client that pushes you past three connected accounts on Pro and the new connect is refused until you're on Agency, so the plan should track a couple of clients ahead of the roster, not lag behind it. It's a clean limit, just one to see coming.

The expectations you set with clients are the next. A single workspace gives each client branded pages and their own CRM routing, but not a private login into an isolated dashboard, and not a native CRM integration that skips Zapier or Make. Promising either is how a good setup turns into a support thread. Say what it is: one workspace, several connected accounts, per-client branding and routing on top.

The last is the shared allowance. It's easy to price a client as if they get their own quota; they don't. Every connected account draws from the workspace's one monthly pool, so a roster of busy clients on Pro's 25,000 can run tight in a way a single account never would. Watch the 80% email that lands automatically, and if the roster is clearly outgrowing the plan, the no-card 30-day Pro trial is there to size up the account and the quota before onboarding the next client, not after the queue starts filling.