A confirmation text tells your customer about the appointment. A calendar invite puts it in their diary, with an alarm on it, so it's still there in three weeks' time when they've forgotten the text.
Sending one
Book the job in as normal. Once it's saved, Mucka asks:
Send [customer name] a calendar invite?
You'll see the date and time, the job reference, and the email address it's going to, so you can check it before committing. Tap Send invite and it goes. Tap Not now and nothing happens. The job is already saved either way, and dismissing the prompt changes nothing about it.
Nothing is ever sent without that tap.
Working on rented property
If the job's at an address with a tenant recorded, the prompt asks who it should go to and lists them:
- the tenant at the address, first
- whoever pays the bill — the landlord, or the managing agent — second
Pick one and send. If you want both to have it, send it again and pick the other.
The tenant leads for a plain reason: a calendar invite says be in on Tuesday at nine, and on a managed property the person who has to be in isn't the person paying. Mucka doesn't choose for you though — plenty of agents want the diary entry too, and only you know which ones.
Whoever you pick is who the email says hello to, and whose name goes into the calendar entry. It never greets one person while landing in someone else's inbox.
Tenants only appear here if you've switched tenant emails on. That's in Settings → Customer messages, and there's more about it in Add tenants to a property.
When you'll see the prompt
You'll be asked when the job has a date on it and there's somebody on it with an email address — a tenant at the address, or the client, or both.
You won't be asked when:
- the job hasn't been booked in yet (nothing to put in a diary)
- there's no client on the job
- nobody on the job has an email address, or the ones on file aren't valid addresses
- the job is already finished or cancelled
- you've already sent an invite for that exact time
If you expected the prompt and didn't get it, an email address is usually the reason. Open the client from Clients, or the property from the job, and check what's on record.
What the customer gets
An email with a calendar file attached. Opening it drops the appointment into whatever they use. Google Calendar, Apple Calendar and Outlook all handle it, on phone or desktop.
The entry carries:
- what the job is
- the date and time, running for however long you've booked
- your business name, and the engineer's name if one's assigned
- the address the work is at
- the job reference
It also sets a reminder an hour before, so their phone nudges them.
If the job moves
Reschedule the job and Mucka asks again, this time Send an updated invite?
Send it and the entry already in their diary gets corrected. They don't end up with two appointments, and they don't end up sat in waiting on the old date.
Until you send that update, the job in Mucka shows Sent, for the old time. The job has moved since, so you can see at a glance who's holding a wrong date.
Checking whether one went
Open the job. If an invite has been sent you'll see a Calendar invite line showing the date it went out. No line means none has gone.
Things worth knowing
It's a one-off, not an automation. Unlike booking confirmations and appointment reminders, this never sends on its own and there's no setting to make it. It's your call, every time.
The customer isn't asked to accept. They've already booked with you over the phone. The invite goes in as confirmed rather than as an invitation waiting on a reply.
It goes to the address on the client's record. You can't type in a different one from the prompt, which is what stops an invite going to the wrong person.
Replies come back to you. The invite is sent from your business, so if the customer replies asking to move it, that email lands with you.