Help Centre

See everything Mucka knows about a client

Pull up a client's full history. Jobs, quotes, invoices, notes, payment behaviour and every email or text you've sent them, all in one place.

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

Every quote, job, invoice and note you've ever done with a client lives on their record page. Mucka can pull it up in a sentence, or you can read through it yourself.

Ask Mucka

The fastest path. Open Mucka and say:

"What's the history with the Walkers?"

"Show me Brian Patel's last three jobs."

"Has Sarah paid the last invoice yet?"

"Did we tell the Harpers we'd be there today?"

Mucka summarises the answer in plain English. No clicking through screens.

That last one reads the Communications log below, so you get what was actually sent and when, and whether it reached them — and if nothing has gone to them, Mucka says so plainly rather than leaving you to assume the confirmation went out. Worth asking before you set off.

You can ask about a day as well as a customer: "Did the reminders go out this morning?" or "Did those texts I just sent go?" Mucka tells you which were delivered, which are still waiting on a delivery receipt, and which didn't get through.

Or open their record page

Every client has a page of their own with the lot on it. Tap a customer's name anywhere in Mucka — on a job, on a property, in search — and you land straight on it.

From the Clients list, tapping a row gives you a quick look first: the headline numbers, their contact details and your notes. Along the bottom of that, always in view however far you scroll, are Edit and View full details — the second one takes you through to the record page.

The record page has:

  • Contact: phone, second number, email and address, each one a tap to ring, mail or map
  • Jobs: every job you've done for them, not just the next few — with the date, the type, where it got to and who went
  • Quotes and invoices: what they were quoted, what they've been billed and what's still owed
  • Certificates: any gas or oil certificates in their name
  • Properties & people: every property linked to them, and the contact at each one
  • Communications: every email and text you've sent them (see below)
  • Notes & flags: anything you've jotted down, plus how they pay and anything worth watching out for

For commercial clients there's also a Company section — contact name, VAT number, account reference, and whether they're a property factor or someone you subcontract for.

Quotes, invoices and certificates only show if you've got those skills switched on and you're allowed to see them. An engineer or a subbie won't see what the customer is worth.

Editing is the same form as always: Edit at the top of the page.

What you've sent them

The Communications section on the record page is the log of everything Mucka has sent that client, newest first. Not just that something went, but what it actually said.

Each entry shows you:

  • What it was: quote, invoice, certificate, booking confirmation, appointment reminder, running-late text, review request, quote follow-up, payment reminder, certificate renewal reminder, service reminder, calendar invite, cover plan offer, or a plain email or text you wrote yourself
  • The wording, exactly as the customer received it. Long ones are trimmed with a Show more to open them out
  • When it went, and who sent it. "Sent by Mucka" means it went out on its own, like an appointment reminder. A name means one of your team pressed send
  • Where it went, so you can see if a quote went to the customer's own address or to somebody else's

If a text or an email didn't reach them, the entry says so in red: check the number for a text, check the email address for an email. That one's worth reading, because it means the customer was never told. Mucka also puts a heads-up in your Actions when it happens, so you don't have to go looking. An email or text that did arrive says Delivered in grey underneath. (Emails show this from 24 September 2026 onwards; older ones just say they were sent.)

The same messages are on the job

Anything Mucka sent about a particular job is on that job as well, in Done so far, mixed in with the notes and the check-ins in the order it happened. So "did anybody tell her we were coming?" is answerable without leaving the job.

That includes the quick look you get by tapping a job in the diary — the Job record section there is the same list, so you no longer have to press Edit, or open the full job page, to read what has happened.

It is the same log, not a second one. An invoice or quote email shows on the job it belongs to, even if you sent it from the invoice itself. A text or email that did not get through still says so in red there, which is the bit worth catching before somebody sets off.

A long message is shortened to its first couple of lines with Read it in full beside it. That opens the whole thing over the top of what you were looking at, wording and all, ready to read or copy out — handy when you are writing to a letting agent about a tenant who has stopped answering and you want to show exactly what was sent and when.

What each person sees depends on what they are allowed to see. Anything about money, a quote or an invoice, is only on the job for somebody who can see quotes or invoices on their own screens. An engineer sees the booking confirmation and the reminders, not what you charged.

What it doesn't cover

  • Replies to your email. When a customer replies to one of your emails it goes straight to your own inbox, not through Mucka, so there's nothing for us to log. Same for a text to your own mobile. A text back to your Mucka receptionist number IS in there, because that one comes through us.
  • Messages to somebody who isn't on your client book — a tenant, most often. There's no client record to put them on, so they show on the job instead, which is where you'd go looking for them anyway. Nothing is lost; it just isn't filed under a customer, because there isn't one.
  • Phone calls. Not in this list yet.
  • Anything sent before the log went live. It starts from the day it was switched on, so older emails and texts aren't in there.

What the tags mean

The tags are Mucka's quick read on how a client behaves:

  • Good payer: invoices land on time without chasing
  • Slow payer: usually pays but needs reminding
  • Bad payer: habitually late or disputes invoices
  • Risk flags: disputes, late payer, property factor, anything worth flagging before you quote again

Mucka updates these automatically as the relationship plays out. You can edit them too if you know something the data doesn't.

What's coming

A few things on the roadmap that aren't here yet:

  • A direct "Ask Mucka about this client" button on the record page (for now, just ask in chat)
  • AI-summarised client snapshots that read like a handover note
  • Lifetime value and seasonal job pattern view

If you spot something you'd like, tell Mucka and it'll log the request.

Common gotchas

  • Duplicate clients. Mucka warns at add-time if the name or phone looks like an existing client. If you've already got duplicates, you can ask Mucka to merge them.
  • Missing history. If a client only shows recent jobs, their older ones might have been added before they had a record (loose appointments or one-off invoices). Mucka can stitch these together if you ask.
  • Fewer jobs than you expected. The page only shows you the jobs you're allowed to see. If you're on an engineer or subcontractor login you'll see your own work for that customer, not everyone's.

Last updated

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