CHATBOTS

Escalate Unanswered Discord Questions to a Linear Ticket

When the FAQ bot can't confidently answer a member's question from the docs, it pings a moderator in Discord and opens a Linear issue so the gap is tracked and resolved.

CategoryChatbots
Enginepaperclip
Difficultyadvanced
Triggerevent
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerMember asks a questionDiscordDiscord
  • ActionSearch Notion docs for answerNotionNotion
  • LogicBranch on answer confidence threshold
  • ActionCreate Linear issue for the gapLinearLinear
  • OutputPing moderator in triage thread with ticketDiscordDiscord

What it does

When a member asks something the docs-grounded bot can't answer confidently, this workflow escalates instead of letting the question fall through the cracks. It pings the on-duty moderator in a triage thread and opens a Linear issue capturing the question, the member, and a link back to the Discord message.

When to use it

Run this when unanswered community questions need an owner and an SLA, not just a shrug emoji. It turns every confident miss into a tracked work item so docs and support gaps get closed and nothing gets lost in chat scroll.

How it works

  1. 1A member asking a question triggers the flow.
  2. 2The bot searches Notion for a grounded answer.
  3. 3A logic step checks whether the answer cleared the confidence threshold.
  4. 4If confident, it replies directly and ends; if not, it escalates.
  5. 5On escalation it creates a Linear issue with the question, member, and Discord link.
  6. 6It posts in the moderator triage thread tagging the on-duty reviewer with the ticket reference.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect DiscordCommunity channels + voice + bots.
  2. 2
    Connect NotionPages, databases, comments.
  3. 3
    Connect LinearIssues, projects, cycles, triage.
  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.