Instantly dashboard for agencies: 4 options compared

Agencies running cold email on Instantly hit the same wall around client three or four: Instantly's dashboard is per-workspace, and an agency's problems are cross-workspace. Which client's campaign broke overnight? Whose bounce rate is creeping? Which mailbox silently disconnected? Answering that means logging into every workspace, every morning.

There are four realistic ways to get one Instantly dashboard across all your agency's clients. Here's each one honestly — including who each is right for. (Full disclosure: option 4 is our product. The other three are genuinely the right answer for plenty of agencies, and we say so below.)

Option 1: Native Instantly, one login at a time

What it is: the default. One workspace per client (the correct structure — here's why), and you open each one daily.

Where it works: up to about 3 clients. The per-workspace dashboard is good — campaign analytics, warmup status, and inbox placement are all there. Three logins is a manageable morning routine.

Where it breaks: the routine scales linearly with clients and gets skipped under load. Nothing tells you which workspace needs attention, so you check all of them to find the one that matters — or you don't, and a silent failure runs for days. And once you've found the workspace that's gone quiet, working out why the campaign stopped sending is a separate checklist entirely. There's no cross-client history, no alerting, and client reporting means transcribing numbers by hand.

Cost: free, except the hours.

Option 2: The spreadsheet roll-up

What it is: a sheet with a tab or row per client; someone pastes in sends, replies, and bounces weekly (or daily, briefly, until that stops happening).

Where it works: 3–5 clients, and as the system of record for retainer and pipeline data that doesn't live in Instantly anyway.

Where it breaks: the sheet is a snapshot, not a monitor. It's only as current as the last paste, it can't alert anyone, and the manual copying is exactly the kind of work that gets deferred in a busy week — which is when things break. Every agency has a version of this spreadsheet; almost none of them are up to date.

Cost: free, plus 2–5 hours a week of copying that someone quietly resents.

Option 3: DIY on the Instantly API

What it is: Instantly's API exposes campaigns, analytics, and account status. With scripts, n8n/Zapier flows, or an internal dashboard, you can pull every workspace into one view you fully control.

Where it works: agencies with a technical founder or developer, an unusual workflow that off-the-shelf tools don't fit, or an existing internal ops stack to plug into.

Where it breaks: it's a real engineering project wearing a weekend-script costume. Per-workspace auth, scheduled syncs, storing history for trends (the API gives you now; trend detection needs then), threshold logic for alerts, and maintenance every time the API or your needs change. The build is a week; the ownership is forever.

Cost: "free" — priced in engineering hours, typically the most expensive option on this page.

Option 4: A dedicated monitoring layer (Coldops)

What it is: Coldops connects each client's Instantly workspace by API key and gives the agency one dashboard on top: every client scored for health, campaigns and mailboxes watched continuously, alerts when a bounce spike, dead mailbox, reply-rate drop, or idle campaign appears — before the client notices — and the weekly client update written automatically from the live numbers, white-labeled under your agency's name. You can see how the Instantly integration works and what data it pulls in on the Coldops + Instantly integration page.

Where it works: agencies with roughly 3–30 client workspaces, where the morning check has outgrown the morning and weekly reporting eats Fridays. Setup is pasting one API key per client; most agencies find an issue they didn't know existed on the very first sync.

Where it doesn't: one or two clients — native Instantly is honestly fine, and a monitoring layer is overhead you don't need yet. Deep custom ops logic — option 3 exists for a reason.

Cost: free for 14 days across as many client workspaces as you like, no card; one paid plan from $49/month, sized by mailboxes watched.

Side by side

How to decide

• 1–3 clients: stay native. Add a written daily checklist so the check survives busy days.
• 3–5 clients: the spreadsheet works if someone actually maintains it. Be honest about whether that's true; also verify each client's sending health directly with a free deliverability check.
• Developer on staff + unusual needs: the API is capable — treat the build as a real project.
• Past 5 clients, no appetite to build: Coldops is built for exactly this. Connect one workspace free and see what the first sync finds — that result is usually the whole evaluation.

The structural point stands regardless of tooling: agencies rarely lose clients to bad campaign results. They lose them when a problem reaches the client before it reaches the agency. Whatever option you pick, pick one that closes that gap.