Start Here

Last Updated: 2025-12-03 20:30 UTC

Platform Feature: This guide is for the full Plixo A/R Automation Platform. Using Sniper? Go to Sniper Documentation →

Personas: CFO / Controller / A/R Manager / A/R Operator / Sales / CSM / Legal / Billing Admin

What you'll learn

Understand what Plixo solves for revenue and finance teams.
Identify which role-based guides are relevant to your job.
Learn the core vocabulary used throughout the product.
Familiarize yourself with the updated CFO Console, Collections workspace, Disputes workspace, and Deliverability tooling so you know what “live data” looks like in /app.

Understand what Plixo is. Plixo is an accounts receivable co-pilot that accelerates cash collection without sacrificing customer relationships. It reduces Days Sales Outstanding (DSO) by orchestrating outreach across email and the mini-portal, spots risk early with an always-fresh aging view, and keeps past-due balances in check. Plixo never holds customer funds--payments settle directly through your Stripe account--and the MVP operates with read-only connections to your ERP.

Match yourself to a persona. Use the table below to jump to your role guide and learn how Plixo supports your daily workflow.

Persona	Primary responsibilities	Go-to guide
CFO / Viewer	Executive visibility, reporting, board updates	CFO Guide
Controller (Admin)	Policies, approvals, connectors, audit	Controller Guide
A/R Manager	Coverage, queue performance, Autopilot safety	A/R Manager Guide
A/R Operator	Daily queue execution, promises, disputes	A/R Operator Guide
Sales	Relationship context, safe nudges	Sales Guide
Customer Success Manager	Renewal health, plan proposals, customer notes	CSM Guide
Legal	Escalated disputes, approvals, templates	Legal Guide
Billing Admin	Subscriptions, plan changes, invoice hygiene	Billing Admin Guide

Get familiar with Plixo vocabulary. Review the glossary below so terminology in the app, dashboards, and notifications is instantly recognizable.
- DSO (Days Sales Outstanding): The average time it takes to collect payment after issuing an invoice. Plixo tracks DSO trends on the CFO dashboard.
- Aging buckets: Standard invoice stages (Current, 1-30, 31-60, 61-90, 90+) used across the queue, reports, and guardrails.
- Autopilot: Plixo's automation engine that drafts, schedules, and sends outreach using the cadence assigned to a segment once guardrails are satisfied.
- Data-Ready: A readiness score that confirms imports, contact coverage, and connector health meet launch thresholds.
- Shadow Mode: A launch state where Plixo drafts communications but requires human review before anything is sent, giving teams confidence before enabling Autopilot.
- Promise-to-pay: A payer commitment to settle an invoice by a specific date; tracked with reminders and adherence reports.
- Dispute: An invoice challenged by the payer; Plixo records status, SLA timers, and evidence tasks.
- Mini-Portal: A secure, tokenized payer microsite where customers can pay, propose a plan, or submit a dispute.

CFO Console: /admin/overview focuses on cash-collected KPIs, promise adherence, and gradient KPI tiles with (i) tooltips. Demo data now pre-populates so every seed reset has realistic cash flow, exposure, and promise charts.
Collections workspace: /work/queue opens with Today’s Focus cards, AI inspector recommendations, taller compose boxes, and indigo row highlights. Operators see guardrails, promises, and templates without leaving the inspector.
Disputes workspace: /work/disputes places SLA Snapshot KPIs above Today’s Focus + Dispute Metrics cards, then a queue-only table that feeds the inspector below. Evidence slots, templates, and status actions all live there.
Deliverability & DNS: /admin/deliverability exposes SPF/DKIM/DMARC records through accordions with click-to-copy helpers plus verification badges. Controllers can confirm DNS status before enabling Autopilot on a domain.

You can explain Plixo's value proposition and limitations in one sentence to an internal stakeholder.
Each team member knows which guide applies to their role.
Common terms like "Autopilot" and "Shadow Mode" are understood across the implementation team.

Skipping persona alignment. Teams move faster when everyone reads their dedicated guide first.
Confusing Autopilot with custody. Remind stakeholders that Stripe processes all payments and Plixo never holds funds.
Overlooking Data-Ready. Launch success hinges on healthy imports--bookmark the Onboarding Playbook early.