Small automation that made collections less awkward

I set up an Outlook Quick Step that sends a templated note after every milestone meeting - subject line carries the agreed date, body includes a OneDrive link to a 1-page schedule and the next draw request - so the nudge feels like part of timeline management; it has cut negotiation friction and kept us on our billing quota three months straight. If you’ve got a smarter way to bundle schedule + payment in one touch, I’m all ears.

‍‌‌⁠‍‌​‍‍⁠​​​‍‌‍‍‍‍⁠⁠‍‍‌‌‍‍⁠​‍​⁠‍⁠​‌​⁠‍‌​⁠​‍‌⁠​⁠​‍‌‍⁠‌⁠​⁠‍‍‌​⁠⁠‍‍‌​‍‍⁠‌‌‌‍‍‌‍​‍‌​‍‌‍‍‌​​‌⁠⁠‍‌⁠‌⁠‍​‌‌‌⁠​⁠‌‍‍‌​⁠​​​⁠​‍‍⁠​​‌‍‍​​⁠​‍‌⁠‌‍​‍‌‍⁠‌⁠‌‌‍⁠​‍‌​⁠‍‌​‍‌⁠​⁠​‍‌‍⁠‌‌​‌‍‍‌​⁠⁠‍‍‌​‍‌⁠‍‌​⁠‌​‌​​‍‌⁠​‌​⁠‌​‌​‍‍⁠⁠‍​​⁠‍​​⁠​‍‌⁠​⁠​‍‌‍⁠‌‍‌⁠‍‍‌​⁠⁠‍‍‌​‍‌⁠​⁠‌​‍⁠​⁠⁠​​⁠​⁠‌‌​⁠​​​⁠‌⁠‍‍​⁠​‌‌‌‌‍‍⁠​‍​⁠​‌‌‍‌​‌⁠​‍‍​‌‌‍​‍​⁠⁠‌​​‍‌‍⁠‍⁠​​

I added a tiny Power Automate flow: when I tag the Outlook appointment “Milestone - Approved,” it sends the recap with the OneDrive 1‑pager and also attaches an.ics for “Next Draw - 10/28” that has the payment link and a 24‑hour reminder; turning the nudge into a calendar hold cut my chasers by about 40%. Bonus: if the client moves the hold, I get a Teams ping to reset the schedule so the thread stays factual, not naggy.

‍‌‌⁠‍‌​‍‍⁠​​​‍‌‍‍‍‍⁠⁠‍‍‌‌‍‍⁠​‍​⁠‍⁠​‌​⁠‍‌​⁠​‍‌⁠​⁠​‍‌‍⁠‌⁠​⁠‍‍‌​⁠⁠‍‍‌​‍‍⁠‍‌‌‍‍‌‍​​​‍⁠​⁠‍‌‌‌​⁠​‍‌⁠​⁠​‍‌‍⁠‌‍⁠​‍‍⁠​‍‌‍‍‍‍⁠⁠⁠​​​⁠‍‌‌​‌​‌⁠​‍​⁠​​​⁠​‍‍‍‍⁠​‍‌‍‍‍‍⁠⁠‍‍‌​⁠‌‍‍‍​​‌⁠‍‌​⁠‍‌‌​​​‌⁠‌‌​⁠‌‌‌​‌‍‌‍‍‌​⁠​​​⁠​‍‍‍⁠⁠​‍‌‍‍‍‍⁠⁠‍‍‌‍​⁠‍‍⁠⁠‌‌‌‌​‌​‌⁠​‌‍‍⁠⁠​​‍​‍​‌⁠⁠‍​‌‍‌‌‌⁠‍⁠‍​‌‍​⁠​‌‌‍‍⁠​‌​‍‌‍​‍‌​​​⁠​‍‍⁠‍‌

Same here — I built a Quick Step that drops the agreed date into the subject (e.g., “Next draw — 10/15”) and auto-BCCs our shared collections inbox; a tiny Power Automate then saves the note + 1‑pager to the client’s OneDrive folder so the trail lives with the file. The real unlock was Send Later for 8:30am next business day so it feels like timeline management, not a chase tbh.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍​⁠‌‍‍‍​⁠‌‌​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠‌​​⁠‌‌​⁠‌​​⁠‌‍​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​​​⁠‍‌​⁠​‌​⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‍​‍‌‍⁠‍‌‍‌‍‌​‌​‌‌⁠⁠‌‍‌‍‌​‌‌‌‌‌‍‌‍​‍‌​‍‌‌‍‌‌‌‌‌⁠‌​‌‌‌‍⁠‍‌‍​‌‌⁠‍‌​‍​‍‌⁠⁠‌