1.6 Slack Channel Setup and Naming Conventions

Why every client needs a Slack channel

Each client must have a dedicated Slack channel. The cycle planner, agenda, and recap automations post their outputs directly to the client's Slack channel by matching the meeting title to the channel name. If the channel doesn't exist or is named incorrectly, the automation posts to the wrong place or fails silently.

Channel naming standard

Use the client's name in lowercase with hyphens — no spaces, no special characters. Match as closely as possible to the client name used in HubSpot and in Fellow meeting titles. Examples: mtmc, bluegrass-paint-protection-film, axios-industrial, dialmycalls, peoplejoy

Meeting naming convention - critical for automations

All architect-client meetings must be named exactly: Customer Name / RevGravy - Bi-Weekly Meeting. This is what the cycle planner automation uses to identify which meetings should trigger a new cycle planner. If the meeting name doesn't match this pattern, no automation fires.

If a client renames their own meeting or uses a different format, ask the architect to update the meeting title. Example: 'Bi Weekly RevGravy' should become 'Visually.io / RevGravy- Bi-Weekly Meeting

When to create a new channel

• When a new possible client had his allingment call done. Invite Phil + Assigned  Architect

When to archive a channel

• When a client offboards — archive after the offboarding is complete (do not delete)
• When a channel is a duplicate or was replaced by another channel
• When a project channel (proj-*) has been inactive and decisions now happen elsewhere