# Approve an AI suggestion Source: https://help.mucka.ai/ai/approve-an-action Category: Mucka AI Last updated: 2026-09-09 > How Mucka prepares actions for you to approve, where they appear, and how to send, edit, dismiss or snooze them. Mucka never sends anything without you tapping approve. Everything Mucka prepares (a quote email, a running-late text, an invoice, a job reassignment) shows up as an action card with the exact words and one-tap approve. ## Where actions appear Two places: - **Your Actions list:** everything waiting on you, in one list. Get to it from **View actions** on your [Home page](/), or from Actions in the menu down the side. - **Inline in chat:** when you've just asked Mucka to do something, the action card appears under Mucka's reply. Same actions in both places. The Actions list is the one to check first thing in the morning; the chat is for stuff you've actively asked for. ## Working the list Anything urgent sits in its own section at the top, so "is anything on fire?" is answerable without reading a word. Everything else is underneath, newest first. - **Search** finds an action by who it's about or what it says. - **The filter button** switches between **To do** and **Done**, and narrows to one kind of work — just the invoices, say, or just the certificates. - **Select** lets you tick several at once and deal with the lot together. An empty list is the point, not a fault. Mucka raises a handful a day and clears anything you haven't touched after 48 hours, so most mornings end with nothing left. One thing never clears itself: a [booking the receptionist pencilled in](/help/ai/your-voice-receptionist). Someone on the phone was told the team would confirm, and the slot is held in your diary, so that card waits until you approve it, dismiss it, or the time has passed. Clearing it isn't the same as deciding it. If the thing behind the card is still true — the invoice still hasn't gone out, the certificate is still due — Mucka will raise it again. Only dismissing it tells Mucka you've made up your mind, and that's what stops it coming back. ### Customers you never invoice through Mucka Plenty of firms have a trade client or two — a warranty company, a housing contract — where the work gets logged here but the money goes through the customer's own system. Mucka used to card every one of those jobs, because dismissing a card only ever retired that one job and the next visit was a new job. Now it learns. **Dismiss two "uninvoiced job" cards for the same customer and Mucka stops raising them for that customer** — on the cards and in the evening summary. Nothing to set up and nothing to switch on. If that was the wrong call, approve one of their cards and Mucka starts chasing them again straight away. That's about a *customer*. If it's a kind of *work* you never charge for — free estimates, an inspection you do as a favour — you can say so directly instead of waiting for Mucka to learn it. See [Work you never invoice](/help/invoices/work-you-never-invoice). ### On a phone Drag a row to the left and all three buttons appear together: **Approve**, **Remind**, **Dismiss**. Tap the row instead to open the card in full. Approving anything that sends a message opens the card first. That is deliberate — a collapsed row can't show you what's about to go out, and you should never be sending something you haven't read. A long swipe only ever dismisses, never approves. ### On a computer The list sits on the left and the action you've picked opens on the right. The tabs across the top of that panel — **Job**, **Client**, **Invoice** — open the record right there, so you can check what a customer owes or when they're booked in without leaving the page and losing your place. ## Three ways to handle an action Each action has three controls: 1. **Approve.** Sends, schedules, invoices, whatever the action was. Mucka confirms and it moves to Done. 2. **Dismiss.** Mucka drops the action. Use this when Mucka prepared something you don't actually want sent. 3. **Remind me.** Takes it off your list and brings it back tonight, tomorrow morning, or Friday. Use this for actions you want to do, just not now (e.g. a quote you want to read once more before sending). ## Just tell Mucka to get rid of it You don't have to find the card and tap it. Say it in chat or on WhatsApp: - "get rid of that notification" - "bin the one about Leigh Cobb" - "stop asking me about this" Mucka clears that card and won't raise it again — exactly the same as tapping **Dismiss**. Worth knowing what it does *not* do. It only clears the card. Nothing is cancelled, nothing is messaged, and the job, quote or invoice behind it is left exactly as it was. If you want the work itself changed too, say so and Mucka will ask you first. And if more than one card could be the one you mean, Mucka reads them back and asks which. That's on purpose: once a card is dismissed it doesn't come back, so it's the wrong thing to guess at. This works on WhatsApp too, which is where it's most useful — the daily "you've got cards waiting" message is the one people most often want rid of, and now you can just reply to it. ## Doing several at once Tap **Select**, tick the ones you want, and approve, dismiss or set a reminder for all of them together. Approving several never sends straight away. Mucka shows you every recipient and every message first, on one screen, and nothing goes until you confirm — the same promise as approving one at a time, just quicker. ## Checking what went out The **Done** tab holds everything you've approved or dismissed, plus anything that expired before you got to it. It's the place to look when you want to be sure a reminder actually went, or to check what Mucka has been doing for you. ## "I've already done that" Some cards have a fourth option, because there's a fourth honest answer: you've already sorted it yourself. The first of these is the card asking whether a customer knows about tomorrow's visit. If you agreed it with them when you took the booking, tap **Already confirmed**. Mucka records that the customer has agreed, sends them nothing, and stops asking about that job. See [Mark a job as confirmed with the customer](/help/schedule/mark-a-job-confirmed-with-the-customer). It matters which button you use here. **Dismiss** tells Mucka you didn't want the card at all, and it takes that seriously — dismiss the same kind of card often enough and it stops raising it. **Already confirmed** says the opposite: good spot, you were just too late. Mucka keeps watching, and it now knows something about the job it didn't before. For complex actions (drafting an email, a schedule change, a payment reminder), tap **Review** instead of Approve. Review opens a full modal where you can edit the wording, change the recipient, or tweak the details before approving. ## Editing before approving Tap Review on any action that has editable fields. You'll see: - The full draft (whatever Mucka wrote) - The recipient(s) - Any attachments - The exact moment Mucka will send Change whatever you like, then tap Approve. Mucka uses your edited version, not the original draft. ## Who sees what **Owners and managers** get the whole list: everything Mucka has prepared for the business, plus anything addressed to them personally. **Engineers** get the list on their phone too — there's an **Actions** button on the bottom bar where an owner's says Contacts — but it only ever holds what's addressed to them by name: - a message from the office that's waiting on a reply - a to-do someone put on their list - a reply to a support ticket they raised They can answer and clear those themselves, without asking anyone. What they never see is the business side of the queue — what customers owe, quotes that have gone cold, work that hasn't been invoiced, or anything that sends an email to a customer. That stays with whoever runs the business, and an engineer's list simply doesn't contain it. **Subcontractors** don't get the list at all. A subbie works for another firm, so their phone shows their work and nothing else. ## Common gotchas - **The "Approve" button doesn't actually send mid-call.** During a Mucka phone call, the agent can prepare actions but only owners tapping in the app actually send them. Phone calls are read-only by design. - **A card you didn't ask for.** Mucka sometimes spots things you might want done (a quote a week stale, an invoice 30 days late) and prepares the action proactively. If it's not relevant, just dismiss. Mucka learns from what you accept and dismiss. - **Snoozed actions reappear at 9am tomorrow.** If you snooze something on Saturday, it pops back Sunday morning. Snooze twice if you want it gone for the weekend.