Meeting Slip Alert — AI Meeting Change Alerts in Slack | Town
Meeting Slip Alert
Meeting Slip Alert is a routine your Townie AI assistant runs on every email to your shared inbox: it spots declines and reschedules, verifies against the calendar that a client meeting actually slipped, and posts an alert to that client's Slack channel. When the client-to-channel match isn't confident, you get a DM instead — so the team hears in seconds and nobody cries wolf.
To: your Townie
Subject: Create me a Meeting Slip Alert routine
Sent when you sign up — works as-is, or edit anything.
See it work: the team knows before you've read the email
Catch slipped client meetings in seconds, not hours
Watches the shared inbox for declines and reschedules, verifies the slip against the calendar, and alerts the right client channel in Slack.
Trigger
When email hits the shared inbox
Tools and actions
Spot declines and reschedules
Verify the meeting slipped
Post to the client channel
Prompt
On each shared-inbox email, spot a decline or reschedule, verify against the calendar that a client meeting really slipped, and alert that client's Slack channel once — DM me when the match is unsure.
🚨
Slip Alert — Northwind
Northwind kickoff just slipped
Your Townie
verified against the calendar and posted to #client-northwind two minutes after the email landed.
What slipped: 📅 Thursday's 10am kickoff
Dana Cho declined and asked to move to next week. The event is still on the calendar with 6 attendees — the alert names the event, who proposed the change, and the thread to answer.
Routing: ✅ matched to #client-northwind
Client matched by name with high confidence, so the channel was alerted directly. One earlier decline today was an internal standup — skipped, no noise.
How this routine works
Works with
- Gmail](/content/integrations/gmail/index.html)
- Google Calendar](/content/integrations/google_calendar/index.html)
- Slack](/content/integrations/workspace_slack/index.html)
- Outlook](/content/integrations/outlook/index.html)
- Calendly](/content/integrations/calendly/index.html)
- Zoom](/content/integrations/zoom/index.html)
- Telegram](/content/integrations/telegram/index.html)
- WhatsApp](/content/integrations/whatsapp/index.html)
- And more
- 1
It runs on every shared-inbox email
Declines and reschedules get spotted the moment they arrive. Internal and non-project meetings are skipped — only client-facing slips matter.
- 2
It verifies before it routes
The sender and subject are validated, and the calendar is checked to confirm the meeting actually slipped — stale or already-resolved changes never fire an alert.
- 3
The right people hear in seconds
The alert posts to that client's Slack channel, exactly once per email, naming the event and who proposed the change. When the match isn't confident, you get a DM instead.
Meeting Slip Alert FAQ
What does the Meeting Slip Alert routine do?
It's a routine your Townie AI assistant runs on every email to your shared inbox: it spots declines and reschedules, checks the calendar to confirm a client meeting actually slipped, and posts an alert to that client's Slack channel — with a DM to you as the fallback when the client-to-channel match isn't confident.
Can it post to Slack on its own? Is that safe?
The alert is internal-only, and it posts only after the slip is verified against the calendar — it never emails clients or changes any meeting. Access is scoped to the accounts you connect. Read more in our security overview.
Won't a busy shared inbox make this noisy?
That's what the verification is for. It fires exactly once per email, skips internal and non-project meetings, and ignores stale or already-resolved changes — so an alert means a real client slip, every time.
What tools does it need?
The shared email inbox it watches, the team calendar for verification, and Slack for the alerts. Your assistant adapts the routine to however your client channels are named.
What happens when it can't match the client to a channel?
You get a DM instead of a channel post, with everything it found — the event, the sender, and its best guess. Confirm the mapping once and it routes that client correctly from then on.