A connected Google Workspace or Microsoft 365 account lets agents act on a real calendar and real contacts — offering appointment slots, recognising callers, booking visits. The connection is made once, at organisation level, on Integrations — no re-authorising per agent, and no credentials anywhere near the AI.
Connecting an account
Connecting requires an organisation owner or admin on a Pro or Scale plan.
One card per provider. Press Connect Google Workspace or Connect Microsoft 365.
polite.ai's own consent dialog comes first. Enter the account to connect — it can differ from the sign-in account — and tick the access to grant: Calendar (see and edit events) and Contacts (look up callers), with Mail as an option where offered. The read scopes start ticked; Mail — the one that sends as the connected account — starts unticked.
Continue to Google/Microsoft leads to the provider's own consent screen to approve exactly what was ticked, then back to Integrations with the connection Active.
polite.ai stores a refresh token, so there is no repeated sign-in — the connection keeps working until it is disconnected or the provider requires re-authorising.
Managing the connection
An Active card shows Connected as with the account's email, plus a chip for each granted scope. Manage access re-opens the consent dialog with the current scopes pre-ticked, to add or remove access in one pass. Reconnect appears as a warning pill when the connection needs re-authorising. Disconnect ends polite.ai's access and deletes the stored tokens immediately — agents that depend on it lose those tools until it is reconnected.
What agents can do with it
Once connected, the tools appear in the Builder — calendar lookups, event creation, contact search, and calendar booking.
Connecting alone gives no agent anything. Each team's tools need explicit approval: an Enable integration tools step appears in the Builder for an admin to confirm. Read tools are ticked by default; anything that sends or changes things carries a write badge and stays off until ticked, and enabling mail allows restricting which domains the agent may ever email.
Teams holding Google or Microsoft tools may only run on approved model providers — OpenAI, Anthropic, Google and Ultravox — so connected-account data never reaches a provider without a no-training commitment. See Models & platforms.
MCP tool servers
The same screen manages the organisation's external MCP tool servers — its own (or a vendor's) systems exposed as live agent tools, connected with no sign-in, an API key, or OAuth. Each card shows the server's health and discovered tools, with re-sync, credential recovery and disconnect; plans include 2 (Pro) or 10 (Scale) connections. Attaching the tools to agents happens in the Builder, like everything else on this page.
What is asked for, and why
Each scope is requested for one visible purpose: calendar access to offer slots and create bookings, contacts access to recognise callers. The AI sees only transient, feature-scoped results — offerable slots, a matched caller's name — never the wider account, and never any tokens. The full picture is in Security, privacy & your data.