CHATBOTS

Slack DM Helpdesk Agent with Conversation Memory

A direct-message helpdesk agent that holds multi-turn conversations, remembers context across messages, and answers from your knowledge base.

CategoryChatbots
Enginepaperclip
Difficultyadvanced
Triggerevent
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerSlack direct message receivedSlack
  • ActionLoad conversation historySlack
  • ActionRetrieve KB context as neededSupabaseSupabase
  • ActionAgent composes context-aware replyOpenAI
  • OutputSend DM responseSlack

What it does

Gives employees a private, conversational helpdesk in Slack DMs. Unlike a one-shot answerer, this agent keeps the thread's history in mind, so follow-ups like "and what about contractors?" resolve against the prior question. It pulls grounding from your knowledge base and reasons over the conversation to decide what to look up next.

When to use it

When questions are exploratory and rarely answered in a single exchange — onboarding, benefits, or complex IT setup where users naturally ask follow-ups. Best when you want a true assistant experience rather than a FAQ lookup.

How it works

  1. 1A Slack direct message to the bot triggers the agent.
  2. 2The agent loads recent conversation history for the DM to preserve context.
  3. 3It decides, per turn, whether to query the Supabase knowledge base and retrieves relevant passages as needed.
  4. 4The agent composes a context-aware reply, asking clarifying questions when the request is ambiguous.
  5. 5The response is sent back as a Slack DM, continuing the conversation.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SlackChannels, DMs, threads, mentions.
  2. 2
    Connect SupabaseTables, auth, storage, edge functions.
  3. 3
    Connect OpenAIModels, embeddings, files.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.