Treasury Sales Deal Request Flow
Submitted by Mohammad Ahmad AlHarbi
Pain point
Branches send deal requests to Treasury Sales with incomplete tables, causing back-and-forth to fill in missing details. Once complete, getting a rate to the requester and their approve/reject/negotiate decision happens over scattered emails and calls with no tracked status.
Proposed solution
A Power Automate flow starts with a form that enforces required fields, then emails Sales with the requester cc'd. Sales replies with a rate via Reply All so the requester sees it directly — the flow only checks that a reply exists, it doesn't parse the content. The flow then emails the requester with Approve/Reject/Negotiate options: Approve triggers an automatic confirmation, Reject closes the request, and Negotiate is handled manually outside the flow.
Claude surface
Chat
Open question
Whether every reply structure gets picked up correctly by the existence check — lower risk than reading content, but still worth a quick real test before the demo.