How teams use it post-sale
Sprig captures the voice behind the behaviour. Triggering a micro-survey when an account's engagement drops — or right after activation — pairs the "what changed" from your product data with the "why" straight from the user, which is the context a save motion or case study ask needs.
Any of these runs the same plays — Accoil pushes the same signal wherever the work happens.
Workflows using Sprig2
Feature-Launch Adoption Loop Playbook 2026
Most feature launches are announcements with no second act: shipped, posted, forgotten. Run the launch as a loop instead — announce to the cohort that actually needs it, guide first use in-product, track every account into adopted, tried, or ignored, and let each lane drive what happens next, from drop-off surveys to PM interviews.
The NPS Autopsy Playbook 2026
Kill the quarterly NPS blast — survey behavior instead. When an account crosses a behavioral threshold (a sustained spike, a 20-point decline, an activation milestone), the moment picks the micro-survey: power users get the advocacy ask, decliners the friction probe, the newly-activated value confirmation. Every answer is joined with the respondent's actual usage and routed to a different play.
Every playbook, one download
All 31 workflows as print-ready playbooks — diagrams included. Plus every new workflow as we publish it.