Server-risk-playbooks
FirstDistro can trigger Action plan playbooks and Today's 5 cards when your backend sends specific server-side product events. These signals surface billing, integration, compliance, and onboarding risk before health scores alone would show it.
Requirements
- Send events from your server with
properties.sourceset toserver. - Turn the event on in Settings → SDK configuration → Event settings (status must be active).
- Associate events with the correct
account_idso FirstDistro can match the customer account.
CLI smoke and vendor self-tracking accounts are excluded from playbook triggers.
Server event → playbook mapping
| Server event | Playbook | When it fires |
|---|---|---|
payment_failed | Billing save | Recent server payment_failed in the last 7 days |
integration_sync_failed | Integration rescue | At least 2 server sync failures in 7 days |
seat_limit_approached | Expansion | Recent server seat-limit signal in 7 days |
kyc_submitted (no kyc_approved within 72h) | Compliance assist | KYC submitted from server and still pending after 72 hours |
| Milestone score 0 after 7+ days | Re-engage | Account age ≥ 7 days with milestone score 0 |
What cs sees
- Today's 5: Save-column card with playbook label and server event context (for example, "Billing save needed · Payment failed yesterday").
- Customer Insights → Action plan: Four-step playbook with evidence showing the server signal, prep notes, optional draft email, and mark complete.
- Snooze: Completing the playbook hides the account from Today's 5 for 7 days (same as other playbooks).
Draft email is optional
Step 3 opens your mail client but does not send email from FirstDistro. You can complete step 4 after internal escalation or scheduled follow-up without sending.
Related guides
- Event tracking — how to send server events and configure milestones
- Event settings in the dashboard — turn risk events on before playbooks can fire