Back to Support Ticket Deflection
SUPPORT TICKET DEFLECTION · PLAYBOOK

Your users can Google it. So why are they opening a ticket?

Ten questions every SaaS support team gets, the docs-y article that quietly creates a ticket, and the rewrite that deflects it. Google reads what a customer meantand hands them the next action; most help centers are organized by your taxonomy, in your jargon. The gap between those two is your ticket volume. Here's where it leaks, and the fix for each.

  1. 01

    “I can’t log in”

    What most help centers serve

    “Configuring SAML SSO & SCIM Provisioning”, Written for an IT admin setting up SSO — not for a user locked out right now.

    The rewrite that deflects

    Can’t log in? Get back in — and how to tell if it’s an SSO issue.

    1. 1.Try a password reset from the login screen.
    2. 2.If your company uses SSO, click “Log in with [your company]” — not a password.
    3. 3.Still stuck? Send your IT admin one line so they can check your SSO config.

    The move: Title it with the words they typed, and answer it in the first line. If the title isn’t their question, they bounce to a ticket.

  2. 02

    “Why am I still being charged for a teammate I removed?”

    What most help centers serve

    “Understanding Proration & Billing Cycles”, They want the credit, not a lecture on how proration works.

    The rewrite that deflects

    Removed a seat but still billed for it? Here’s why — and how to get the credit.

    1. 1.Seats prorate to your billing cycle.
    2. 2.Open Billing → Seats to confirm the change applied.
    3. 3.Mid-cycle removals credit your next invoice.
    4. 4.If it didn’t, tap “Report a billing issue” — we adjust within one business day.

    The move: Name the exact thing they’re staring at (the invoice line), then resolve it — don’t explain the system.

  3. 03

    “How do I connect an integration? Why isn’t my data syncing?”

    What most help centers serve

    “API Reference: Webhooks & OAuth Scopes”, They’re clicking a button, not reading API docs.

    The rewrite that deflects

    Connecting an integration (Slack, HubSpot, etc.): 3 steps — and the 2 reasons sync fails.

    1. 1.Settings → Integrations → pick your tool → Connect.
    2. 2.Authorize, then choose what to sync.
    3. 3.Not syncing? Reason 1: the token expired — reconnect.
    4. 4.Reason 2: a permission scope is missing — re-grant access.

    The move: Pair the happy path with the top 2 failure modes in the same article. It’s activation-critical, so it deflects a churn risk, not just a contact.

  4. 04

    “How do I cancel — or just downgrade?”

    What most help centers serve

    “Plan Changes & Subscription Management”, Often buried on purpose — which breeds a ticket and resentment, and misses the chance to save the account.

    The rewrite that deflects

    Need to cancel? Here are your options (including a cheaper plan).

    1. 1.Settings → Plan.
    2. 2.Choose Downgrade to keep your data on a smaller tier, or Cancel to end at the period’s close.
    3. 3.Either way, your data is held 90 days and access runs until the cycle ends.
    4. 4.Changed your mind? Reactivate anytime in that window.

    The move: Offer the off-ramp before the exit. A self-serve downgrade saves an account a buried cancel page would have churned.

  5. 05

    “What’s included in my plan? Why am I hitting a limit?”

    What most help centers serve

    “Usage & Quotas Reference”, They’re not comparing plans — they hit a wall right now and want to know why and what to do.

    The rewrite that deflects

    Hit a limit? Here’s what your plan includes and how to see your usage.

    1. 1.The 3 limits that actually block work: seats, storage, and API calls.
    2. 2.Check live usage at Settings → Usage.
    3. 3.Here’s what each cap does the moment you reach it.
    4. 4.Raise it in one click from the same screen.

    The move: Answer the limit question at the moment of the limit, with the upgrade path attached. It deflects the ticket and surfaces expansion revenue.

  6. 06

    “How do I export my data?”

    What most help centers serve

    “Data Portability & Retention Policy”, Reads like legal cover, not a how-to — so they ask a human “can I actually get my stuff out?”

    The rewrite that deflects

    Exporting your data: what you get, in what format, and how long it takes.

    1. 1.Settings → Data → Export.
    2. 2.You get a CSV (or JSON) of your records, settings, and history.
    3. 3.Large accounts get an emailed download link within the hour.
    4. 4.Here’s exactly what’s included — and what isn’t.

    The move: Answer trust questions with specifics. Vague reassurance on data, security, or portability creates tickets and quiet distrust; concrete specifics deflect both.

  7. 07

    “How do I make someone an admin / change what they can do?”

    What most help centers serve

    “Roles & Permissions Reference” (the full grid), It’s org-chart-shaped, but the user is task-shaped: “I want Sam to manage billing, nothing else.”

    The rewrite that deflects

    Who can do what — and how to change it.

    1. 1.The 3 roles in plain terms: what each can and can’t touch.
    2. 2.Change a role in 2 clicks: Settings → Members → pick a person → Role.
    3. 3.The one thing only an Owner can do: transfer ownership or delete the workspace.

    The move: Shape permission docs around the task, not the matrix. “I want X to do Y” is the real query; a capability grid makes them ask a human to translate it.

  8. 08

    “How do I invite my team?”

    What most help centers serve

    “User Management” (a tour of the screen), Explains the buttons but not the gotchas — pending invites, seat limits, what the invitee sees — which are exactly what generate the follow-up ticket.

    The rewrite that deflects

    Inviting teammates: how to send it, what they’ll see, and why an invite might not stick.

    1. 1.Settings → Members → Invite, then enter their email.
    2. 2.They get an email and land on a join page.
    3. 3.At your seat limit? The invite holds until you add a seat — here’s where.

    The move: Tell them what happens next. Spell out the invitee’s experience and the one failure mode, and the “did it work?” follow-up never gets sent.

  9. 09

    “I lost my 2FA / authenticator — how do I get back in?”

    What most help centers serve

    “Multi-Factor Authentication Setup”, It’s how to enable 2FA — but they’re locked out of it and mildly panicking.

    The rewrite that deflects

    Lost your 2FA device? Here’s the safe way back in.

    1. 1.Try your backup codes first — here’s where you saved them.
    2. 2.No codes? Request a reset.
    3. 3.For security we verify identity manually — usually within a few hours.
    4. 4.Here’s what we’ll ask for, so you can have it ready.

    The move: On security flows, lead with the safe path and set the time expectation up front — or they’ll re-ticket twice while they wait.

  10. 10

    “Is it down? Something just broke.”

    What most help centers serve

    Nothing self-serve — so the panic goes straight to a ticket., With no triage path, every blip becomes a contact spike.

    The rewrite that deflects

    Something not working? Check this before you report it.

    1. 1.Check your status page first — and subscribe there for updates.
    2. 2.60-second self-check: hard refresh, clear cache, and check your integration’s status too.
    3. 3.Still broken? Report it with what you were doing and the error you saw, so we jump straight in.

    The move: Give the panic somewhere to go that isn’t a ticket. A status page plus a 2-step self-triage absorbs the spike — and the “what to include” ask makes the tickets that do land actionable.

See it on a real question, try the live demo

Run this on your own help center

Upload a CSV of your last 3 months of closed tickets. We send back a free Deflection Snapshot: your top repeat questions, the wording customers use, and a sample rewrite.

Get a free Deflection Snapshot