Skip to content
Bloom · For agencies

Bloom for social media agencies.

Bloom runs every client as a separate brand inside one workspace, so an agency publishes to all 18 of each client’s networks, routes every post through a client_reviewapproval state the client signs off in, and hands that client a white-label report that traces a click from a specific post to a named lead. Access is granted per connected account, so a freelancer booked for one client never sees another client’s inbox. All 18 networks publish — there is no connect-only tier — and AI drafting runs on your own API key, so a fifteenth client adds no per-seat AI charge.

Its own app & sign-in · per-account access · your own AI key
18
networks, all publish
5
roles, eight actions
4
approval states
10
catch-up / 5-min tick
01 · Separation by construction

Every client is a brand, cleanly separated.

Multi-client is not a plan upgrade in Bloom — it is the shape of the data. An organisation holds brands, a brand holds connected accounts, and a member’s access is granted per connected account. That one choice is what lets a freelancer work on two clients while neither client knows the other exists, and it is the only granularity that survives contact with a real agency roster.

Per-brand weekly queues

Each client’s schedule is keyed to the brand — platform, weekday, hour and minute — and resolved in that client’s own timezone, so a client in another country gets their 9am rather than yours. Two clients never share a slot grid by accident, and a seasonal campaign is entered once against the brand that owns it.

Access granted per account

A seat is scoped to the connected accounts it is given, not to the whole workspace. A contractor hired for one launch sees that client’s accounts and nothing beside them — no other inbox, no other analytics, no other queue. Revoking one account’s token stops that stream and leaves every other client untouched.

Credentials encrypted at rest

Every connected-account credential is stored under AES-256-GCM with a scrypt-derived key. Nine networks connect through one-click OAuth and nine take a pasted credential; either way the token is held once and reused by publishing and the unified inbox alike.

The unified inbox reuses that same stored credential — see the inbox page for which networks return conversations, and the full read-back table on the networks page.

02 · Sign-off that is a recorded step

A client_review state your client signs off in.

“Did the client approve this?” should have an answer that is not somebody’s memory of an email. Bloom’s approval chain has four states in order, and the third exists specifically so an agency can hand a client the power to say yes without handing them the publish button.

The editor writes

draft

The post exists, has its per-network targets set, and can be edited freely.

Your team checks

internal_review

Where a junior's work reaches an account lead before a client ever sees it.

The client signs off

client_review

A client seat is scoped to exactly this step — review and approve, nothing else.

Cleared to queue

approved

The state a post carries once sign-off is recorded, with a timestamp, not a Slack memory.

Four states, in that order. The client_reviewstep turns sign-off into a timestamped event rather than a thread nobody can find six weeks later — which is also what makes a dispute about “who approved the typo” answerable from the record.

03 · Prove the lead, not the impression

Show which post produced the lead.

The hardest part of keeping an agency retainer is proving the work moved revenue, not reach. Bloom’s short links are part of the product rather than a bolt-on, so the chain from a post to a conversion to a named lead is one dataset — presented to the client under your brand, not Bloom’s.

Links a client can read aloud

Each short code is eight characters drawn from a 32-character alphabet with the ambiguous glyphs removed, so a link quoted on a slide or typed from a podcast mention lands where it should. Per-platform UTM parameters are written without anyone hand-editing a query string — the step where cross-channel reporting usually breaks.

Bots do not inflate the numbers

Every click is classified as bot, mobile or desktop, so an automated crawler hitting a link does not pad a client’s result. Where a network will not release its engagement — Pinterest sits behind app review, X read access is paid — the report shows the reason rather than an implied zero.

Reported under your brand

A white-label report shows the client the posts, the clicks and the leads under your agency’s identity rather than Bloom’s, so the quarterly conversation is about the revenue a campaign produced rather than the impressions it accumulated.

The full read-back set — which networks report engagement and why the others cannot — is on the networks page.

04 · Five roles, eight actions

A client seat that cannot publish.

Owner, admin, editor, client and viewer — five roles, each checked against eight distinct actions rather than a single admin flag. That granularity is what lets you give a client a real login with real numbers while keeping the schedule, the connected accounts and the publish button out of their reach.

Client

A seat built for sign-off: it can see the brand’s drafts, move a post through client_review, and read the attribution report — and it cannot publish, reschedule or connect an account. This is the role that answers “can we give the client a login?” without any of the usual anxiety about what they might change.

Editor

Drafts, refits a post per network and sends it to review, but does not hold the final approval. The role an account manager or a freelancer sits in, scoped to exactly the client accounts they were booked for.

