Billing

How connected accounts are counted

What counts as a social account, what does not, and what happens at your plan’s cap.

What counts

One connected social channel is one unique handle you have authorised DemandBird to publish to or read analytics from.

Counted, one each:

  • A LinkedIn personal profile
  • A LinkedIn Company Page — each page is its own channel, even if one login manages several
  • An X/Twitter profile
  • An Instagram account
  • A Facebook Page
  • A Threads account
  • A Bluesky account
  • A Mastodon account
  • A Substack publication
  • A YouTube channel

What does not count

None of these add to the number your bill is based on:

  • Team members. Free on every paid plan, up to the plan's cap.
  • Workspaces. Free, and unlimited on Business and Agency.
  • Client seats and review-only seats. They are team members.
  • API tokens and MCP clients. However many you create.
  • Your linked phone number for SMS or WhatsApp.
  • Reconnecting a channel you already had. Re-authorising after a token expiry is the same channel, not a new one.

How many you get

PlanMonthlyAnnual (per month)Channels includedOf those, X/TwitterMax channels
Pro$29$21.75515
Business$49$36.75103Unlimited
Agency$149$111.75205Unlimited

The X/Twitter column is a sub-limit, not a separate allowance. On Pro, 5 channels including at most 1 X/Twitter means: five channels total, and no more than one of them may be X/Twitter. X/Twitter costs us materially more to support per channel, which is why it is metered separately. See Add-ons for the rates past those numbers.

What happens at the cap

Pro is a hard cap at 5. Connecting a sixth channel is refused rather than billed. If you need more, move to Business.

Business and Agency have no ceiling. Connecting a channel past the included block adds it to your subscription at the per-channel rate, prorated for the remainder of the current period. You are told the price before the connection is confirmed.

Disconnecting a channel removes the charge from the next period.

Which workspace a channel lands in

On an account with more than one workspace, a newly connected channel belongs to the workspace you were in when you started the connect flow. It counts once against the account, not once per workspace.

A channel can only live in one workspace at a time. Re-authorising it from a different workspace moves it rather than duplicating it, and DemandBird asks you to confirm that move before doing it — so a mis-clicked reconnect cannot silently relocate a client's channel.

Counting is per account, not per workspace

An agency on one bill has one pool of channels across every client workspace. There are no per-workspace allowances to shuffle between, and no workspace can exhaust another's budget, because there is only the one.

The same is true of AI usage: the monthly caps are per account.

Seeing your current count

Settings → Billing shows the channels currently counted, split by type, with the rate applied to each. Settings → Connections is the list itself, including any channel whose authorisation has expired.

An expired channel still counts. It has not been disconnected — it needs re-authorising, and DemandBird keeps its history and its schedule waiting. Disconnect it if you genuinely want to stop paying for it.