CHATBOTS

IT Helpdesk Slack Bot: Self-Serve Password Reset Slash Command

An /it-reset slash command verifies the requester's identity, kicks off the password reset against your directory.

CategoryChatbots
Enginesim
Difficultyintermediate
Triggerevent
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerEmployee runs /it-reset slash commandSlack
  • LogicVerify identity and rate-limit
  • ActionTrigger reset via identity provider webhookHTTP webhook
  • LogicBranch on reset success or error
  • OutputSend private instructions to userSlack
  • OutputLog action to IT audit channelSlack

What it does

Gives employees a one-step `/it-reset` command in Slack to start a password or MFA reset without opening a ticket. The bot verifies the request, triggers the reset through your identity provider's webhook, and walks the user through secure completion steps.

When to use it

When password and MFA resets are the single biggest source of IT interruptions and you want them self-served safely, with an audit trail, instead of over DM or walk-up.

How it works

  1. 1An employee runs the `/it-reset` slash command, triggering the flow with their Slack identity.
  2. 2A logic step confirms the invoking user matches the account in scope and that resets aren't rate-limited.
  3. 3An HTTP webhook call to your identity provider initiates the reset flow.
  4. 4A branch handles success versus a directory error or locked account.
  5. 5The bot sends an ephemeral (private) Slack message with reset instructions or the failure reason.
  6. 6The action and outcome are recorded to the IT audit channel for traceability.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SlackChannels, DMs, threads, mentions.
  2. 2
    Connect HTTP webhookTrigger any URL on agent actions.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    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.