Browse the docs
Documentation

Slack

Post completed meeting summaries to the Slack channels you choose, and to yourself as a direct message.

Slack integration posts a meeting's summary to the Slack channels you choose when the meeting finishes processing. Each member can also get their own meetings as a direct message. Only an Owner or Admin can connect Slack and manage which meetings go to which channel.

Everyone in a channel sees the summaries posted there, including people who can't open the meeting in VoiceCap. Choose channels with that in mind. A route only ever posts meetings that the Owner or Admin who set it up can open in VoiceCap.

Connecting Slack

  1. Go to Settings > Integrations.
  2. Find the Slack card and click Connect Slack.
  3. Pick the Slack workspace and click Allow. You're sent back to Settings > Integrations with a "Slack connected." confirmation.

The card then shows the connected workspace, for example "Connected to acme.slack.com".

Install VoiceCap into a single Slack workspace. Installing it for a whole Enterprise organization isn't supported, and you see "Install VoiceCap into a single workspace, not a whole Enterprise organization." if you try.

A Slack workspace can be connected to one VoiceCap organization at a time. If it's already connected to another one, you see "That account is already connected to another VoiceCap organization. Disconnect it there first."

Channel routes

A channel route says which meetings are posted to which channel. Under the Slack card, click Add channel route, pick a channel and set the filters. The route posts the meetings that match these filters and that you can open in VoiceCap yourself, so it never shows a channel more than you can see:

  • Whose meetings: All members, or Selected members to post only the meetings of the people you pick.
  • Meeting type: Any meeting, External meetings or Internal meetings. A meeting is external when at least one calendar attendee's email is outside your organization's domains. Meetings without calendar attendees (uploads and pasted meeting links) only match Any meeting.
  • Groups (optional): only meetings filed into one of the groups you pick.
  • Participant domain (optional): only meetings with a calendar attendee on that domain or one of its subdomains. Adding acme.com also matches eu.acme.com. Meetings without calendar attendees never match a domain.

Every filter you set must match. Within one filter, any of its values is enough: a route with two groups posts meetings filed into either of them.

While you edit, the editor shows how many of the last 20 completed meetings you can open the route would have matched. It shows a count only, never meeting titles.

The channel list shows public channels and the private channels VoiceCap has been added to. To post to a private channel, invite @VoiceCap to it in Slack first, then click Refresh in the editor.

If two routes post the same meeting to one channel, the channel gets the message once. An organization can have up to 50 channel routes.

Whoever saves a route last owns it: from then on it posts the meetings that person can open. If the route's owner leaves the organization or is no longer an Owner or Admin, the route stops posting and shows "The admin who set up this route is no longer an owner or admin here. Save the route again to take it over." Another Owner or Admin can open it with Edit and save it to take it over, or delete it. Send test message doesn't restart such a route.

A stopped route still counts for what its channel gets: if it's set to Brief, the channel keeps getting the brief message from the other routes on it.

Full or brief

Each route picks what its messages contain:

  • Full: the meeting title, date and time, length, number of participants, whether it was external or internal, the groups that made the route match, the summary, up to 10 action items and up to 5 decisions, and an Open in VoiceCap button.
  • Brief: the same title and details and the button, with only the number of action items and decisions instead of the summary and the lists.

Participant names and email addresses are never posted, only how many people attended. The date and time are shown in each reader's own Slack time zone.

A channel shared with another organization (shown with a Shared badge) always gets the brief message, whatever the route is set to.

When a meeting is filed into a group later

If a meeting is shared with a group after it finished, routes filtered on that group post it then, as long as the meeting finished within the last 7 days. A channel that already got the meeting doesn't get it again.

When a meeting changes after it was posted

When someone edits or regenerates a meeting's summary, renames the meeting, edits or deletes one of its decisions, removes the meeting from a group, or stops sharing it with the whole organization, VoiceCap updates the messages it already posted about that meeting, in channels and in direct messages. An updated message never shows more than the one it replaces: a message that was posted brief stays brief.

When VoiceCap updates a meeting's messages, a channel that would no longer get the meeting (it left the route's group, the route was stopped or deleted, or the route's owner can no longer open it) gets "This meeting is no longer shared here." instead, with the Open in VoiceCap button. A direct message gets the same note if the meeting's owner has changed or left the organization.

Stopping or deleting a route stops new posts to its channel. Messages it already posted stay as they are until the meeting changes or is deleted.

Ticking off an action item or renaming a speaker doesn't change posted messages. If Slack doesn't allow a message to be edited, it stays as it was. A deleted meeting's messages are removed, as described below.

Who can see posted summaries

  • Everyone in the channel can read the message, whether or not they can open the meeting in VoiceCap. The editor reminds you of this for every route.
  • A channel shared with another organization (shown with a Shared badge) also shows the message to people outside your Slack workspace, so it only ever gets the brief message.
  • Open in VoiceCap still needs access: someone who can't open the meeting sees that they don't have access.
  • On the meeting page, the meeting's author, Owners and Admins see where it was posted, for example "Posted to #sales in Slack".
  • When you delete a meeting, the summaries VoiceCap posted about it are removed from Slack too, in channels and in direct messages. If Slack isn't connected at that moment, VoiceCap can't reach those messages, so remove them in Slack yourself.

Getting your own meetings as a direct message

Once Slack is connected, every member sees Send my meeting summaries to me in Slack on the Notifications card in Settings > Profile. Turn it on to get each of your completed meetings as a direct message from VoiceCap, with the full summary.

Your Slack account must use the same email address as your VoiceCap account, and your VoiceCap email must be verified. Meetings filed into a group later aren't sent as a direct message.

When posting fails

If Slack refuses a message for a route, the route shows the reason in the routes table:

  • "VoiceCap can't find this channel. It may have been deleted, or it's private and VoiceCap was removed from it."
  • "Invite @VoiceCap to this private channel."
  • "This channel is archived."
  • "VoiceCap isn't allowed to post in this channel. Check who may post there in Slack."

Every route on that channel stops posting until you fix it. Fix the channel in Slack, then click Send test message on one of its routes. The test message contains no meeting content. When it arrives, the routes on that channel start posting again. Saving the route with Edit does the same.

A meeting that failed to post isn't sent again automatically, and neither is one marked Didn't finish, since it may already be in the channel. Check the channel and share the meeting there yourself if it's missing. The Recent activity list under the routes shows each recent post, its status (Posted, Failed, Sending, Didn't finish, Skipped or Removed) and a link to the meeting when you can open it. A skipped post says why it wasn't sent, for example "Not sent: Slack needed to be reconnected."

If Slack rejects VoiceCap's access, the card switches to an Error status. Click Reconnect Slack and approve the request again.

If you reconnect Slack to a different workspace, routes made for the old one show "Belongs to another Slack workspace" and post nothing, and Send test message refuses them. Edit each one and pick a channel in the new workspace, or delete it.

Disconnecting

  1. Go to Settings > Integrations.
  2. Under the Slack card, click Disconnect.
  3. Confirm in the "Disconnect integration?" dialog.

Disconnecting stops all posting, including direct messages, and removes VoiceCap's access to your workspace. Your channel routes are kept and work again if you reconnect the same workspace. To remove the app from Slack too, open your workspace's app settings in Slack and remove VoiceCap. Removing VoiceCap in Slack first also disconnects it here, and the card shows Not connected.