Slack

Slack is the human side of the loop. Connecting it lets Halyard deliver an agent’s question to the right teammate as a Slack DM and capture the reply as knowledge the next agent can search. Slack is the source for Workspace admins (Reader A) setting the org up so agents can ask humans.

What you get: teammate routing and captured knowledge. When an agent calls ask_expert and the knowledge base can’t answer, Halyard notifies the teammates most likely to know in Slack (up to three for a question asked through Haly in Slack — see routing); their replies become a searchable knowledge entry. If nobody else can be reached, Haly asks the person who asked what they know and writes that down instead. Slack is the only live teammate-notification channel today — without it, questions have nowhere to go.

Two connections, two jobs

Both live under Settings → Integrations in the Halyard app, and they do different things:

• Slack workspace — an org-level connection. One admin authorizes Halyard for the whole workspace via OAuth; Halyard stores the bot token and team. This is what powers teammate notifications and answer capture. Connect this once for the team.
• Slack account — a per-user connection. Each teammate links their own Slack identity so their messages and answers are attributed to the right Halyard person. This is identity and attribution, not routing.

A workspace admin connects the workspace; every teammate links their own account so routing and attribution land on the correct people.

Connect the workspace

1. In the Halyard app, go to Settings → Integrations.
2. On the Slack workspace card, start the OAuth flow and approve Halyard for your workspace.
3. Confirm the connection shows as verified.

The whole workspace is eligible once connected — Halyard does not present a channel picker, so there is no per-channel selection step.

Link your account

Each teammate opens Settings → Integrations, finds the Slack account card, and links their personal Slack identity. Do this for everyone you add to the team so their answers attribute correctly. See Your team & routing for how routing uses these identities.

Thread summaries (optional)

Off by default. A workspace admin can turn on Summarise public channel threads on the Slack workspace card. When it is on, Halyard watches threads in the public channels the bot has been invited to and, once a thread goes quiet, keeps a short summary, a link back to the thread, who took part and when. The messages themselves are held for at most 72 hours while the thread is open and then deleted; they are never indexed or searchable.

Summaries that contain a decision, an answer or a process land in the review inbox as candidates. Everything else is recorded as activity only, so “what did the team work on this week” can include chat without storing chat. Private channels and direct messages are not included.

Channel policy

There is no channel picker, so this is advice, not configuration: keep teammate notifications flowing through a narrow, intentional set of channels rather than spraying every conversation. A focused channel policy keeps signal high and makes captured answers easier to trust. Treat it as a team convention.

Next

• Set up your workspace — the full org-setup tutorial.
• Your team & routing — how questions reach the right person.
• Connect your sources — the full source matrix.