Microsoft 365 integration

Book Microsoft 365 appointments by website or phone

Connect an approved Microsoft 365 or Outlook calendar workflow for availability and confirmed appointment booking with InsertChat.

Review gate: this route remains noindex until a live provider test and customer-safe product screenshot are attached.

Channels

Where it works

AI website assistant and AI receptionist

Authentication

How access is granted

OAuth connection through the supported Outlook or Microsoft 365 integration path.

Repository evidence

Review status

Repository onboarding booking contract reviewed 2026-08-17; live provider screenshot pending

Connection type:
Managed OAuth tool connection
Owner:
Product Integrations
Last tested:
Pending live provider verification
Permissions:
Minimum enabled read and write actions listed on this page; exact provider scopes require live verification.

Changelog: 2026-08-17 — Repository onboarding booking contract reviewed 2026-08-17; live provider screenshot pending

Request integration support

Data access

Reads

What InsertChat reads

  • Availability and calendar context allowed by the connected Microsoft account
  • Event details required for the specific enabled booking workflow
  • Only the account and calendar scope granted during connection

Writes

What InsertChat writes

  • Confirmed appointment events through the enabled Microsoft calendar tool
  • No email, contact, or unrelated Microsoft 365 write unless separately enabled
  • No update or cancellation claim until that exact action is configured and tested

Working workflow

One reviewed path from conversation to outcome

  1. 1Customer asks for an appointment through chat or phone.
  2. 2The assistant collects the fields required by the reviewed booking flow.
  3. 3The Microsoft calendar connection checks the permitted availability and creates the confirmed event.
  4. 4The assistant reports success only from the returned result.

Setup

  1. 1Connect the intended Microsoft 365 account through the workspace integration flow.
  2. 2Select the calendar and the minimum tools needed for booking.
  3. 3Configure timezone, availability, required details, confirmation, and fallback.
  4. 4Test the created event and the unavailable-connection path from both channels.

Limitations

  • Microsoft tenant policy and administrator consent can restrict connection or scopes.
  • Calendar, meeting-link, update, and cancellation behavior varies by the exact tools enabled.
  • A failed write must route to fallback rather than being represented as a booking.

Troubleshooting

  • Confirm the active Microsoft tenant and account are the intended booking identity.
  • Review granted scopes, selected calendar, timezone, and tenant consent.
  • Re-run a controlled booking after reconnecting or changing permissions.