Slack, Gmail, GitHub, and Teams-friendly copy guide

Slack and Gmail workflows are available on Pro and Agency plans. Free accounts can still use the core generator, but connected delivery tools require an upgrade.

1. Open Settings in ClientCadence.
2. Select Connect Slack and approve the workspace install.
3. After Slack returns to Settings, the Slack card should show Connected.
4. If Slack permissions change later, reinstall the app to refresh access.

You can use ClientCadence in Slack three ways:

• Send a direct message to the ClientCadence app.
• Mention ClientCadence in a channel.
• Use the slash command /clientcadence.

Slack requests from a paid connected workspace are saved to History. When your message includes a project name or client name already saved in ClientCadence, the history item is attached to that project.

• help
• draft update [rough notes]
• follow up with [client or company]
• summarize [rough notes]
• risk
• status
• connect

Gmail access is send-only. ClientCadence sends only the approved message you choose from the output panel. It does not read, scan, import, or analyze your Gmail inbox.

1. Open Settings in ClientCadence.
2. Select Connect Gmail and approve send-only Gmail access.
3. Generate an update in the dashboard.
4. Select Gmail from the output panel, enter the recipient and subject, then send.

After Slack or Gmail is connected, generate a client update in the dashboard. The output panel shows Slack and Gmail buttons next to Copy. Slack sends to a selected public channel. Gmail sends the approved output as a plain text email from the connected Gmail account after you review the recipient, subject, and message.

GitHub is an activity context source, not a client sending channel. On Pro and Agency workspaces, ClientCadence can import selected pull requests, issues, commits, tags, and releases as draft context, and reply to explicit /clientcadence commands in GitHub conversations.

Use GitHub import when technical progress needs to become a client-ready update. ClientCadence helps separate completed work from released work, then you review the final draft before sending or copying it.

If your team uses Microsoft Teams, choose the Teams output format and copy the reviewed draft into Teams. This is a message format for copy/paste workflows. ClientCadence does not post directly to Microsoft Teams in this release.

Teams-friendly drafts are shorter than email, usually use compact bullets, and keep the next action visible for channel discussions.