Mission Control

Rail accounts, credentials and channels

Publishing resolves channel to rail account to credential, so nothing in the job layer knows about the split. There is deliberately no failover between accounts: a dead key alerts rather than retrying through an account holding a different channel set.

Rail accounts

Buffer caps channels per account, so a product with three people across LinkedIn and X needs two. Capacity is tracked here and warned on before it is exceeded.

Futurebits Buffer ABuffer

3 of 3 channels used — at capacity

Holds the founder's LinkedIn member account, the founder's X account and the brand LinkedIn page. Keep one email identity per Buffer account and record it on the credential.

unconfigured

Buffer API key for this account, from Settings → Developers. Keep one email identity per Buffer account and record it below.

Which login this vendor account sits under. Worth recording when juggling several.

The daily job alerts seven days before this date.

Futurebits Buffer BBuffer

1 of 2 channels used

A second account because Buffer caps channels per account and the first one is full. This is the juggling the model exists to make visible: the delivery lead's LinkedIn lives here, on its own email identity and its own quota.

unconfigured

Buffer API key for this account, from Settings → Developers. Keep one email identity per Buffer account and record it below.

Which login this vendor account sits under. Worth recording when juggling several.

The daily job alerts seven days before this date.

Futurebits Cal.comCal.com

No channel cap on this account

Booking rail. The webhook that closes the attribution loop points at this account.

unconfigured

Cal.com API key, from Settings → Developer → API keys.

Which login this vendor account sits under. Worth recording when juggling several.

The daily job alerts seven days before this date.

Futurebits GA4GA4

No channel cap on this account

Nightly traffic snapshots. Share the GA4 property with the service account.

unconfigured

The full Google service-account JSON key file, with the GA4 property shared to that service account.

Which login this vendor account sits under. Worth recording when juggling several.

The daily job alerts seven days before this date.

Futurebits Search ConsoleSearch Console

No channel cap on this account

Query snapshots that feed the opportunity finder.

unconfigured

The full Google service-account JSON key file, with the property shared to that service account.

Which login this vendor account sits under. Worth recording when juggling several.

The daily job alerts seven days before this date.

How many channels this plan allows. Zero means no cap to track.

Credential health

Several rail accounts per brand means several keys on different expiry clocks. The daily job alerts seven days before any of these expire.

No credentials stored for this brand

Nothing here is broken — no key has been added yet. Paste one against a rail account above, or add a standalone key for a vendor without an account, such as the Telegram bot or a Cal.com webhook.

Sending identities

A mailbox channel is an SES from-address on one of these. Nothing can send until DKIM verifies and the ramp is started by hand.

hello@go.futurebits.tech

go.futurebits.tech · configuration set mission-control-futurebits · daily cap 60

DKIM: verified
SPF: aligned
DMARC: p=none
Ramp: day 1 · 14 day schedule

Day 1 of 14 of the ramp: 5 sends allowed today.

Deliberately not futurebits.tech: cold-email complaints must not touch the reputation of the domain carrying client correspondence. Verify DKIM, publish SPF and DMARC, point the MX at SES for inbound reply detection, then start the ramp. Nothing sends until warmup_started_on is set.

Channel inventory

Rows are people plus the brand-owned surfaces, columns are networks. Each cell says which account holds that channel and how much capacity is left on it.
VoiceLinkedIn (member)YouTubeXLinkedIn (page)BlogMailboxNewsletterCommunity

Example Delivery Lead

Delivery Lead

Delivery lead LinkedIn

Active · p2 · Futurebits Buffer B · 1 slot left

———————

Example Founder

Founder

Founder LinkedIn

Active · p1 · Futurebits Buffer A · 0 slots left

account at capacity

—

Founder X

Active · p2 · Futurebits Buffer A · 0 slots left

account at capacity

——

Outreach mailbox

Warming up · p1 · no account

——

Brand-owned

pages, listings and shared surfaces

—

Flow teardowns on YouTube

Active · p3 · posted by hand

—

Futurebits company page

Active · p3 · Futurebits Buffer A · 0 slots left

account at capacity

futurebits.tech/blog

Active · p1 · posted by hand

—

Substack newsletter

Active · p2 · posted by hand

UAE founder groups and product Slacks

Active · p2 · posted by hand

Manual channels

No publish job ever dispatches these — a human posts them. They exist so touches can be logged against them and attribution stays whole, and the social flow shows them as to-dos rather than queue items.

  • Flow teardowns on YouTube

    YouTube · priority 3 · Active

    Likely the highest-converting asset later, once call recordings give you material. Deferred, not dismissed.

  • futurebits.tech/blog

    Blog · priority 1 · Active

    The proof surface: teardowns and case studies. Published by hand, tracked here.

  • Substack newsletter

    Newsletter · priority 2 · Active

    Substack has no documented publish endpoint, so this is prep-and-paste.

  • UAE founder groups and product Slacks

    Community · priority 2 · Active

    Posted by hand. Mint the link through /r/<slug> anyway, or the funnel cannot see it.

Jump to

Search brands, flows, people and control panel sections