CHATBOTS

Onboarding coach answering Zendesk tickets from Notion docs

When a new onboarding ticket lands in Zendesk, this drafts a doc-grounded reply from your Notion knowledge base and posts it as an internal note for an agent to send.

CategoryChatbots
Enginesim
Difficultybeginner
Triggerevent
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew onboarding ticket in ZendeskZendeskZendesk
  • LogicKeep how-to questions only
  • ActionRetrieve pages from NotionNotionNotion
  • ActionDraft grounded reply with citationsOpenAI
  • OutputPost draft as Zendesk internal noteZendeskZendesk

What it does

Brings the doc-grounded coach to your ticketing workflow. New onboarding tickets in Zendesk trigger a retrieval against your Notion knowledge base, and OpenAI drafts a complete reply citing the relevant articles. The draft is added as an internal note on the ticket so a human agent can review and send it in one click.

When to use it

Use it when your onboarding support runs through Zendesk rather than live chat and you want agents to start from a strong, accurate draft instead of a blank reply box. The agent-in-the-loop step keeps quality high while cutting handle time.

How it works

  1. 1A new ticket in Zendesk tagged as onboarding fires the trigger.
  2. 2A filter confirms the ticket is a how-to question, not a bug or billing issue.
  3. 3Relevant pages are retrieved from the Notion knowledge base.
  4. 4OpenAI drafts a grounded reply with cited article links.
  5. 5The draft is posted as an internal note on the Zendesk ticket for agent review.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect ZendeskTickets, queues, knowledge base.
  2. 2
    Connect NotionPages, databases, comments.
  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.