Discord

Alan in your Discord server. Same shop, different doorway.

Discord or Slack, pick one. Add Alan to your server; DM the bot or @-mention it from any channel to log counts, mark production tasks done, query stock, draft customer-order schedules. Same eleven tools as the in-product AI, in the channel where your team already hangs out.

Get started for freeTalk to the founder
B
BobToday at 9:42 AM

done 47 PCB-100

A
AlanBOTToday at 9:42 AM

Logged 47 PCB-100 completed. Stock movements posted: -47 PCB-RAW, -47 ATMEGA328P, -235 CAP-100, -470 RES-100, +47 PCB-100.

B
BobToday at 9:44 AM

count PCB-RAW 24

A
AlanBOTToday at 9:44 AM

Logged 24 PCB-RAW. Books had 28, variance −4. Want me to apply the adjustment, recount, or open an investigation?

How it works

Connect once, Alan lives there from then on

Open Settings → Integrations, tap Add to Discord, pick the server, authorize Alan. The bot lands in your server with the permissions it needs (read messages, send messages, use slash commands, add reactions) and nothing more. Total hands-on time: about 10 seconds.

Once installed, anyone in the server who's also a member of your TuringDock workspace can DM Alan or @-mention it. First message from a new Discord user prompts a one-tap link to their TuringDock account.

Count from the bench

count PCB-RAW 47 in your DM with the bot. Alan finds the SKU, computes variance against current on-hand, writes the cycle-count event, and responds with the variance + an action question.

If books and counted match, you get a one-line confirmation. If they don't, Alan offers to apply the adjustment, recount, or open an investigation. The bench operator doesn't need to open the app.

Start, pause, mark done

start PCB-100 when you walk to the bench Monday morning. done 47 PCB-100 when you finish, with the actual quantity. Alan moves the task through its state machine and posts stock movements atomically against the BOM snapshot taken when the task was scheduled.

The Gantt and the My Tasks board update in the web app the moment Alan processes the message. Whoever's sitting at the desk sees the bar flip colour.

Same Alan, three doorways

The character is one. Whether you DM Alan in Discord, in Slack, or in the right-rail sidebar of the TuringDock web app, you're talking to the same first-person assistant with the same eleven tools and the same workspace context. Pick whichever doorway your team already uses.

Workspaces with both Discord and Slack connected: Alan responds in the surface the message came from; the other surface stays silent. No double-posts, no notification spam.

Why this is the new age of MRP

Legacy MRPs assume your team lives in their software. They build their own chat, their own notifications, their own mobile app. The operator has yet another tab to keep open and yet another set of credentials to forget.

TuringDock works the opposite way: we add Alan to the channel your team is already in. If that's Discord, Alan is in Discord. If that's Slack, Alan is in Slack. The MRP becomes ambient intelligence where the work already happens.

Build what's next. Leave the MRPing to our AI.

Build what's next.

Leave the MRPing to our AI. Sign up free, set your shop up in an afternoon.

Get started for free

Common questions

What can Alan do in Discord?
The same eleven tools as the in-product AI: log cycle counts, mark production tasks complete, query stock, ask what's on an operator's plate, draft customer-order schedules, summarize reports, forecast demand. Slash-commands + plain-language messages both work. DMs and @-mentions in channels both work.
How do I install Alan to my Discord server?
Sign in to TuringDock as a workspace admin, open Settings → Integrations, click Add to Discord. You'll be redirected to Discord to pick a server and authorize Alan; takes about 10 seconds. Alan is then DM-able from any channel where the server members include your TuringDock workspace members.
Can I have both Slack and Discord connected?
Yes. Some teams have ops in Discord and customer success in Slack, or are mid-migration between the two. Alan responds in whichever surface the message came from; never cross-posts. No notification spam.
Do operators need a TuringDock account to DM Alan?
Yes. Alan only responds to Discord users who are linked to a TuringDock workspace member, same as Slack. First message from an unlinked Discord user prompts a one-tap link flow. This is the safety boundary that prevents an unrelated Discord member from triggering shop-floor actions.
What Discord permissions does Alan need?
View Channels, Send Messages, Send Messages in Threads, Read Message History, Use Application Commands, Add Reactions. That's the bare minimum to function. Alan does not request administrative permissions, role management, or moderation tools.
Does Alan train on our Discord messages?
No. Alan uses Anthropic's Claude API in standard inference mode; per Anthropic's API policy, your data isn't used to train models. Alan reads your Discord messages only when you DM or @-mention it, only the messages directly addressed to it, and only to answer your request. Server messages where Alan isn't addressed are not read or stored.
Is Alan in Discord live?
In private preview as of May 2026. To join the first cohort using Alan in Discord, reach out at hello@turingdock.com or install from Settings → Integrations once your workspace is enrolled.

Related features

Alan in Slack

Same Alan, in Slack. Pick the doorway your team uses.

AI-first Gantt

What Alan updates when you mark a task done from Discord.

Cycle counts

The other side of Alan's count workflow.

Last updated 2026-05-27