EazeProOur editorial approach and corrections
Ask for the recorded remaining balance and the reason it needs attention. Review the invoice before contacting the customer; a summary is not a payment or a sent reminder.
Identify the customer and invoice.
Use the customer or invoice reference when available. Similar names and repeat jobs can make a broad question ambiguous. Ask the assistant to identify the record behind its answer before preparing a follow-up.
Ask for the remaining amount.
An invoice total is not necessarily the amount still outstanding. A deposit, partial payment or recorded refund can affect the balance. Ask for the total, recorded payments and remaining amount rather than only the original invoice value.
For this customer invoice, show the total, recorded payments and remaining balance. Identify the invoice you used.
Read overdue in context.
EazePro’s current direct receivables view uses service/delivery timing and a 24-hour grace period for its classifications. That is different from general invoice due-date aging. Check your actual service dates and customer terms before describing a balance as overdue.
Missing schedule information is also meaningful. It should be reviewed rather than treated as proof that an invoice is overdue or paid.
Keep a draft separate from a send.
An assistant can help write a proposed reminder using details you have verified. A drafted sentence does not mean a message was sent. The current EazePro connector does not send customer reminders or create invoices.
Review the recipient, balance and wording before using the application’s communication workflow. Do not include payment credentials in a prompt.
Check completion at the right level.
A recorded payment and an assistant’s prediction of payment are different things. Likewise, a queued message and a delivered message are different states. Use authoritative records and available delivery evidence when deciding whether more action is needed.