CONTENT CREATION

Answer a support ticket with a Loom-sourced article when one matches

When a Zendesk ticket arrives, match its question against your library of Loom-derived help articles and, if there's a strong match, draft a reply embedding the relevant article…

CategoryContent Creation
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew Zendesk ticket createdZendeskZendesk
  • ActionLLM ranks help articles by relevanceOpenAI
  • LogicProceed only if match confidence is high
  • ActionFetch matched Loom chapter timestampsLoomLoom
  • OutputDraft Zendesk reply with article and Loom clipZendeskZendesk

What it does

Intercepts incoming Zendesk tickets and compares the customer's question to your existing Loom-based help articles. When the LLM finds a confident match, it drafts a support reply that links the article and embeds the most relevant Loom chapter. Weak or no match leaves the ticket untouched for a human.

When to use it

For support teams that have built a library of recorded walkthroughs and want to deflect repeat "how do I" questions with the exact video segment that answers them, without auto-sending anything risky.

How it works

  1. 1A new Zendesk ticket is created and triggers the workflow.
  2. 2An LLM reads the ticket and ranks candidate help articles by relevance to the question.
  3. 3A confidence check decides whether the top match is strong enough to act on; low confidence ends the run.
  4. 4Fetch the matched recording's chapter timestamps from Loom to deep-link to the right moment.
  5. 5Draft an internal Zendesk reply with the article link and the timestamped Loom embed for an agent to approve.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect ZendeskTickets, queues, knowledge base.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect LoomVideo transcripts, libraries.
  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.