The Problem With Team Scheduling
When five reps share one booking page, two things tend to go wrong: the rep who gets assigned does not find out fast enough, and the manager has no easy way to see what the whole team booked that day. Meetario solves both with a combination of round-robin assignment and Slack notifications — but only if you set the channels up correctly.
How Round Robin and Slack Work Together
A round robin event type in Meetario distributes incoming bookings across your team based on availability and rotation rules. Whoever gets assigned as the host for a given booking is the one who receives the Slack notification — Meetario sends the new booking message to the assigned host's connected Slack channel, not to every team member. This means the notification always reaches the person who actually owns that meeting, without anyone needing to check a shared inbox.
For this to work, every rep on the round-robin rotation needs their own Slack connection. If a rep has not connected Slack under their Meetario login, they simply will not get notified when they are assigned — the booking still happens, but the alert never fires for them.
Channel-Per-Rep Setup
Because the channel is chosen individually during each person's Slack authorization (see our guide on setting up Slack booking notifications), you have flexibility in how you structure this:
- Personal channels — Each rep connects and picks their own private or personal channel, so only they see their assignments.
- Shared team channel — Every rep authorizes into the same
#team-bookingschannel, so the whole team sees every assignment as it happens, creating natural peer visibility. - Hybrid — Reps use personal channels for their own alerts, while a separate custom webhook (see our guide on scheduling automation) posts a copy of every booking to a shared channel for management visibility.
Most sales teams land on the hybrid approach: personal notifications keep individual reps focused, while the shared feed gives leadership a live view of pipeline activity without pinging everyone for every booking.
Team-Wide Visibility for Managers
Because the native Slack integration only notifies the assigned host, managers who want to see everything the team books need a second channel. Set this up with a custom webhook under Account → Webhooks, filtered to the booking.created event across your round-robin event type, routed through Zapier or Make.com into a shared management channel. This gives you a running feed of every booking regardless of who was assigned, which is useful for spotting volume trends or coverage gaps in real time.
Setting Up a Team Workflow Step by Step
- Create a round-robin event type under Event Types → New Event Type and add each team member as a host.
- Have every team member individually connect Slack under Account → Integrations, choosing either a personal or shared channel.
- Optionally create a management-level webhook routed to a shared channel for full-team visibility.
- Test by booking several slots back-to-back and confirming assignments rotate correctly and notifications land in the right places.
- Review the assignment logic under the event type's Round Robin settings if any rep seems to be getting more or fewer bookings than expected.
Common Pitfalls
- Assuming one Slack connection covers the team — It does not. Each rep must connect individually, even though they share one Slack workspace.
- No shared visibility channel — Without one, managers have to check the Meetario dashboard manually to see team-wide activity.
- Forgetting to test rotation — Book a handful of test slots after setup to confirm round robin is actually distributing bookings evenly before rolling it out to real prospects.
Troubleshooting Team Notifications
A team member is not receiving notifications
The most common cause is that the team member has not connected their own Slack account under Account -> Integrations. Each person on the round-robin rotation must authorize Slack individually — there is no way for an admin to connect Slack on behalf of another user. Have the team member log in to their Meetario account, go to Integrations, and complete the Slack OAuth flow. If they have already connected but still see nothing, ask them to check which channel they selected during authorization — the notification may be landing in an unexpected channel.
Notifications are going to the wrong channel
The destination channel is locked in during the Slack authorization step and cannot be changed afterward without reconnecting. To switch channels, the team member needs to disconnect Slack under Account -> Integrations, then reconnect and choose the correct channel during the new authorization prompt. This takes under a minute and does not affect any existing bookings or calendar sync settings.
Duplicate notifications for round-robin bookings
If both a personal notification and a webhook-driven management channel post appear for the same booking, that is expected behavior in a hybrid setup — one message goes to the assigned host's personal channel, and the webhook fires separately to the shared channel. If you are seeing true duplicates in the same channel, check whether the team member accidentally authorized Slack twice or whether multiple webhooks are targeting the same channel. Review active webhooks under Account -> Webhooks and deactivate any redundant ones.
How do I audit notification delivery?
For built-in Slack notifications, the quickest audit method is to book a test slot and confirm the message arrives. For webhook-driven notifications, Meetario logs every delivery attempt under the webhook's Deliveries tab, including HTTP status codes, timestamps, and response bodies. If you need a historical audit trail of all team notifications, consider routing webhooks through Zapier or Make.com with logging enabled so you have a permanent record outside of Slack's message retention limits.
Quick Start
If you are rolling this out to a sales or support team, start by connecting Slack for every rep individually, then decide whether you need a shared management channel on top. Once notifications are flowing correctly, our guide on Slack vs email notifications is worth reading to understand exactly how much faster your team can respond to new leads. For details on how round-robin assignment logic works, see our round-robin scheduling guide.