WhatsApp invoice delivery in practice

Why we built this feature

When we launched Invoicr, we had a straightforward idea: make invoicing faster and cheaper for UK sole traders. The bank-to-bank payment angle solved the cost problem. But we kept hearing the same thing from plumbers, electricians, and decorators in our early user calls: "I need to get this in front of the client straight away."

Email felt slow to them. Not in reality, but in perception. A client might see an email hours later, or it lands in spam. WhatsApp is different. It's immediate. It's intimate. It's where they already message their customers about arrival times and job updates.

We didn't invent this behaviour; we just made it official. Before WhatsApp delivery existed in Invoicr, some users were taking screenshots of their invoice PDFs and sending them through WhatsApp manually. That's friction. Our job was to remove it.

The mechanics are simple, the impact isn't

You draft your invoice in the app. You hit send. One option is email. Another is WhatsApp. If you choose WhatsApp, the app generates a link to the invoice and pushes it through WhatsApp Business API to your client's phone number. They tap the link, see the invoice in a secure portal, and if they're ready to pay, they use open banking to transfer the money directly from their bank account to yours.

No card fees. No payment gateway middleman. No client having to hunt for their card details or remember a password.

What took us longest wasn't the technology. It was thinking through the edges. What if a client's phone number changes? What if they're on WhatsApp but prefer email? We settled on this: the feature is optional. You can use WhatsApp for some clients, email for others, or both. We also made sure the invoice portal works identically whether they arrive via WhatsApp or email, so the experience is consistent.

A real moment: launch week

When we rolled out WhatsApp delivery to Pro users, we were nervous. Integration with WhatsApp Business API required approval from Meta. There's always a delay, always a form in triplicate, always something. But we got it through.

On launch day, we had a message from a mobile mechanic in Leicester. He'd sent three invoices via WhatsApp before lunch and marked two as paid already. He wrote: "This is how I actually work. You've finally built something for me, not for accountants."

That stuck with us. Not because it was flattering, but because it was true. Most invoicing software is designed for office workers and bookkeepers. It assumes you're sitting at a desk, managing dozens of transactions in a spreadsheet, reconciling quarterly. A mobile mechanic isn't. A plumber isn't. They're on a job site, dirty, tired, and they need to get an invoice out fast without breaking their workflow.

The payment piece changes everything

Here's the thing that separates Invoicr's WhatsApp delivery from a generic "send PDF via chat app" feature: the payment method on the other end.

Most invoice apps, if they offer WhatsApp delivery at all, send you a PDF or a link to a hosted invoice. The client then has to navigate to a payment page, enter card details, and pay through Stripe or Square or some other processor. They're paying 2 to 3 per cent in fees, and you're losing 1 to 2 per cent of that to the processor. It's a chain.

With Invoicr, the WhatsApp message includes a link to your invoice. They see what they owe. If they tap "Pay now," they're taken through our bank-to-bank payment flow. They authorise the transfer using open banking, and the money goes directly into your account. No middleman. On a £500 job, you save about £8.50 compared to card fees. That adds up fast when you're invoicing multiple clients a week.

We found that clients actually prefer this. It's faster, it feels safer (they're not handing over card details), and there's no "payment failed" surprise three days later.

What we didn't expect

The oddest insight came a few months in: clients were more likely to pay immediately via WhatsApp than they were to email invoices. Not because WhatsApp is magical, but because of context. When you send a WhatsApp message to a client, you've already had a relationship with them. You've been messaging them about the job, the date, the time. The invoice is the next logical message, not a cold email from finance@yourcompany.

That context matters. We also noticed that tradespeople started using WhatsApp delivery for different reasons than we expected. A gardener told us she uses it to send invoices to commercial clients (offices, restaurant chains) who expect quick turnaround and sometimes pay on the spot. A decorator uses it for repeat domestic clients he has a good relationship with. A handyman sends to clients he's confident about, and emails to new customers where he wants to leave a paper trail.

It's not a replace-everything feature. It's a choose-the-right-tool feature. That flexibility matters more than we anticipated.

The constraints are real

WhatsApp delivery is available on our Pro plan (£9.99 a month or £79.99 a year), alongside unlimited invoices, automated payment reminders, and quotes. We didn't put it on the free tier because the infrastructure cost and the per-message API fees add up. We're honest about that.

There's also a ceiling: we're UK-only right now. WhatsApp delivery works because we've built Invoicr specifically for UK sole traders, with UK open banking, UK VAT compliance, and UK CIS compatibility. We could have launched internationally earlier, but we chose to go deep in one market rather than shallow in many.

That's a constraint we're comfortable with, because the tradespeople using this app value specificity. They don't want a global platform with a UK mode bolted on. They want something built for them.