Gmail & Outlook

Gmail and Outlook show up in Pact in two different ways today — they are not symmetric, so read this before you go looking for a matching "Connect Outlook" button.

• Gmail connects your actual mailbox to Pact's AI assistant: it can read, summarize, triage, and send confirmed replies from your inbox, and logs outbound sends to the matching CRM contact.
• Outlook isn't a mailbox connection in Pact today. What exists is an Outlook add-in that runs inside Outlook itself, plus two-way Microsoft Calendar sync — see Outlook & Microsoft 365 below.

Sequence and journey emails go out through Pact's own transport — Resend — not through your personal mailbox, for either provider.

Connecting Gmail

1. Go to Settings → Integrations and connect Google — this is the same OAuth flow used for Google Calendar.
2. When your workspace has the Gmail AI assistant feature enabled, Pact appends two Gmail scopes to that same Google grant: gmail.readonly (list/read messages and threads) and gmail.modify (send a reply, and change labels / read state — which covers archiving, marking read, and forwarding). Pact does not request the full-account https://mail.google.com/ scope, so it never has permanent-delete access.
3. One Google consent screen covers Calendar and Gmail together — you don't get a second, separate prompt.

Pact stores an OAuth refresh token, not your password. You can revoke access at any time from your Google account's security settings.

Google Workspace (GSuite) considerations

If your organization manages apps via Google Workspace admin, your IT admin may need to allowlist Pact's OAuth client ID before individual users can connect.

What the Gmail assistant does

With Gmail connected, Pact's AI assistant can:

• Fetch and summarize unread threads, and triage your inbox
• Draft a reply grounded in the matched CRM contact/account/deal — it declines to draft when there's no matching context, rather than inventing one
• Send a confirmed reply, archive, forward, snooze, or delegate a message
• Log outbound sends to the matching contact's activity timeline automatically (only when the recipient is a known CRM contact)

This is an inbox copilot, not sequence infrastructure — it does not send sequence steps and does not pause a sequence when a reply lands.

Inbox permissions and privacy

The gmail.modify scope lets Pact send, label, and mark messages read on your behalf, but it cannot permanently delete anything — that requires the broader mail.google.com scope, which Pact never requests.

If you want to disconnect Pact from your inbox, go to Settings → Integrations and disconnect Google. This also disconnects Calendar sync, since they share one grant.

Outlook & Microsoft 365

Pact does not offer a Gmail-equivalent "connect your Outlook mailbox" flow today. Two related things do exist:

• Outlook add-in + Teams app — an AI compose assistant that runs inside Outlook's own compose window, suggesting subject lines, message bodies, and meeting agendas grounded in your Pact CRM data. It's distributed through Microsoft AppSource, signs in with its own short-lived token (not a personal mailbox OAuth grant), and is installed and managed from Admin → Extensions. See Browser & Inbox Extensions for the capture API, sign-in flow, and client details.
• Microsoft Calendar sync — two-way calendar sync with Microsoft 365 is available as its own connection, separate from mail.

If your team needs Outlook reply activity captured into Pact today, the add-in's capture actions (from Admin → Extensions) are the supported path.

Troubleshooting

"Access denied" during OAuth

Your Google Workspace admin may have restricted third-party OAuth. Contact your IT admin and share the OAuth client ID shown on the Google connection settings.

Gmail assistant features aren't showing up

The Gmail AI assistant is behind a workspace feature flag. If Google is connected but you don't see summarize/triage/reply actions, ask an admin to confirm the feature is enabled for your workspace.

Emails landing in spam

This applies to sequence/journey sends via Resend, not personal Gmail replies — Resend sends via its own API, so your sending domain's reputation applies. Warm up new domains gradually and avoid sending to unverified lists. See Importing data for consent guidance.