Slack
Slack is the human side of the loop. Connecting it lets Halyard deliver an agent’s question to the right expert 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: expert routing and captured knowledge. When an agent calls ask_expert and the knowledge base can’t answer, Halyard notifies a teammate in Slack; their reply becomes a searchable knowledge entry. Slack is the only live expert-notification channel today — without it, questions have nowhere to go.
Two connections, two jobs
Section titled “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 expert 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 expert links their own account so routing and attribution land on the correct people.
Connect the workspace
Section titled “Connect the workspace”- In the Halyard app, go to Settings → Integrations.
- On the Slack workspace card, start the OAuth flow and approve Halyard for your workspace.
- 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
Section titled “Link your account”Each expert opens Settings → Integrations, finds the Slack account card, and links their personal Slack identity. Do this for everyone you add as an expert so their answers attribute correctly. See Experts & routing for how routing uses these identities.
Channel policy
Section titled “Channel policy”There is no channel picker, so this is advice, not configuration: keep expert 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.
- Set up your workspace — the full org-setup tutorial.
- Experts & routing — how questions reach the right person.
- Connect your sources — the full source matrix.