CONREP: automating payment confirmations for an offline-first business
A 10-minute manual task, done by hand for every client, now runs itself. Over 1,000 times and counting.
The problem
Every time a client paid, B2B or B2C, a sales agent had to confirm it by hand. That meant going into the CRM, finding the order, pulling the invoice number, the payment date, the total, and the rest of the relevant details, then writing the message and sending it to the client.
In their internal system, this was slow going. A single confirmation could take up to 20 minutes. Multiply that across every payment, every day, and it adds up to a serious drain, with the usual side effects: typos and copy-paste mistakes, slow responses to clients, and agents stuck doing repetitive data entry instead of selling.
The solution
The fix had to fit a business that doesn't run like an online store. There's no checkout event to hook into. Payments happen offline, and the status lives inside their internal system. So the work was in two parts.
First, we built custom webhooks inside their internal system so that the moment a payment status changes, that update is broadcast as an event we can act on. That was the hard part, and the part that makes everything else possible.
Then we built an n8n flow that listens for those events. When a payment status updates, the flow fires on its own: it pulls the information tied to that client's order, assembles the confirmation, and sends it out with all the relevant details filled in. No agent has to notice the payment, dig through the CRM, or write anything.
The result is that a task which used to depend on a person remembering to do it, and having 20 minutes to spare, now happens automatically the instant the payment is logged.
Why it worked
The instinct with automation is to start with the easy, online-native cases. This was the opposite: an offline business with no built-in trigger to hook into. The work that made it succeed was unglamorous, building the webhooks that turn an internal status change into an event worth acting on. Once that foundation existed, the automation itself was straightforward, and it has been quietly reliable ever since.
The lesson generalizes. Plenty of repetitive, error-prone tasks in offline businesses look un-automatable only because there's no obvious trigger. Often there is one, just below the surface, waiting to be exposed.
Want results like these?
Book a 30-minute call. We'll talk through your setup and whether there's a build that makes sense for you.