Plixo Documentation

Guidance for onboarding, billing administration, troubleshooting, and production operations.

Quick Start (10-15 minutes)

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: Controller / A/R Manager / A/R Operator / Billing Admin

What you'll learn

  • Stand up your Plixo organization with the right team access.
  • Connect Stripe payments and import your initial receivables data.
  • Configure core guardrails and launch safely in Shadow Mode.

Step-by-step

  1. Create your organization and invite teammates.
    • Visit app.plixo.ai and sign in with your work email. The first user becomes the Controller-level admin.
    • Name your organization exactly as it appears in your ERP so automated branding and email signatures render correctly.
    • Invite your Controller, A/R Manager, Operators, and Billing Admin from Admin → Users & Roles. Assign the minimum role needed; you can always expand permissions later.
    • If you were referred by a Plixo partner, enter their referral code during sign-up—partner accounts are auto-credited as soon as your starter trial spins up.
  2. Connect Stripe payments.
    • Navigate to Admin → Connectors and choose Connect Stripe. Authorize the Plixo Stripe app--funds continue to settle in your Stripe balance, not in Plixo.
    • Send the automated test event to confirm webhooks are firing. You should see a "Stripe test received" badge on the Data-Ready widget.
  3. Import receivables data.
    • Download the invoice and customer CSV templates (or export equivalent reports from your ERP).
    • Upload your files from Admin → Connectors → CSV Import. Use the mapping preview to match headers (Invoice Number, Due Date, Balance, Contact Email).
    • Resolve validation errors inline--common fixes include normalizing currency codes and verifying emails. Optional: enable the read-only connector for NetSuite or QuickBooks Online once credentials are approved by IT.
  4. Set policy guardrails.
    • From Admin → Policies, create your first cadence. Choose a tone (Formal, Neutral, or Confident), specify business hours, and cap discretionary discounts.
    • Define approval thresholds for credits and payment plans. Controllers receive notifications when approvals are required.
  5. Start in Shadow Mode, then graduate a low-risk segment.
    • Keep new segments in Shadow Mode so operators can review every drafted outreach before it is sent.
    • Once the Data-Ready score is green for three consecutive days and bounce rates are below 2%, enable Autopilot for one low-risk segment (e.g., invoices < $5k in the 1-30 bucket).

Success checks

  • Stripe connection shows "Active" and the test webhook badge is green.
  • At least one invoice and customer CSV import has succeeded with >=95% contact coverage.
  • A first cadence is published, assigned to a segment, and running in Shadow Mode with drafts appearing in the queue.

Common pitfalls

  • Using personal emails for invites. Only invite work-domain addresses so SPF/DKIM alignment stays intact.
  • Skipping the Stripe test event. Without it, Autopilot cannot confirm payments and will keep chasing settled invoices.
  • Publishing policies without quiet hours. Configure quiet hours to prevent off-hour sends and improve deliverability.

Changelog

2025.10
  • Ops console readiness dashboard
  • Maintenance toggle + cron pause commands
  • Docs portal initial release
2025.09
  • Deliverability warmup scheduler
  • Cash App Assist enhancements