Frequently asked questions
How Resiphon actually works, in plain prose.
First-visit answers for home-service owners — what the dashboard counts, how the CSV is read, what each opportunity bucket covers, what happens to a follow-up after you approve it, how the three products (Scan, Campaign, Monitor) are priced, and the data Resiphon keeps. If something here is unclear, resiphon@polsia.app reaches a human.
The numbers
Why the dashboard leads with one number.
The hero counts closed recoveries — every dollar attached to a queue row you marked Won in the current calendar month — and the one count headline under it, so the dollar-to-won multiple is meaningful on first read.
CSV upload
Column mapping is automatic. Detection is rule-based.
Resiphon scores each row against the four category rules below. Aliases are recognised, the inferred mapping is shown in the dropdowns, and anything off can be corrected before submit.
The follow-up flow
Drafting, approval, sending, and logging the outcome.
Each follow-up starts in your queue as a draft, moves to "queued" on approval, sends on best-effort, and gets a closed-revenue row on Log-outcome — that last step is what paints the dashboard.
Pricing
Three products, each bought on its own.
Resiphon has no flat monthly rate. You pick the product that fits the work in front of you: a Revenue Scan, a Recovery Campaign, or Resiphon Monitor. Each one ships with the same dashboard tile underneath it.
Your data
Tenant-scoped, isolated, never pooled.
The same scoping rule applies everywhere — every queue row, every dashboard tile, every follow-up — and there is no second customer on the same database table as you.
Ready to try it?
Send a sample export. We'll show you the leak.
A CSV with customers, estimates and the last quarter of jobs is enough. Run a Revenue Scan and watch the headline number sit next to what you spent. No contract, no chat-first gating.