Products
CoJourno
Gambit 2
Automated Social Publishing
From air to social in minutes,
not hours.
After a package airs, someone watches it again, writes a title, writes a description, picks a thumbnail, posts to each platform. CoJourno's social publishing Gambit does that for you - in your editorial tone, with the level of human oversight you choose.
What this Gambit does
The social publishing Gambit watches the content, and generates the publishing artefacts - title, description, tags, thumbnail - using AI that has been tuned to your editorial tone, not a generic content model.
Title generation reads the package, the rundown, the script if one exists, and the metadata. It produces a headline in your voice - neither tabloid nor flat, calibrated to the conventions your social audience expects from you. Description follows the same logic, written for the platform it's destined for.
Thumbnail generation either selects the strongest still from the package using face detection and composition heuristics, or generates one based on a visual template you've configured. You decide which.
Then the Gambit publishes - to the platforms you've connected, with the format conventions each platform wants, accompanied by the 9:16 reframed output if Intelligent Vertical Reframing Gambit is running.
​
You set the level of automation. Full automation: the package goes to social without further human intervention. Approval mode: the artefacts are generated and queued, a human reviews and approves with one click, and then it goes out. We've configured this both ways in different newsrooms - the right answer depends on your editorial comfort level, not on what the technology can support.
The hour after every package
Your reporter has built the package. The producer has reviewed it. The bulletin has aired. And then a separate piece of work begins: writing a title that captures the story, writing a description that doesn't read as auto-generated, selecting or generating a thumbnail, and publishing to each social platform with the right specifications.
For every piece of content. Every day.
In some newsrooms, this is a dedicated social desk. In others, it's the journalist herself, doing the work after she's already finished her shift. Either way, the cost is the same: an hour or more per piece of content, repeated across dozens of packages a day, all of it work that doesn't require human judgment except in the smallest moments.
The story is already built. The publishing is just paperwork.
Where it sits
The publishing Gambit chains together with the rest of your post-production flow. It triggers on the same MAM/NRCS events that mark a package complete and ready for distribution. It connects to your social platforms via API and uses your existing editorial accounts, not new ones. If Gambit 01 is also running, the reframed 9:16 output is picked up automatically. If not, the original is used.
What changes
The journalist's story goes from air to social in minutes, not hours. The social team is freed up for the editorial and strategic work that actually requires human judgment - covering breaking stories, managing community responses, planning campaigns. And the consistency of voice across your social output stops depending on which person was on shift when the package was published.
built by