Newsrooms have a particular relationship with social media. The social channels matter, sometimes more than the website for breaking news, and the audience expectation is fast. Fast in a way that almost no other category has to deal with. A forty-minute delay on Twitter for a breaking story is the difference between a story that gets traction and a story that dies on the wire.
For most of the last decade, the answer was a dedicated social desk. Two or three people, watching the wire, rewriting items for each platform, hitting publish. When budgets tightened in 2024 and 2025, the social desk was one of the first things to go in many regional newsrooms. The channels stayed, the staff to run them did not.
This post is about one of those newsrooms. A regional daily in northern France, about 80 editorial staff before the cuts, 60 after. They lost their two-person social desk in the restructuring. They came to us a month later because the channels were dying and the editor-in-chief refused to watch that happen.
What they wired up
The setup took two weeks of part-time work from one of their editors. Three pieces:
- Wire ingestion: bbuddy reads two feeds. The internal CMS publishing queue (newest articles, every minute) and the AFP wire (national plus the regional desk's subscription bundle). Both come in as RSS.
- Voice profile: bbuddy reads the masthead, the last 18 months of social posts, and a style guide the editor-in-chief had already written. The voice profile says, essentially: present-tense, no editorialising, source named, no clickbait.
- Per-platform format rules: a 280-character X post that leads with the news and links to the article. A 1,000-1,300-character LinkedIn post with a one-sentence analytical angle. An Instagram caption only when there is a visual element worth surfacing.
The flow
Today, the newsroom's social flow looks like this:
- An article is published in the CMS. Within 30 seconds, bbuddy has read it and drafted the X and LinkedIn versions.
- Both drafts land in the editor's queue. The editor on duty taps Approve, or edits, or kills. Default is Review mode. No auto-publish.
- A typical approval cycle is 20 to 40 seconds. Total time from article publish to live social post is under a minute for routine items.
- For breaking news from the wire, the editor can flip a channel into Auto mode and let bbuddy publish immediately. Drafts still land in the queue beforehand, so an editor can intercept and edit on the way through.
The editor on duty is not "the social person" any more. It is whichever desk editor is on shift. Social became one extra item in the existing review cycle, taking maybe ten minutes of attention per editor per shift.
What still requires human judgment
Three categories of decision that bbuddy never makes alone in this newsroom:
- Sensitive stories: identifiable victims, ongoing legal matters, anything covered by reporting embargoes. The wire feed has a tag system that routes these into a separate "do not draft" bucket.
- Threading: when a developing story needs a sequence of related posts, an editor builds the thread structure. bbuddy fills in the individual posts.
- Replies and corrections: any reply, correction, or community management decision goes through a human. Always.
The wider lesson
The pre-cut social desk had two strengths: editorial judgment and speed. They lost the staff that gave them both, then recovered the speed through automation while preserving editorial judgment by keeping the editor in the loop.
For newsrooms staring at a similar restructuring, the question is not "can AI replace the social desk". It cannot replace the judgment part. The question is "can we automate the speed part while keeping the judgment in the existing editorial rhythm". For this newsroom, the answer turned out to be yes.