Internal Comms & Meetings

How to draft a slack announcement as Event Agency Founders

Internal Comms & MeetingsFor Event Agency Founders3 apps12 steps~24 min to set up

You're running a 4-person agency and Slack announcements fall through the cracks constantly. After a venue change, a vendor swap, or a day-of timeline shift, you're typing the same update three different ways — one Slack message for the internal team, a different tone for the client-facing channel, a third version for your contract staff group. There's no draft saved anywhere. You're writing these from memory at 10pm before a Saturday event. If you miss a channel or misphrasing something, a coordinator shows up to the wrong load-in time. The work isn't hard — it's just happening at the worst possible moment, with zero system behind it.

Build this on Starch → See the apps used

Internal Comms & MeetingsFor Event Agency Founders3 apps12 steps~24 min to set up

Outcome

What you'll set up

A Starch app that drafts Slack announcements from your meeting notes and event data — you review and send, no blank-page writing

Separate announcement drafts per audience (internal ops crew, client stakeholder channel, contract staff) pulled from the same source of truth

An automated trigger that fires a draft the moment a meeting ends or a key detail changes in your event timeline

The Starch recipe

Apps, data, and prompts

The combination of Starch apps, the data sources they pull from, and the prompts you use to drive them.

Apps used

Meeting Notes Email Agent Knowledge Management

Data sources & config

Meeting Notes connects directly to Google Calendar (Starch syncs your Google Calendar data on a schedule) to detect which meetings just ended and trigger a draft. Gmail is synced on a schedule so Starch can read vendor email threads and extract changed details. Your Notion runbooks and announcement templates are synced on a schedule from Notion into Knowledge Management so the drafts match your agency's voice and format. Slack is connected from Starch's integration catalog; the agent queries it live when posting or pre-filling a draft for your review.

Prompts to copy

After every client-facing or internal ops meeting, draft a Slack announcement for the #event-ops channel summarizing any venue, vendor, or schedule changes decided in the call. Use the meeting summary as source. Write in plain, direct language — no fluff. Flag anything that affects day-of logistics.

When a vendor confirms or changes a detail over email, draft a Slack message for the relevant event channel. Pull the vendor name, service type, and updated detail from the email thread. Keep it under 100 words.

Store our standard announcement templates — load-in schedule changes, catering headcount updates, AV call times — in Knowledge Management so Starch can pull the right format when drafting.

Run these in Starch → or paste them into your favorite agent

Walkthrough

Step-by-step

1 Connect Google Calendar — Starch syncs your calendar on a schedule. Tag which calendars contain client or ops meetings so Starch knows which calls should trigger an announcement draft.

2 Connect Gmail — Starch syncs your Gmail on a schedule. Point it at the labels or threads where vendor confirmations and change notices land (e.g., your 'Vendors - Active' label).

3 Connect Slack from Starch's integration catalog. Map your channels: one for internal ops crew, one per active event client, one for contract staff. Starch queries Slack live when it needs to send or stage a draft.

4 Set up Meeting Notes with the prompt: 'After any meeting tagged [event name], extract all decisions affecting vendor logistics, venue details, or day-of schedule. Draft a Slack announcement for #event-ops and a separate version for the client channel, noting the different tones.'

5 Add your announcement templates to Knowledge Management — load-in change notice, catering headcount update, AV call-time alert. Connect your Notion docs; Starch syncs Notion on a schedule so the templates stay current.

6 Build a Starch automation: 'When a meeting on my Google Calendar ends and Meeting Notes detects a schedule or vendor change, draft a Slack announcement, route it to my review queue, and tag it with the event name.'

7 Build a second automation for email-triggered announcements: 'When Gmail receives an email from a confirmed vendor contact that contains the words confirmed, updated, or change, extract the key detail and draft a Slack message for the relevant event channel. Hold it for my approval before sending.'

8 Test with a real event in flight. After your next ops call, check the draft Starch queues — verify the venue name, load-in time, and assigned coordinator are pulled correctly from the meeting notes.

9 Add a review step: each draft lands in your Starch inbox with a one-click approve-and-send button. You read it, edit the one thing that's slightly off, and post. Total time: under 90 seconds.

10 Set up a recurring Friday automation: 'Every Friday at 4pm, pull all event changes logged this week in meeting notes and vendor emails, and draft a weekend-readiness Slack summary for the internal ops channel covering any events in the next 72 hours.'

11 Once the workflow is stable, share the Starch app with your lead coordinator so they can trigger announcement drafts from their own meeting notes — you get notified for approval but stop being the only one who can write these.

12 Publish the announcement template set to your team's shared Knowledge Management space so every coordinator is pulling from the same formats, and Starch's drafts stay consistent across events.

See this running on Starch

Connect your tools, describe what you want, and the agent builds it. Closed beta is free.

Try it on Starch →

Worked example

