Event promotion

Builds a three-phase plan for one event (before, during, after), gets the person's yes on exact times, then drafts, checks and schedules it. Every time is stated with its time zone, because an event is the one place a wrong offset breaks the whole plan.

Before you start

1. get_account: the person's time zone, AI drafts left, weekly cap, autonomy.
2. list_channels: networks, max_length, media rules, needs_reconnect, queue_paused. Pick the audience's home: LinkedIn for B2B events, Instagram and Facebook for consumer and local ones, Google Business for a store opening, X for live commentary.
3. list_personas: company voice for the event, a founder or speaker voice for personal posts.
4. list_posts with status: "scheduled" and from / to around the event: avoid colliding with other content.
5. suggest_posting_times on the main channel for the countdown slots.

Workflow

1. Collect the event facts in one message. Name, format (in person, online, hybrid), start and end date and time with the event's time zone, venue or join link, registration link and deadline, price or "free", capacity, speakers or agenda with their consent to be named, who it is for, the one reason to come. Missing items stay [placeholders].
2. Resolve time zones before anything else. If the event's zone differs from the person's zone in get_account, write both ("Thu 14:00 London, 09:00 New York") in the copy where the audience is mixed, and compute every scheduled_at in the person's zone with its offset. State the conversion in the plan so they can catch a mistake. Clock changes: check whether the date falls in a daylight saving shift week.
3. Draft the plan as a table (when, phase, channel, angle, media, AI draft or own text) and say how many AI drafts it uses. Default shape for a 3-week-lead event; shrink for shorter notice:

1. Get a yes, then write. create_draft for the person's own text, else generate_draft with an idea containing the angle and the concrete facts. Several channels in channel_ids for linked versions; tailor with per_channel. Speaker posts: one post per speaker, name and topic, a one-line reason to listen to them, a quote only if they gave it.
2. Visuals. Announce, speaker and recap posts want an image. attach_image with image_svg (clean card: event name, date with time zone, one line, 1200x627 or 1080x1080) or image_url of a real photo. Live and recap posts use real photos the person supplies at image_url; don't fabricate crowd scenes.
3. Check each post with check_post.
4. Schedule (schedule level and up): schedule_post with an ISO time and offset for every countdown and day-of post. The "during" and thank-you posts depend on the event happening, so schedule only the ones with fixed times (the 2-hours-before post); keep live moments and the thank-you as ready drafts and tell the person to approve them in ProPost on the day, or, with a publish connection, to say "go" so you can publish_now each after showing the text and channel and getting an explicit yes. At drafts level, stop after drafts.
5. Report: a timeline with conversions, and what's waiting (photos, speaker approvals, the live drafts).

Writing guidance

• Lead with the benefit to the attendee, then the logistics. "Learn how three clinics cut no-shows in half" beats "Join us for our webinar". (Only if that claim is the speaker's and true.)
• Every event post carries: what, when (with time zone), where or link, how to register. Someone seeing only that post should be able to act.
• Scarcity only if true: "12 seats left" needs the real number from the person. Otherwise use the deadline.
• Live posts are short and specific: one idea from a talk, attributed. "Maria Lopez: 'We stopped counting leads and started counting calls booked.'" is good only if she said it and agreed to be quoted.
• Recap = value, not victory lap: three concrete takeaways, a thank-you, the next step. Photos of attendees only with a general consent that was signalled at the event.
• Online event reminders include the join link, start time in two zones, and how long it runs.

Guardrails

• Never name or quote a speaker, sponsor or attendee who hasn't agreed.
• No attendance, satisfaction or ROI numbers the person didn't provide.
• Don't post a venue address of a private location, or a join link for an event that must stay invite-only, on public channels.
• Don't publish_now live moments on your own initiative.
• If the event is cancelled or moved: list_posts with status: "scheduled", unschedule_post the affected ones, then fix and reschedule. For the message itself see propost-sensitive-announcements.

If something fails

• time_in_past: the beat is already past; drop it or move it.
• time_too_far: more than a year ahead; hold the posts as drafts.
• weekly_limit: schedule the countdown and day-of posts first; keep the rest as drafts.
• image_required: attach an image, then retry.
• too_long: shorten with rewrite_post or update_post.
• Anything else: see ../CONVENTIONS.md.