What the copilot never does

• It never goes beyond the manifest. If something isn’t declared as a screen, field or action, it doesn’t exist for the copilot — it never improvises a button or a screen you didn’t give it.
• It never saves, sends or deletes without your confirmation, even if you turned on “let’s do it together” — it’s the product’s own floor, and it can’t be turned off from any setting.
• Your provider’s support staff only guide from their own internal panel: they never fill in or run anything, even if that console’s manifest declared the action.
• It never acts against a third party outside your site (for example, the WhatsApp provider itself) — on those stretches, it guides and waits (section 6).
• It never touches an already-connected channel’s record or the Integrations screen — it only guides in both, for the same reason: several cards of the same type at once, with no safe way to know which one you mean (sections 7.2 and 8.4).
• It never changes your plan or your payment method. Billing is always guide-only — it never fills in or taps anything there (section 8.2).
• It never deletes an agent — that feature doesn’t exist in the platform yet (section 7.1).