Docs Intent Signals Playbook 2026
Docs traffic is the most ignored intent stream in post-sale. This play classifies every identified account's docs session as risk intent (data export, migration, cancellation) or growth intent (API reference, advanced features), joins it with the account's engagement score, ARR and renewal date, and routes it to the save-play owner or the AE — days before it becomes a ticket or a churn.
Someone at your best account just read the "export your data" page. Your CRM says they're green. Meanwhile the account that spent forty minutes deep in your API reference — the clearest buying signal a customer ever gives for free — got no expansion motion at all, because docs traffic is the most ignored intent stream in post-sale. Marketing instruments every blog visit; nobody routes a cancellation-doc read. This play fixes that: every docs session from an identified account arrives carrying the pages read, the reader's role and the account's engagement score; the pages get classified as risk intent or growth intent; account context — ARR, renewal date, plan — gets joined on; and the signal lands with the person who can act on it, the same day.
Measure it on intent signals routed per week, save plays opened from docs reads, expansion pipeline sourced from docs, and time from doc read to first touch.
How it works7 steps
01SignalInstrument docs like product — because they are product
Pipe docs analytics into your event stream: Mintlify's analytics flow through Segment alongside your product events, so a docs session is just another account behavior. The session arrives as data — the pages read, the reader's role where you know it, and how deep the session went.
- Identify readers wherever you can: logged-in state on gated docs, or the email domain from your changelog and support links. Anonymous traffic still aggregates to account level via company IP — an unnamed reader from a named account is a routable signal.
- Session depth separates browsing from intent: one pageview on the webhooks page is a stray click; six pages of the API reference in one sitting is a project.
02ScoreClassify the pages: risk or growth
Tag your docs taxonomy once, then let every session classify itself. Risk pages: data export, cancellation, migration guides, competitor comparisons, "switching from" content. Growth pages: API reference, advanced features, integrations, anything describing a higher tier than the account's plan. Accoil joins the read with the account's engagement layer, which is what makes the classification honest: an export-page read from an account whose engagement score has been sliding for a month is a five-alarm signal; the same read from a thriving account is probably someone building a backup job. Out the other side comes the routed record: intent class, ARR, renewal date, current plan.
03DecisionSplit the stream: save motion or sales motion
One field routes the signal: intent class. Risk reads flow to the save branch; growth reads flow to the product-qualified branch. Weight by context — risk intent inside 120 days of renewal outranks everything else in the queue, and growth intent from an account already on your top plan routes to the CSM as an advocacy conversation instead of the AE. Neutral reads (getting-started, troubleshooting) don't route at all; a play that cries wolf on every pageview gets muted in a week.
04ActionRoute risk reads to the save-play owner, pages attached
The Slack alert names the exact pages: "Acme read /docs/export-your-data and /docs/migration-guide yesterday — engagement score 41 and falling, renewal in 94 days." That specificity is the entire value; "account showing churn signals" gets ignored, a named page does not. Route to the save-play owner, not a channel-wide broadcast, and thread the account's score trend underneath so triage happens in the message. Field report from teams running this: the cancellation-doc read shows up two to four weeks before the cancellation conversation. That's your entire save window — spend it on outreach, not on re-verifying the signal.
05ActionRoute growth reads to the AE with the feature named
Growth intent routes as a product-qualified signal, and the message names the feature interest: "Three users at Northwind spent this week in the webhooks and API-auth docs — they're on the Team plan, which caps API calls." The AE gets the what (feature), the who (reader roles, when known), and the gap (current plan vs. what the docs describe). This is warmer than any MQL your marketing team will source this quarter — treat it with the same SLA you'd give an inbound demo request.
06Human stepCSM or AE reaches out about the thing they were reading
The outreach references the reading, helpfully — never surveilled. "Saw your team digging into the webhooks docs — want a working example against your account?" beats any campaign ever sent, because it's specific, timely and useful. For risk reads, don't name the scary page; open on the underlying job: "A few teams exporting data this time of year are consolidating tools — worth 15 minutes to make sure you're getting full value?" Offer help with the task, and you'll hear the real story — consolidation, budget, a new stakeholder — while it's still a conversation, not a decision.
07OutcomeCount the days you got back
The outcome is lead time: intent caught days or weeks before it becomes a ticket, a cancellation email, or an expansion opportunity your competitor found first. Track what each routed signal became — save play opened, pipeline created, false positive — and tune the page taxonomy quarterly. Pages that never produce action get unclassified; pages that keep preceding churn get weighted up. Within two quarters, the docs stream stops being noise and starts being your earliest-warning system.
How Accoil fits
Accoil is the join. Docs analytics alone tells you a page was read; Accoil tells you what it means, by landing the read next to the account's engagement score, trend, segment and plan — the difference between "someone read the export doc" and "a sliding account read the export doc 94 days before renewal." The docs platform captures the sessions, Segment moves the events, Slack delivers the routed signal to the human who owns the motion.
The tools named here stand in for their categories — capture sessions from GitBook-style docs or your own help center instead of Mintlify, move events through RudderStack instead of Segment, read alerts wherever your team lives; the play is identical, and Accoil pushes the same signal wherever the work happens.
Accoil is the scoring layer in this playbook — it works on the product events you already collect, and shows your accounts scored in under 48 hours. Free to start, no credit card.
Explore Accoil →Keep reading
AI Agent Account Context Playbook 2026
AI agents are only as useful as what they know about the account. Give yours the whole picture — engagement and usage from Accoil, contract and pipeline from the CRM, billing from Stripe, support history, session replays — and every signal comes back as a one-page brief, a drafted outreach and a suggested next step. The CSM reviews and sends; the judgment stays human, the hour of prep doesn't.
Monday-Morning Account Triage Playbook 2026
Most CSM weeks are planned by the inbox: whoever emailed last gets the attention. This play starts the week from the product data instead — a Monday digest of the biggest score moves, stalled onboardings and upcoming renewals, triaged in fifteen minutes into three piles: save touches to make now, expansion signals for sales, and thriving accounts to leave alone.
Expansion Signal to PQL Handoff Playbook 2026
Expansion revenue hides in usage data long before anyone asks for a bigger plan. Catch accounts that cross your expansion threshold — engagement high, seats nearly full, limits being hit — qualify them against a written PQL profile, and hand the sales-ready ones to an AE with the evidence attached. Everyone else gets in-app prompts instead of a pitch.
Every playbook, one download
All 31 workflows as print-ready playbooks — diagrams included. Plus every new workflow as we publish it.