The two levels of MIA: Proposes and Acts

Where do I see the level, and how do I change it?

• In the MIA panel, at the top, next to the name of whoever is helping you, a label shows the level that applies to you: Proposes (violet) or Acts (green), with a small arrow. In the panel at its usual width you only see its icon —a light bulb for Proposes, a lightning bolt for Acts—; widen the panel and its name shows up too.
• Click it: the How MIA works menu opens with both options, each with its explanation, and a check mark on the one that applies. Proposes: “MIA proposes every change and you apply it.” Acts: “MIA makes routine changes right away and asks before risky ones.”
• Choose one. The label changes right away, and the new level applies from your next message.

When you start a new conversation, the panel also shows the sentence of the level that applies. And if MIA only proposes in your account, in the menu Acts appears disabled and, below it, with a padlock: “In this account, MIA only proposes.” (in a workspace: “In this workspace, MIA only proposes.”).

What does MIA do in each level?

What always waits for your click, whatever the level?

• What can't be undone and what's done in bulk — deleting, merging, changing many items at once. The card puts the number up front and tells you whether what's deleted goes to the 30-day trash.
• What goes out of MB Suite, now or later — emails, WhatsApp messages, posts, invitations, changes on your ad platforms; and also what stays scheduled or turned on to go out by itself: scheduling a campaign or a report delivery, activating a flow or a sequence, enrolling people in them, publishing a form or a report to the client portal, or editing something that's already scheduled or live.
• What's sensitive — members, roles, permissions and invitations; your brand, your domains and your sending domain; disconnecting an integration; creating, archiving or deleting Accounts and who pays for them; partners; client portal access; and what changes how the account works for everyone, such as the CRM's settings, team and assignment rules.

For those, MIA prepares a confirmation card and waits. A “yes” written in the chat confirms nothing: only the button on the card does. How each card works is in Apply, confirm and undo what MIA does: the cards.

Why does MIA sometimes ask even in Acts?

Because in that request it read something written by other people, and it treats that as data, never as an order. That covers everything MIA reads from your records —people, companies, deals, tasks, messages, comments, form answers—, the files you attach, your platforms' data when it's broken down by something other than the date, the device or the country —campaigns, ads, keywords, search terms, pages, posts—, the settings anyone on your team can write —custom fields, the labels of most modules, templates, descriptions— and what comes from the web, like the pages and errors the site audit finds. It only trusts what MB Suite writes —the numbers it calculates, its guides— and the structure that changes with each module's permissions, such as the pipelines and their stages or the CRM labels. That's why, when MIA has to read something like that before changing something, it usually proposes the change even in Acts. The card says so: “I read text written by third parties in this request, so I'm asking for your OK before changing anything.” More in MIA and your data: what it sees, what it never sees and how long it's kept.

There's one exception: if all it read were short names —a deal's title, the name of a person, a company, a campaign or a label—, in Acts it still makes some internal changes that can be undone, such as moving a deal to another stage, changing its value or completing a task, as long as they don't give anything to someone else —an owner, an assignee, a follower— and don't trigger anything that goes out of MB Suite. Everything else it proposes.

Why does MIA bring a plan instead of cards?

When a request involves more changes than it makes sense to review one by one, MIA puts them together in a plan that you review and approve with one click, in both levels. See Plans of several steps: approve many changes at once.

Who decides the level, and can I change it?

Your account and you. The ceiling belongs to the account: MB Suite sets it —Proposes by default—, and the owner or an admin can lower it to Proposes for the whole team. If MIA only proposes in the account, nobody can choose Acts there. Within that ceiling, each person chooses how MIA works for them: everyone starts in Proposes, and each person's choice doesn't change anyone else's. Your choice is saved for each account, and nothing you type in the chat changes the level: only the label does.

How do I make MIA only propose in the whole account?

• Go to Settings > MIA and open the How it works tab. At the top you see the level that applies in the account, Proposes or Acts, with its explanation.
• Turn on Propose every change to me: from then on, MIA proposes every change in the account and whoever asked for it applies it. It applies to the whole team.
• To go back to the level MB Suite sets, turn it off.

That switch only lowers the level: it never raises it above what MB Suite sets, and if MB Suite has MIA on Proposes in your account, the tab tells you. The rest of the team sees the switch, but only an owner or an admin can change it.

If you need Acts in an account where MB Suite has MIA only proposing, ask MIA to pass your request to the MB Suite team (see When MIA can't do something yet, and how to pass a request to support). If it was the owner or an admin of your account who lowered it, ask them.