Agency Groups
An Agency Group links two or more workspaces together as one agency's clients. It doesn't merge them — each client workspace keeps everything Workspaces already describes as fully isolated: its own inboxes, lists, campaigns, credit balance, and suppression list. What an Agency Group adds is a set of capabilities that deliberately reach across that isolation, scoped to the agency itself rather than to any one client.
A workspace either belongs to no Agency Group at all — standalone — or belongs to exactly one.
The eleven capabilities
| Capability | What it does | Covered in |
|---|---|---|
| Client portal | Clients log in to their own branded portal to see and reply to their own replies — read-only or reply-enabled, set per client | Client portal |
| Unified reply inbox | Merges replies across every client workspace into one newest-first feed for the agency operator — filterable, with reply-send support | Unified reply inbox |
| Custom domain | Use your own domain for the client portal instead of ForgeSend's — two DNS records added in sequence, ownership then routing, fully automatic once both are in place, one domain per Agency Group | Custom domain |
| Agency branding | One logo and one brand color, applied across every client portal and every portal digest email under the agency | Agency branding |
| Portal digest emails | Each portal user chooses Daily, Weekly, or Off for a summary of new Interested replies | Portal digest emails |
| Agency-wide bounce suppression | A hard bounce in one client's workspace blocks sending to that address in every other client workspace under the same agency | Suppression across clients |
| Cross-client campaign cloning | Duplicate a campaign from one client workspace directly into another client workspace under the same agency | Cross-client campaign cloning |
| Agency-level API keys | One screen lists every API key across every client workspace in the agency — create or revoke any of them without switching workspaces | Agency API keys |
| Platform-wide spam-complaint suppression | An address manually flagged as a spam complaint by 2+ different senders anywhere on ForgeSend is blocked everywhere | Suppression across clients |
| Command Center | A cross-client health rollup with risk flagging — owned agencies only | Command Center |
| Client Report | A credit-charged, AI-written client update, reviewed before sending | Client Report |
Agency-wide bounce suppression and platform-wide spam-complaint suppression are covered on the same page because they're the same kind of thing — automatic suppression that crosses a single workspace's own boundary — but they run at genuinely different scopes. One stays inside your agency; the other reaches every workspace on ForgeSend, agency or not. See Suppression across clients for exactly where that line falls.
Standalone workspaces
A workspace with no Agency Group is unaffected by nine of these eleven capabilities — there's no client portal to log into, no unified reply inbox spanning clients that don't exist, no domain to route to a portal that doesn't exist, no agency branding to resolve, no sibling workspace to check for a cross-client bounce, no other client to clone a campaign into or from, no agency-wide key list to appear on, and Command Center itself never renders without an owned agency group. Platform-wide spam-complaint suppression is the one clean exception: it isn't agency-scoped at all, so it applies to every workspace on ForgeSend, standalone or not. See Suppression across clients for why that one's different.
Client Report is the odd one out — unlike every other capability here, it's open to any workspace, agency-linked or not; there's no Agency Group check gating it. What varies is the data: every number it shows is drawn from the same agency-only snapshot history Command Center reads, so a standalone workspace's report comes back all zeros. See Client Report for the full explanation.
Where to go next
Next: Client portal