Help Centre

Thank a customer for paying

Send a short thank-you automatically when an invoice is settled. Text, email or both, and off until you switch it on.

Walkthrough coming soon
90-second video. We're recording these now.

Mucka tells your customer when the job goes in the diary, again before you turn up, and again when your engineer sets off. This is the last one: a short thank-you when they've paid.

It can go as a text, as an email, or as both — each channel has its own switch, and both start off. Head to Settings → Customers → Automatic messages and open Payment thank-you.

It's Customer messages, not Notifications. Settings → Mucka → Notifications is your own alerts, the ones that reach your phone. This one goes to your customer, so it lives under Settings → Customers → Automatic messages instead.

Or just ask. Say "thank people when they pay" to Mucka in chat or in the app and it'll switch it on, as long as you're the owner.

However the money arrived

It doesn't matter how the payment got recorded. All of these fire it:

  • A customer paying by card through your invoice link
  • A card taken on site
  • A bank transfer or cash you type into the invoice
  • Telling Mucka "she paid that yesterday" in chat or by voice
  • A payment Mucka spots in Xero, QuickBooks, FreeAgent or Sage

Three things it deliberately won't do

Worth reading before you switch it on, because each one otherwise looks like the feature being broken.

It only goes when the bill is cleared in full. A deposit or a part payment sends nothing at all. The message says you're all square, and on a part payment that isn't true — you'd be telling someone who still owes you money that everything's settled, and then chasing them anyway.

It won't fire on an old invoice. Anything you raised more than about two months ago is left alone. That's there so plugging in your accounts software can't suddenly message your whole back catalogue: connecting Xero can reconcile hundreds of old invoices in one go, and every one of them would otherwise be a text.

It goes to whoever is being billed. Never to a tenant, even if you've got tenant messages switched on for the other three. The tenant isn't the one paying the landlord's bill.

One payment, one message

If someone settles five invoices in a single bank transfer, they get one message with the total on it — not five. The wording names the first invoice and counts the rest, so it reads "against INV-2385 and 4 others".

Wording it yourself

Same as the other automatic messages. Open the row and you can rewrite both the text and the email, with the merge fields listed underneath and a live preview of exactly what your customer will get:

| Field | What it becomes | | --- | --- | | {{greeting}} | Hi + their first name | | {{client}} | Their full name | | {{amount}} | What they just paid, e.g. £96.00 | | {{invoice_ref}} | The invoice number, e.g. INV-2385 |

The text shows a running segment count as you type, so you can see what it costs before you save it. There's a reset back to Mucka's wording if you go too far.

A few bits aren't editable, on purpose: your business name at the front, the contact number on the end, and the fact that texts never carry links. UK networks block texts with links, so that one would stop your messages arriving at all.

Switching it off for one customer

If a particular customer doesn't want messages from you at all — a builder or a letting agent who settles a dozen invoices a month — open their client record and turn off Automatic messages there. That stops everything Mucka sends them on its own, this one included, without losing it for anybody else.

Where to see what went

Every thank-you shows on the client's record under Communications, with the actual wording and the time it went. Or just ask Mucka: "did we thank Laurie for that payment?"

Nobody who's already paid gets one. Switching it on applies from the next payment onwards. Mucka doesn't go back through invoices that were settled last week — a thank-you for a bill somebody's already forgotten about reads worse than nothing.

Last updated

Still stuck? Talk to a human — we answer every one.