# Mark a job as confirmed with the customer

Source: https://help.mucka.ai/schedule/mark-a-job-confirmed-with-the-customer
Category: Schedule
Last updated: 2026-08-12

> Tell Mucka the customer has already agreed to a visit, so it stops chasing you the night before to confirm it.

The night before a job, Mucka checks whether the customer actually knows you're coming. If nothing has gone out and nobody has said they've agreed it, you get a card offering to send them a confirmation.

Most of the time that's useful. But if you book jobs on the phone, you've usually agreed the time with the customer while they were still on the line — and being asked to confirm it again the next evening is just noise.

So tell Mucka. There are two places to do it, and neither of them sends the customer anything.

## When you book the job

On the job itself, under the date and engineer, there's a tick box:

> **Customer's confirmed this time**

Tick it if you've already agreed the visit with them. That's it — Mucka won't raise a card about that job.

The box only appears once the job has a date on it (there's nothing to agree to otherwise), and it's hidden on a [pencilled-in job](/help/schedule/pencil-a-job-in), because a pencil is provisional by definition.

## On the card, the night before

If you forgot to tick it, or the job was booked by someone else, the card that comes up has three buttons rather than two:

- **Send confirmation** — emails the customer the message shown on the card.
- **Already confirmed** — records that you've agreed it with them. Nothing is sent.
- **Dismiss** — you don't want either.

**Already confirmed** is the one to use when you've spoken to them. It writes it onto the job, so the diary shows it as confirmed and Mucka stops asking.

<Callout>
  **Don't use Dismiss for this.** Dismissing a card tells Mucka you didn't want it raised at all, and it learns from that — dismiss enough of them and it stops flagging unconfirmed jobs altogether, including the ones nobody has spoken to. "Already confirmed" tells it something completely different: the spot was right, you'd just got there first.
</Callout>

## Moving a job unticks it

If you change the date or time, the confirmation comes off. The customer agreed to Tuesday at nine; they haven't agreed to Thursday at two, and nobody has told them yet.

That means a moved job can raise a fresh card the night before — which is the point. It's the one case where a job everybody thought was sorted quietly isn't.

The exception is a job moved by the AI receptionist while the customer is on the phone. They agreed the new time out loud during that call, so it stays confirmed.

## Where you can see it

Open any job and the Schedule section tells you where it stands:

- **Confirmed with the customer when the job was booked** — someone agreed it with them.
- **Marked as confirmed with the customer** — you ticked the box or answered a card.
- **A confirmation went out. No reply back yet** — a text or email was sent, but nobody has come back to you.

That last one is deliberately not the same as confirmed. A text that left the building isn't a customer who read it.

## What this isn't

Two other things in Mucka use the word "confirm", and this is neither of them:

- **[Booking confirmation texts](/help/schedule/booking-confirmations-and-reminders)** are the automatic text Mucka sends when a job goes in the diary. If you've got those switched on, jobs are already covered and you won't see these cards for them.
- **[Confirming a pencilled job](/help/schedule/pencil-a-job-in)** is you committing to a slot you were holding. That's your decision about your diary, not the customer's about their day.