Policies & Templates
Last Updated: 2025-12-02 10:48 UTC
Personas: Controller / A/R Manager / Legal
Tier Availability: Policy-as-Code features require a Growth, Scale, or Enterprise subscription. Starter plans include basic cadences only.
What you'll learn
- Build cadences with tone, timing, and escalation rules.
- Configure approval thresholds and discount caps.
- Manage policy versioning and publishing.
Step-by-step
- Create or edit a cadence.
- Navigate to Admin → Policies and select New Cadence or edit an existing one.
- Choose tone presets (Formal, Neutral, Confident) and define message steps with offsets (e.g., Day 0, Day 7, Day 14).
- Set guardrails.
- Configure quiet hours, maximum sends per day, and escalation triggers (e.g., escalate to Operator if no response after Day 21).
- Define discount and credit caps; specify which roles must approve exceptions.
- Manage templates.
- Edit email bodies with merge tags like
{customer_name},{invoice_balance}, and{pay_link}. Preview how the message renders for sample invoices. - Attach supporting documents (e.g., latest statement) when relevant.
- Edit email bodies with merge tags like
- Version and publish.
- Draft changes in a new version without impacting live cadences.
- When ready, publish and select which segments should receive the update. Plixo logs the change in the audit trail.
Success checks
- Each active segment references the correct cadence version.
- Approval thresholds align with finance policy and trigger notifications as expected.
- Templates use consistent branding and merge tags without errors.
Common pitfalls
- Editing the live version. Always use drafts so you can review before changes go live.
- Overlooking quiet hours. Default settings may send during customer off-hours; customize for global teams.
- Hardcoding amounts. Use merge tags to avoid inaccurate balances.
Related pages
- Next step: Segments
- Collections Queue
- Deliverability