For agencies
What Quillen does across client accounts
This is the specification, not the pitch. If you run social for other people you are evaluating limits, isolation, and who can publish what, so those are the things on this page, along with the ones we do not have. Every number below was read out of the shipping code on 1 September 2026.
For why an agency would want this at all rather than what it does, the agencies page is the shorter read.
10
Connected accounts
on Team, counted across all platforms together
5
Seats
included on Team, with owner, admin and member roles
Two step
approval
Member drafts, owner or admin signs off before anything publishes
The numbers, on Team
Team is the plan that matters for an agency, because seats, autopilot and two step approval only exist there.
| Capability | What it is | Where it applies |
|---|---|---|
| Connected accounts | 10 on Team, counted across all platforms together | Checked when you connect an account, not on a settings page |
| Seats | 5 included on Team, with owner, admin and member roles | Seat count is checked atomically as an invite is accepted |
| Approval queue | One queue for the whole workspace, filterable by campaign | A single inbox across every connected account |
| Voices | Several personas per workspace, one default per connected account | A campaign drafts with the persona assigned to that campaign |
| Two step approval | Member drafts, owner or admin signs off before anything publishes | Team only, off until an owner turns it on, and it disables autopilot |
| Per account pacing | A warm up ramp and a daily ceiling, both derived rather than typed in | The lower of the platform ceiling and your plan cap, then the ramp |
| Warm up gate | Cold replies blocked until 10 followers, 10 connections and 7 days | The first gate in the posting path, ahead of pacing and dedup |
| Deduplication | One reply per post per 30 days, and 3 replies per person per 14 days | Enforced across the whole workspace, not per account or per user |
| Engagement cooldown | 30 days before anyone you already engaged can be engaged again | One ledger row per person per platform, shared across the workspace |
| Autopilot | Optional, LinkedIn campaigns only, and never available on X | Team only, off unless you switch it on for a specific campaign |
| Export | Analytics charts and the credit usage ledger download as CSV | A download button on the analytics and usage pages |
The questions agencies ask
How many client accounts can I run?
Ten connected accounts on Team, and the important detail is that ten is the total across every platform rather than ten per platform. A client whose X and LinkedIn you both run therefore uses two of the ten. The cap is checked at the moment you connect an account, counting every connection in the workspace that has not been revoked.
Will two clients end up sounding the same?
Not if you assign each one a persona. A workspace holds as many personas as you build, each synthesized from that person own writing rather than from a shared tone preset, and every connected account carries the persona it composes with by default. The one thing to know: when a campaign is created it is assigned the first active persona in the workspace, so on a multi client workspace you should set the campaign persona deliberately rather than leaving the default.
Can my team draft without being able to publish?
Yes, that is what two step approval does. With it on, anything a member drafts goes to an owner or admin for final sign off, and autopilot is disabled entirely while it is on. It is Team only, an owner turns it on, and it is off until they do. Turning it back off does not release drafts already waiting for approval.
Can I set a different daily limit for each client account?
No, and we would rather say so than describe a field that does not exist. Per account throughput is derived, not typed in: each send is capped by the lower of the platform ceiling and your plan cap, then by a warm up ramp for a newly released account, then by a daily draw of 80 to 100 percent of that ceiling. What you do control per campaign is a daily cap on how many comments that campaign produces.
Does anything post to a client account without someone approving it?
By default no, on every plan and every platform. There is one exception and you have to switch it on: an optional autopilot for LinkedIn campaigns, Team only, off unless you enable it on a specific campaign, and only drafts that pass the voice lint are ever eligible for it. On X automatic posting is not available at all, and turning on two step approval disables autopilot everywhere.
Can two of my clients accidentally contact the same person?
No, and this cuts both ways so it is worth understanding. Deduplication and the engagement cooldown are scoped to the whole workspace rather than to an account or a user, so nobody gets replied to twice from two of your accounts. The other side of that: two clients in one workspace share a single do not contact list, so a prospect one client engaged is suppressed for the other.
What we do not claim
Things you might reasonably assume, and what is actually true.
- Ten accounts means ten per platform
- It does not. Ten is the total across every platform on Team, and the connect flow counts every unrevoked connection in the workspace regardless of which platform it is on. Five clients whose X and LinkedIn you both run is ten accounts, not five.
- You can set a budget per client account
- There is no such field. Per account throughput is derived at send time from the platform ceiling, your plan cap, the warm up ramp and a daily variation draw. The only number you set yourself is a per campaign daily comment cap. Anyone describing per account budgets in this product, including us in an earlier draft of this page, is describing something that does not exist.
- You can connect ten accounts from day one
- Not during a discounted intro month. While an org is on the ten dollar first month the connected account cap is forced to one on every plan, so the second client account has to wait for the first full billing period. Worth knowing before you plan a migration weekend around it.
- Each client is isolated from the others
- Only in voice, not in suppression or in billing. Personas and campaigns are per client, but deduplication, the engagement cooldown and the credit balance are workspace wide by design. If you need genuine isolation between clients, that is separate workspaces, and today that means separate subscriptions.
- There is white label or client facing reporting
- There is not. No branding configuration, no logo upload, no custom domain, and no generated client report. What exists is CSV export: every analytics chart and the credit usage ledger download as a file you can put into your own reporting. The filenames are ours.
- Analytics break down per client account
- They do not yet. Analytics are aggregated across the workspace and split by platform rather than by connected account, so a per client view has to be assembled from the CSV export. The accounts page does show warm up state and follower and connection counts per account.
- One composed post can go out from several client accounts at once
- It cannot. Cross posting produces one post per platform, and you choose which account on that platform it goes from. Posting the same thing from three client accounts is three actions.
- Impressions are available for every client
- On X yes, on LinkedIn no. Impressions come from the X API; the third party provider we use for LinkedIn does not expose them, so that column is empty for LinkedIn rather than estimated.
- There is agency or reseller billing
- There is not. One workspace is one subscription at a flat Team price, and there is nothing in the product that sells seats individually or invoices per client. If you need per client invoicing, you are doing that in your own billing.
- Everything runs on official platform APIs
- It does not, and we do not say it does. Posting to X uses the official X API. LinkedIn posting and replying run through a third party provider on a session API, and X discovery reads go through a third party aggregator. That distinction matters more when the account is a client account than when it is your own.