Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.deductive.ai/llms.txt

Use this file to discover all available pages before exploring further.

Slack is where on-call life actually happens. Deductive lives there as a first-class participant. It answers in threads, it auto-investigates alerts, and every Slack thread is bidirectionally linked to the investigation in the web app. By the end of this page you’ll know how to talk to Deductive from any thread, how to continue an alert investigation without losing context, and how to share an investigation across channels.

​
What this page assumes

The Deductive Slack app is already installed in your workspace (admin one-time work. See Admin setup → Connect Slack if it isn’t), and the bot is invited to the channels where you want to use it. This page covers the day-to-day “talk to Deductive in Slack” patterns. Auto-investigation setup is at Wire alerts to auto-investigate.

​
Talk to Deductive in any thread

Two ways to start a conversation:

​
Mention the bot

@Deductive followed by your question. Works in any channel the bot is in, in DMs to the bot, and in threads on existing messages. 
@Deductive what's the recent latency trend on the payments service?
Deductive replies in-thread (or starts a thread on your channel message). The reply includes a web UI link that opens the same conversation in the web app.
Mentioning Deductive in a Slack channel

​
Reply in an alert thread

When an alert fires and Deductive auto-investigates, the alert’s thread becomes the working surface. Replying with a follow-up. Even without @Deductive. Extends the same investigation. 
[alert post]
Deductive: triaged → likely cache eviction storm. Canvas: [link]

You: are you sure it's not the new deploy from 14:20?
Deductive: re-running with that hypothesis weighted higher…
Replying in an alert thread continues the investigation
This is the pattern most teams settle into. The thread is the conversation; the canvas is the artifact.

​
Keep your team in the loop

A few patterns that compound nicely: Drop a canvas link into your incident channel as the on-call work proceeds. The canvas keeps updating as Deductive (and you) refine the investigation, so a link posted at minute 2 is still useful at minute 30. It beats pasting findings repeatedly. Reply to Deductive’s investigation reply with a confirmation or correction. That reply is captured as feedback (see Teach Deductive), which means your in-thread “yep, root cause was the deploy, reverting now” makes the next investigation of the same kind sharper. Reuse a reinforced decision tree. When a question matches a tree your team has already reinforced, Deductive’s reply names it inline (“reusing reinforced path: payments-deploy-regression”). Teammates can see exactly which canonical reasoning path is being applied and decide whether it’s still the right one.

​
Try this next

Wire alerts to auto-investigate

If you skipped this earlier, this is the page that turns Slack from “chat with the bot” into “the bot is doing work for you”.

Teach Deductive

Replies in alert threads are feedback. Make them count.