Viewer

Read-only across the accounts it is granted. A seat you can hand a stakeholder who needs to watch the numbers without touching the work — a strategist, a founder, a partner at the client who is not the approver.

The rate governor, the catch-up cap and the rest of the scheduling constants — and why each is the number it is — live on the publishing page. If your team is more in-house than agency, the governance case is laid out for in-house social teams instead.

Who it’s for

However your agency is shaped.

From a two-person studio to a white-label reseller, the same per-account separation holds — and you never pay for seats you don’t use.

Full-service agency

Fifteen clients, one login

Each client is its own brand with its own queue, inbox and report. An account lead runs several at once without a single client’s work ever bleeding into another’s.

Freelance collective

Contractors, scoped tight

Book a freelancer for one launch and give them exactly that client’s accounts. They never see the roster, the other inboxes or the other analytics — and a revoked token stops only their stream.

In-house + agency

Shared sign-off

Route every post through client_review so the brand’s own team approves before anything ships, with the approval recorded as a timestamped event rather than a Slack thread.

White-label reseller

Your brand on the report

Hand clients a report that compares reach by rate and traces a click to a named lead — under your identity, not Bloom’s, so the retainer renews on revenue.

Before you connect anything

Safe at agency scale, stated up front.

The risk that scales with an agency is not effort, it is suspension. Bloom’s limits are scoped to the thing a platform actually polices — the account — and named before you connect one.

The governor is per account

maxPerDay and minIntervalMinutes apply to each connected account, never to a shared platform budget, so eleven accounts on one network never spend each other’s allowance and a busy client cannot throttle a quiet one.

Recovery is gradual by design

After an outage Bloom releases at most ten catch-up posts per five-minute tick — a backlog drains, it does not dump — and a post more than 24 hours past its slot is skipped rather than published late under a client’s name.

Reach only where it is reported

Engagement reads back from ten of the eighteen networks; the other eight carry a stated reason rather than an implied zero. A white-label report never shows a client a number Bloom could not actually measure.

06 · Questions

Agency questions, answered plainly.

How does Bloom keep one client's work from leaking into another's?

A Bloom organisation holds brands, a brand holds connected accounts, and a member's access is granted per connected account rather than per workspace. A freelancer booked for one client is given the accounts that belong to that client and nothing else, so they never see another client's inbox, queue or analytics. The weekly queue is keyed to the brand, so two clients never share a schedule by accident.

Can a client approve posts without being able to publish?

Yes. The approval chain has four states — draft, internal_review, client_review and approved — and client_review is a recorded step a client seat moves a post through. A client can be given one of five roles checked against eight distinct actions, so a client seat can review and sign off without ever holding the publish button or being able to change the schedule.

Can I show a client which post produced a lead?

Yes, through Bloom's own short links. Each link is an eight-character code that carries per-platform UTM parameters automatically, classifies every click as bot, mobile or desktop, and follows the click through to a conversion and a named lead. A white-label report shows the client the posts, the clicks and the leads under your brand rather than Bloom's, so the conversation is about revenue rather than impressions.

Is it safe to run eleven accounts on the same network?

Yes. The rate governor sits in front of each connected account with its own maxPerDay ceiling and minIntervalMinutes gap, so eleven Instagram accounts never share one budget and a busy client cannot spend a quieter client's allowance. After an outage Bloom releases at most ten catch-up posts per five-minute tick, because dumping a backlog in one burst is the pattern platforms suspend accounts for.

Does scaling to more clients add a per-seat AI charge?

No. AI drafting is bring-your-own-key: Bloom supports Groq, OpenAI, Anthropic Claude and Ollama, verifies the key before saving it, and returns a 409 if no key is set rather than producing nothing silently. You pay your model provider directly, so adding a fifteenth client does not add a per-seat AI surcharge to a Bloom plan.

Which networks can an agency actually publish to?

All eighteen: Instagram, Facebook Pages, Threads, LinkedIn, X, Pinterest, YouTube Shorts, Reddit, Telegram, Tumblr, dev.to, Mastodon, Bluesky, Nostr, Lemmy, Mbin, Misskey and Plurk. There is no connect-only tier — every one of the eighteen has a real publisher. Engagement reads back from ten of them and conversations arrive from seven; the networks page carries the full table.

Give every client their own clean brand.

Bloom runs on its own application and its own sign-in — an Autocloz account is not required. Create your first client brand, scope a seat to its accounts, and send the first post through client_review today.