Social MediaComposer

Composer

The composer writes posts for one event, from that event’s published website, and puts them in front of you before anything is queued. Approved posts join the autopilot queue; nothing else does.

Open the event → SocialCompose.

What it writes from

Everything is generated from your published website content. Nothing is invented. You choose a source:

SourceWrites about
Event announcementThe event itself.
CountdownTime remaining until the event.
A speakerOne speaker — pick them, or let the composer choose.
An agenda sessionOne session — pick it, or let the composer choose.
RegistrationRegistering to attend.
Your own briefA prompt you write.

A brief steers emphasis only — for example “emphasise the networking dinner on day two”. The facts still come from your published content, so a brief cannot introduce a speaker or a date that isn’t on your page.

Platforms and languages

Pick the platforms to write for; any platform without a connected account is marked not connected. English and Arabic are generated separately and post as separate updates — they are not two halves of one post.

Generation is rate-limited per day, and the button shows how many runs you have left.

Reviewing

Each generated post appears as a card with a preview and its character counter against that platform’s limit. On each one you can:

  • Edit the text and Save.
  • Regenerate it. If you have edited it, the button says so — regenerating replaces your edit.
  • Undo the last change.
  • Mark reviewed, which is what unlocks bulk approval.
  • Discard it.
  • Approve it.

Approve all requires every post in the run to be marked reviewed first. If any are not, the action is refused rather than silently approving unread copy.

Earlier runs stay available under Earlier runs, so generating a new set does not throw the previous one away.

The approval gate

Approving is the moment a post becomes real. It is checked against every switch between it and the platform, most global first — the same order the sender itself applies, so an approval cannot succeed on a post the sender would later refuse.

  1. The post is still ready. A post that was discarded, or reset for regeneration, cannot be approved from a stale tab.
  2. The workspace kill switch is released. ⚠️ A workspace with no kill-switch record at all counts as engaged, not as permitted — the absence of a permission is not a permission.
  3. The event has autopilot settings, and its own kill switch is released.
  4. Autopilot is enabled for that event.
  5. The platform is one this event posts to.
  6. An account resolves for that platform — the event’s bound account, or your default if it isn’t bound. Not “any connected account”.
  7. A free slot exists: within the event’s daily per-platform limit, outside quiet hours, and in the future.

If any check fails, the composer says which one — “Turn autopilot on for this event before approving posts”, “There is no free slot within the daily limit”, “That time falls inside quiet hours” — rather than failing generically.

When the workspace kill switch is engaged, the composer shows a banner at the top and refuses approvals outright, with a link straight to the switch.

After approval

An approved post is queued for a specific time and appears in:

  • the event’s Queue tab, and
  • the campaign calendar, where you can still edit its text, move it to another day, or pause it.

Approving does not send. The queued post sends when it comes due, and only if the switches still allow it then — engaging a kill switch after approval stops queued posts as they come due, with nothing to cancel by hand.

When the composer can’t start

You seeWhyFix
The composer writes with your own AI keyNo AI key configuredSet up a key (Spectrum and above)
No social account is connected yetNothing to post fromConnect an account
This event has no published websiteNothing to write fromPublish the website

If a single post fails to generate, that card says so and the rest of the run is unaffected — you can write that one yourself.