Willow & Stone Corporate Gala — October 2025 Venue Change

Sample numbers from a real run

Original venue: The Meridian Ballroom, load-in 3pm	0
New venue: Harbor Pavilion East, load-in 1pm	0
Affected staff: 2 coordinators, 4 contract AV crew, 1 catering captain	7
Channels to notify: #gala-ops, #client-willow-stone, #contract-staff-oct18	3
Time to draft all 3 announcements manually (previous approach): ~35 min at 9pm night before	35
Time to review and approve Starch drafts: ~4 min	4

Your venue contact emails you Thursday afternoon that the Meridian Ballroom has a water issue and the event is moving to Harbor Pavilion East — load-in moves from 3pm to 1pm. Previously you'd write three separate Slack messages that night, probably from your phone, hoping you said the same thing in each. This time: Starch catches the email from the venue contact (Gmail synced on a schedule), detects 'venue change' and 'updated load-in time,' and queues three drafts within minutes — one for #gala-ops with logistics detail, one for #client-willow-stone in a calmer, reassuring tone, and one for #contract-staff-oct18 with just the new address and call time. You open Starch, read all three in 4 minutes, fix the parking note in the contract staff version because Harbor Pavilion has a different lot, and approve. All three post. Your coordinator wakes up Friday morning with the right information. No one shows up to the wrong building.

Measurement

How you'll know it's working

Time between a change decision and team notification (target: under 30 minutes for any day-of-critical update)

Number of day-of miscommunications traced to missed or incorrect announcements per quarter

Coordinator hours spent reconfirming logistics because the original announcement was unclear or late

Announcements sent without founder review (as agency grows and you delegate approval to lead coordinator)

Unanswered vendor change emails that should have triggered a team notification (catch rate)

Comparison

What this replaces

The other ways teams handle this today, and how the Starch version compares.

Writing Slack messages manually from memory

Zero cost, but happens at the worst time — late at night, from your phone, often incomplete — and there's no audit trail of what was communicated and when.

Notion + copy-paste to Slack

Keeps templates in one place but still requires you to manually pull details, fill in the template, and copy it to the right channels — no automation, no trigger from email or meeting notes.

Zapier + Slack + Gmail

Can automate email-to-Slack triggers but requires you to predefine exact rules and message formats; no AI draft that reads the email content and adapts the announcement to three different audience tones.

HoneyBook or Dubsado internal notes

Good for client-facing communication history inside those platforms, but neither routes updates to your Slack ops channels or generates audience-specific drafts for internal vs. contract staff.

A VA for communications

A trained VA can handle this well, but at $20-40/hr and only available during business hours — a venue change at 4pm Thursday still falls back to you.

On Starch RECOMMENDED

One platform — meeting notes, email agent, knowledge management all running on connected data. Setup in plain English; numbers stay current via scheduled syncs and live agent queries.

Try it on Starch →

FAQ

Frequently asked questions

Does Starch actually post to Slack, or does it just draft?

Both options exist. You can set it to hold every draft for your one-click approval (recommended when you're starting out), or once you trust the output for a specific trigger type — like a routine load-in reminder — you can let it post automatically. You control which automations are auto-send vs. review-first.

My Slack has channels for each event — can Starch figure out which channel to post to?

Yes, if you tell it how your channels are named. Give Starch a description like 'channels for active events follow the pattern #client-[lastname]-[month]' and it will route drafts to the right one. If it can't match confidently, it flags it for you to pick before sending.

What if the vendor email doesn't have obvious keywords like 'change' or 'update'?

Starch reads the full email content, not just keywords. If a caterer writes 'we'll need to arrive closer to noon instead' without using the word 'change,' the agent will still catch the schedule shift. That said, you should review drafts for the first few weeks on any new vendor relationship to make sure the extraction is reading those threads correctly.

I use HoneyBook to manage client communication — does Starch connect to it?

HoneyBook is reachable through Starch's browser automation — no API needed. For the Slack announcement workflow specifically, the trigger usually comes from Gmail (vendor emails) or Google Calendar (meeting notes), so HoneyBook doesn't need to be in the loop unless you want to pull contract or timeline data directly from it into the announcement.

Is my client's event data sitting in Starch's database?

Your Gmail and Google Calendar data sync on a schedule into Starch to power the automations. Starch is not SOC 2 Type II certified today, so if your clients are enterprise accounts with strict data compliance requirements, that's worth checking before connecting. For most independent agency use — corporate galas, brand activations, nonprofit events — this hasn't been a blocker for the founders using it.

Can I draft announcements for platforms other than Slack — like a group text or a WhatsApp group for contract staff?

Starch can draft the message content for any channel. For WhatsApp, it would automate through your browser — no API needed — to post or pre-fill a message. Group SMS depends on your provider; if it's web-accessible, browser automation handles it. The draft itself is the same either way — you'd just configure which channel gets which version.