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.
See it work: the team knows before you've read the email
Catch slipped client meetings in seconds, not hours
Gmail
Google Calendar
Slack
Outlook
Calendly
ZoomIt 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.
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.
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
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.
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.
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.
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.
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.
