{
  "$schema": "https://promptfoo.tech/schemas/workflow-template.json",
  "name": "Zapier: Auto-Summarize Every Support Ticket into the CRM",
  "slug": "zapier-support-ticket-summarizer",
  "platform": "Zapier",
  "category": "customer-support",
  "difficulty": "Beginner",
  "tags": [
    "zapier",
    "support",
    "crm",
    "openai"
  ],
  "summary": "Every time a support ticket closes, Zapier pushes a 3-line AI summary and next-action tag to the CRM — so sales and CS finally share context.",
  "overview": "Sales calls a customer and has no idea about the four-week support saga that just ended. This Zap fixes the silent hand-off: every closed ticket becomes a 3-line summary on the account record with a suggested next action.",
  "variables": {
    "WEBHOOK_URL": "<your webhook URL>",
    "API_KEY": "<your provider API key>",
    "OPENAI_API_KEY": "sk-..."
  },
  "steps": [
    {
      "order": 1,
      "name": "Choose your ticketing source",
      "description": "Zendesk and Intercom have first-class Zapier triggers. Help Scout works too but requires a webhook step."
    },
    {
      "order": 2,
      "name": "Strip noise before the AI call",
      "description": "Signatures, quoted replies, and auto-responses waste tokens and confuse the model. A Formatter step handles this cleanly."
    },
    {
      "order": 3,
      "name": "Constrain the summary format",
      "description": "Three lines only — what happened, resolution, sentiment (positive / neutral / frustrated). Anything longer gets ignored in the CRM."
    },
    {
      "order": 4,
      "name": "Add the next-action classifier",
      "description": "Give it four options, no free text. Free-text next actions never get acted on."
    },
    {
      "order": 5,
      "name": "Write to the CRM as a note",
      "description": "Not a task — a note. Tasks create anxiety; notes create context."
    }
  ],
  "howItWorks": [
    "Trigger: Zendesk / Intercom / Help Scout ticket status changes to closed.",
    "Formatter pulls the last N messages and strips signatures + quoted replies.",
    "OpenAI generates a 3-line summary: what happened, resolution, sentiment.",
    "A second prompt suggests a next action: 'follow up in 30 days', 'flag for expansion', 'flag for churn risk', or 'none'.",
    "The summary + next action lands as a note on the CRM account."
  ],
  "benefits": [
    "Sales walks into every call knowing the last support touch.",
    "CS leaders can filter accounts by churn risk without reading tickets.",
    "Historical searchability — one line per ticket instead of paragraphs."
  ],
  "useCases": [
    "B2B SaaS with named account owners.",
    "Agencies where account managers rarely see support conversations.",
    "Post-sale motions where expansion signals hide in support tickets."
  ],
  "example": "CRM note: 'Ticket #4821 closed. What: SSO misconfig blocked 12 users. Resolution: guided admin through IdP metadata upload. Sentiment: frustrated. Next action: follow up in 30 days.'",
  "faqs": [
    {
      "q": "Won't this create noise in the CRM?",
      "a": "Only if you write every ticket. Filter by ticket length or category so 1-message tickets don't spam the account."
    },
    {
      "q": "Which model?",
      "a": "GPT-4o-mini is more than enough. This is summarization, not reasoning."
    },
    {
      "q": "Privacy?",
      "a": "Strip PII in the Formatter step if your DPA requires it. Never send full email addresses to the model when the account ID is enough."
    }
  ],
  "source": "https://promptfoo.tech/workflows/zapier-support-ticket-summarizer",
  "updated": "2026-05-18",
  "license": "CC-BY-4.0"
}