A Channel You Cannot Schedule Is Not a Channel.

Most brands decide whether to add a channel by looking at the audience number.

It is the easiest fact to find and close to the least useful thing to know.

The question that actually predicts whether a channel survives is operational. Can it be planned, approved, scheduled, moderated and reported inside the system your team already runs, or does it need one person with the app open on their phone?

A channel that fails that test does not fail loudly. It gets added, it gets posted to keenly for a few weeks, and then it quietly becomes somebody’s side job and stops. Threads is the clearest example of a platform that failed the test for a long stretch and then passed it, which is why a lot of brands who said no were answering a different question than they thought.

The audience number is the wrong question

Threads has been reported at more than 400 million active users. That number tells you the ceiling of a channel, not whether your team can run one.

Plenty of enormous platforms are bad fits for a specific brand, and plenty of smaller ones are excellent. Audience size decides whether the opportunity is worth wanting. It says nothing about whether you can service it.

The fit question, who your buyers are and whether they are there, is a separate exercise and NBK works through it in should your brand be on Threads. The question that comes after it is the one that kills more channels, and almost nobody asks it before signing off.

The test a channel actually has to pass

Before you agree to add anything, run it through six questions. They take ten minutes and they are more predictive than any audience statistic.

• Can it be scheduled from the tool that already holds your content calendar?
• Can a draft pass through your approval step before it publishes, without someone screenshotting a phone?
• Does it have a named owner with the time in their week, not an implied one?
• Do replies and mentions arrive in the same inbox as every other channel?
• Do the numbers land in the same report as everything else, on the same cadence?
• Could a different person run it next month if the owner left?

Six yeses means the channel is a line in a system you already have. Four or fewer means you are proposing a second, informal system that runs on one person’s goodwill.

What a failed channel looks like six weeks in

The pattern is consistent enough to predict. Week one, the person who championed the channel posts daily and the posts are good, because they are writing natively and paying attention.

Week three, they are travelling, or in a launch, and the channel goes three days quiet. Nobody notices, because it is not on the calendar and not in the report.

Week six, someone asks how it is going and there is no answer, because the numbers live in an app rather than in the monthly deck. The channel is not dead, which is worse than dead. It sits there half-lit, with a brand handle nobody is moderating and replies nobody is reading.

That is not a content failure. It is an operations failure, and it was decided at the moment the channel was added without a seat in the system.

Threads spent its early life failing this test

For its first stretch, Threads was a channel you had to be present for. There was no way to put it in the same queue as everything else, so the only way to run it was to open the app.

The API opened to developers in June 2024, which let third-party tools publish posts, retrieve content and build reply management. Native scheduling followed in the app in January 2025, handling original posts through the composer with scheduled items sitting in the drafts folder.

Native scheduling is genuinely useful for one person running one account. It is not the same thing as your calendar. It cannot see the rest of your month, it cannot hold an approval, and it does not report anywhere your finance director will ever look.

What the API changes actually did

The interesting part is not any single feature. It is that a run of changes through late 2025 and early 2026 closed most of the gaps between what the app could do and what a tool could do on your behalf.

Meta’s own developer changelog dates them: spoiler support for text, image and video in October 2025, the profile discovery follower threshold dropping from 1,000 to 100 in November 2025, ghost posts in December 2025, GIF publishing through GIPHY in February 2026, creating posts with reply approvals and managing pending replies in February 2026, embedding public posts without an access token in March 2026, and cross-sharing posts to Instagram Stories in March 2026.

They arrived piecemeal rather than as one launch, which is why the shift is easy to miss. No single announcement said the channel had become operable, so most brands are still working from an impression formed when it was not.

Scheduling is the floor, not the finish

Scheduling is the capability everyone checks first and the one that proves least. It only means a post can be queued.

It is worth confirming your own stack covers it, because vendors move at different speeds and a channel your tool cannot publish to is a channel your process cannot hold. Buffer, Hootsuite and Sprout Social all state Threads publishing and scheduling on their own product pages, alongside Threads metrics.

Check yours rather than assuming. The rest of the test matters more, and almost nobody runs it.

Approvals are what makes a channel safe to delegate

Approval is the difference between a channel a junior can run and a channel only a director can touch. Without it, every post is either a bottleneck or a risk.

This is also where the Threads changes get more interesting than the posting ones. Reply approvals and pending reply management through the API mean the conversation under a post can be governed by the same process as the post itself, rather than by whoever happens to see the notification.

If your approval step exists in a chat thread and a set of screenshots, adding any channel makes it worse. That is a workflow problem, not a platform problem, and it is the sort of constraint we spend most of our time removing in workflow and ops consulting.

Replies have to land in the same inbox

A channel with unread replies is worse for a brand than no channel at all. It reads as a company that started something and lost interest.

So the moderation question is not “can we reply”, it is “will we see it”. If replies arrive in a separate app with separate notifications, they get answered when someone remembers.

Hootsuite says you can respond to Threads comments from its dashboard, and Sprout Social says Threads comments arrive in its Smart Inbox. That is the shape you want, whatever the tool: one place a person opens each morning, containing everything.

If it does not reach the report, it did not happen

Every channel that is not in the monthly report eventually loses its budget and its time, because nothing defends it when the quarter gets tight.

This is the quiet reason API access changes the commercial answer. Metrics that a tool can pull are metrics that land in the same report as your other channels, on the same cadence, compared on the same terms.

A channel measured by screenshots is measured by whoever takes the screenshots, and it will always look either better or worse than it is.

Someone has to own it by name

Every operational rule above collapses without an owner. Not a team, not a rota, a person whose name is against the channel and whose week contains the hours.

Give them a defined scope: how many posts, what the reply window is, who approves, what gets escalated. And give them a documented backup, because holiday is the most common cause of a channel going quiet.

If the honest answer is that nobody has the hours, the correct decision is not to add the channel. Two channels run properly beat five run occasionally, every time.

What good looks like

A well added channel is boring to describe, which is the point.

• It appears on the same content calendar as every other channel, planned in the same session.
• Its posts move through the same approval step, with the same people and the same turnaround.
• Its replies arrive in the shared inbox, with a stated response time.
• Its numbers are in the monthly report, next to the others, on the same definitions.
• One named person owns it, one named person covers them, and both know the escalation route.

Nothing there is about the platform. That is why the test travels to whatever launches next.

How NBK thinks about adding a channel

We treat a new channel as a change to the operating system, not an addition to the content plan. The first conversation is about capacity, approvals, ownership and reporting, and only then about what to post.

The reason is commercial. Organic growth compounds through consistency, and consistency is a property of the system rather than of anybody’s enthusiasm. A channel the system cannot carry will not be consistent, however good the first month looks.

That is also why the API question is worth taking seriously rather than treating as developer detail. A platform that third-party tools can drive is a platform your existing process can absorb without hiring anyone.

Next step

If you are weighing up a new channel, run the six questions before you look at the audience number again. The answers usually make the decision for you.

And if the honest blocker turns out to be your approval step rather than the platform, start there. Our free social media approval process template is a reasonable place to begin, and if your process is slowing down good ideas across every channel you already run, NBK can help rebuild the workflow behind the content.