To send payment reminders from Sage 100 or EBP, connect the software to Muzau. A Muzau agent reads the overdue invoices and writes each customer an email from your connected mailbox, rather than a form letter: it cites the reference, the amount and the due date, asks for the payment date and offers to resend the invoice. It stops as soon as the invoice is paid in the software or the customer replies. You can approve each reminder before it goes out.
Sage 100 or EBP knows which invoices are past their due date. What comes out of it, most often, is a form reminder letter: the same template for every customer, an amount, a reminder level. It reaches the customer as one more notice among the notifications, and nobody feels bound to answer it.
The rest takes time: checking that no payment has arrived in the meantime, writing to the person who pays, keeping up the second reminder without damaging the relationship. Your team keeps the relationship and the decision to go further; the agent takes on writing the reminders and tracking them, alongside it.
Sage, including Sage 100, and EBP connect in Muzau's tools, like Cegid, following the model of reminders with Pennylane. The agent reads what the reminder needs: each invoice's reference, its amount, its due date and its payment status. Nothing more: it posts no accounting entry and does no matching of payments. You create the agent in the Workshop, in your own words: remind once the due date has passed, or a few days before, up to six reminders on the days you choose.
Each email cites the reference, the amount from the software, never calculated, and the due date, and asks for the payment date. It writes briefly, without blame, and gets firmer from the second reminder, without threats. The email goes out from the business's mailbox when one is connected, Gmail, Outlook or another mailbox, otherwise from the agent's address. The customer replies to it like any other email.
As soon as the invoice is paid in the software, the agent sees it and stops chasing it. It also stops when the customer replies, even from another address in the same thread, or when a team member writes to them from the connected mailbox; an out-of-office message does not count. A customer who replies STOP, or asks not to be contacted any more, is no longer chased by any of the business's agents.
In Management, you read each planned reminder in advance, exactly as it will go out. You have it rewritten with an instruction, save your own text, move it to another day the agent runs, or cancel the next one, which stops the follow-up for that customer. On the Autonomy page, you decide whether reminders wait for your go-ahead. They go out Monday to Friday at 9 a.m. by default, never more than one scheduled message per 24 hours to the same person, and a large stock of unpaid invoices comes in batches: 10 new customers at most per 24 hours.
With or without an agent, a reminder pulled from accounting software is only right if the software is up to date. Before each round of reminders:
The software's form letter keeps one use: a letter, when emails have got nowhere and your team decides what comes next. Until then, an email addressed to one person, asking a single question, calls for an answer. For the wording of the second and third reminders, see the tone of an invoice reminder.
Autonomous does not mean unchecked. You set the level of autonomy of every agent, its limits cannot be crossed, everything it does is recorded in a plain-language log, and one gesture stops it all.
For the tasks you don't have time for. You give the address of your website, then describe the work in your own words. Nothing to install.