Check Two Payment Records Before You Chase a Customer
Before your muse sends a late payment reminder, it can check two separate payment records and the customer's own messages, so you never chase someone who has already paid.
What it does
The fastest way to annoy a good customer is to chase a bill they settled last week. It happens when a payment lands in one place and the reminder is written from another. This check closes that gap. When an invoice looks unpaid, the muse first looks in two independent places, such as your payment app and your bank or booking system, and then reads the customer's recent messages for a receipt or a payment note. Only when all three come back clear does it draft the reminder. If a record shows the money arrived, the invoice gets marked as paid instead, and no reminder goes out.
How to use it
- Connect the two places where payments show up for your business, for example a payment app and your booking or accounting system.
- Give the muse access to the customer messages it may read for payment notes, and name the accounts it must never touch.
- Set the rule in plain words: "Before any payment reminder, check both payment records and the customer's messages. If any one shows they paid, stop and tell me instead."
- Read the first few checks yourself. Open the records the muse cites and confirm the match is the right customer and the right invoice.
- Keep approvals on for the reminder itself. The check can run on its own, the message to the customer still waits for your yes.
What you need
- A muse account
- Two separate places where your payments are recorded, connected or readable by your muse
- The customer message thread for the invoice in question
- Approval settings on for outgoing reminders
What to watch for
- Two records only help if they are truly separate. If both simply copy the same system, a payment missing from one is missing from both, and the check adds little.
- Names repeat. A payment from a person with a common name can belong to a different customer, so check the amount and the date, not just the name.
- A promised payment is not a paid one. If the messages only say the money is coming, the muse should report that and wait, not mark the invoice settled.
- Customer messages and payment records are private business material. Keep them inside your own systems, and disconnect any record you no longer want the muse to read.