Using Wilson

Once an admin has installed Wilson for your organization, each teammate does two things: link their Slack account once, then start giving Wilson work in DMs and channels.

Link your Slack account

Linking tells Wilson which Dynamiq user you are when you message it in Slack — that mapping is what lets your own connected apps apply to your requests.

You can only link to the Slack workspace that belongs to the organization you are connecting from. To unlink later, open the account menu and choose Unlink Slack account — it takes effect immediately, and you can re-link anytime.

Talk to Wilson

Wilson listens in two places:

• Direct messages. Open a DM with Wilson and just type — every message in the DM is for Wilson, no mention needed.
• Channels. Where Wilson is in the channel, start a message with @Wilson and your request. Wilson replies in a thread on your message.

A Slack thread where a user has mentioned Wilson and Wilson has replied with a summary and an uploaded file

screenshot: wilson-slack-conversation

A few things worth knowing about how Wilson behaves in Slack:

• One thread is one conversation. Wilson keeps the context and files of a thread together and picks up where that thread left off. A new thread (or a new DM message that starts its own thread) is a fresh conversation.
• In channels, mention Wilson each time. Wilson acts on messages that mention it. A plain follow-up in the thread that does not mention Wilson is left alone — mention @Wilson again to continue.
• Send and receive files. Attach files to your message and Wilson works with them; it returns deliverables as native Slack file uploads in the same thread, with a short summary alongside.
• It asks before risky actions. For anything destructive, irreversible, external, or costly, Wilson asks you to confirm with buttons in the thread before proceeding.
• Slash commands. Use /cancel to stop Wilson's current task in that channel, and /start for a quick reminder of what Wilson is.

Manage connectors

Wilson uses the same connectors as Chat, but you manage them on the Wilson site's Integrations page rather than inside Slack. When you connect an app there, you choose a scope:

• Just me — a personal connection only you use.
• Entire organization — a shared connection available to the whole team.

In a DM, Wilson runs as you, so both your personal connections and the organization's shared ones are available. In a channel, requests run in the organization's context, so the shared organization connections apply. This is where the flagship AWS and database connectors come in — connect a database once (with its SSH tunnel if it sits behind a bastion) and Wilson can query it from Slack.

What differs from web Chat

Wilson is the same agent as Chat, adapted to Slack. Compared with the web Chat surface:

• No per-conversation model picker. Wilson runs on the model configured for the workspace, rather than one you choose per conversation.
• Connectors are managed on the site, not per conversation. There is no in-Slack connector toggle; the enabled set comes from your and your organization's Integrations.
• Output is Slack-native. Results arrive as file uploads and threaded messages instead of the web workspace's interactive file and tool-details panels.
• Slack controls replace the web UI. Slash commands and thread buttons stand in for the sidebar, model selector, and on-screen toggles.

Next steps