CHATBOTS

Slack Bot: Escalate Unanswerable Questions to Zendesk

When the helpdesk bot can't confidently answer a Slack question from the knowledge base, it opens a Zendesk ticket and tells the user it has been routed to the support team.

CategoryChatbots
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerSlack app_mention receivedSlack
  • ActionSearch knowledge baseSupabaseSupabase
  • LogicBelow confidence threshold?
  • ActionCreate Zendesk ticketZendeskZendesk
  • OutputReply with ticket ID in threadSlack

What it does

Closes the loop on questions the bot can't handle. Instead of dead-ending with "I don't know," the workflow detects low-confidence retrievals, creates a Zendesk ticket capturing the question and Slack context, and replies with the ticket number so the employee knows a human is on it.

When to use it

When you've deployed a Slack knowledge-base bot and want a safety net for the gaps. Ideal for teams that already triage support in Zendesk and want unanswered Slack questions to become tracked tickets instead of getting lost.

How it works

  1. 1A Slack `app_mention` triggers the flow with the user's question.
  2. 2The question is matched against the Supabase knowledge base.
  3. 3A logic step checks whether the best match clears the confidence threshold; confident hits exit early (handled by the answerer bot).
  4. 4For misses, a Zendesk ticket is created with the question, requester, and a link to the Slack thread.
  5. 5The bot replies in-thread with the ticket ID and an expected response window.

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 ZendeskTickets, queues, knowledge base.
  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.