Documentation
Product docs for adoption, troubleshooting, and evaluation.
Documentation is part of how buyers evaluate software and how operators recover from edge cases. ChaseNow should explain invoice intake, reminder timing, pause controls, payment confirmation, and troubleshooting without making users guess.
Getting Started
Set up ChaseNow, add your first invoice, and understand how the follow-up sequence starts from day one.
Create Invoice
Create a new invoice inside ChaseNow and decide whether to send now or schedule the first send.
Upload Invoice
Add an invoice you already sent, attach the original PDF if you have it, and start the ChaseNow follow-up layer.
Automatic Follow-up
Understand how ChaseNow sends the first email, schedules the next milestone, and keeps chasing weekly after due date.
Pause Reminder
Pause an active chase when a customer asks for time and keep the invoice separate from active reminders.
Resume Reminder
Resume a paused invoice chase manually or let it restart automatically from the selected resume date.
Mark Paid
Mark an invoice paid to stop the chase immediately and move the invoice into the collected state.
Dashboard
Use the ChaseNow dashboard to understand what is outstanding, what is overdue, and what has already been collected.
Analytics
Read the ChaseNow analytics layer so outstanding trends, expected collections, and client payment behavior make operational sense.
Bank Details
Add business bank details in settings so invoices and reminders can include a direct-transfer path when needed.
Reminder Scheduling
Understand the exact milestone logic ChaseNow uses before due date, on due date, and after an invoice becomes overdue.
Email Deliverability
Understand what affects ChaseNow reminder delivery and what to verify when customers say they did not receive a message.
Troubleshooting
Use this guide when an invoice is not sending, the timeline looks wrong, or the dashboard state does not match what you expect.
Use the docs
Read the workflow, then run it on a real invoice.
The documentation should support onboarding, evaluation, and support deflection. The best next step is still to put one invoice through the actual product.