Route sales leads by Google Workspace or Microsoft 365

If your product integrates deeply with Google Workspace or Microsoft 365, the first sales question is often “which one do you use?” isBusinessEmail answers it from the lead’s email domain before anyone picks up the phone.

What you learn from one call

"workspace": {
  "google_workspace": { "detected": false, "evidence": [] },
  "microsoft_365": {
    "detected": true,
    "tenant_id": "00000000-0000-0000-0000-000000000000",
    "auth": "federated",
    "identity_provider": "okta",
    "evidence": ["…"]
  },
  "other_suite": null,
  "pending": false
}

(Values illustrative.)

Signal	Routing idea
Microsoft 365 detected	Rep who knows Graph, SharePoint and Teams; demo the Microsoft connector
Google Workspace detected	Demo Drive/Gmail flows; Google Marketplace install story
Both detected	Ask: identity on one, mail on the other is common (and mid-migration)
Federated (Okta, ADFS, Ping)	Bring SSO/SCIM details early; IT is likely involved in buying
`other_suite` (Zoho, Proton…)	Lead with the parts of your product that don’t need either suite
Neither, personal provider	Self-serve or nurture

Implementation

Call /v1/check when the lead arrives (form webhook, CRM workflow or automation tool). A {"domain": "…"} check works if you only have the company domain.
Write uses_microsoft_365, uses_google_workspace, identity_provider (and optionally the tenant ID) into CRM properties.
Branch your assignment rules on those properties.

Step-by-step for common tools: HubSpot forms · Zapier · Make · n8n

Things to keep in mind

It’s the company, not the person. A Microsoft 365 tenant doesn’t mean this lead has a license or admin rights.
pending: true means detection is still running in the background; re-check a few minutes later, or route by category alone for now.
Detection is a strong hint, not proof. DNS can be unusual or stale. Let reps confirm in the first call.
We never probe individual mailboxes or accounts. See how detection works.