Kevin Hale

Every unpaid invoice gets the right reminder for how late it is: a friendly nudge, a firm follow-up or a final notice. A receivables board shows the whole ledger and how likely each client is to pay, and every final notice waits for your approval before anything goes out.

An agent sorts every support ticket into Billing, Technical or Account and scores how sure it is. A visual board shows the whole queue, and every ticket under the confidence threshold waits for your approval before it is routed.

Refund requests measured against the written policy rather than against a mood: days since the charge, the amount a rule is allowed to settle, and whether this customer has already had money back recently. Each request carries the rules it met and the rules it broke, so a decision can be explained months later. Requests are logged and decided from the screen. Nothing here touches a payment system.

The support desk, ordered by what breaks first. Every open ticket is measured against its first reply target at the moment the check runs, so the board shows what is late rather than what is old. Tickets are logged from the screen, assigned and closed from the screen, and the checks run again on each change.