Setupp reads every host’s real calendar. Then writes one event they are all on.

Reads every host's real availability and writes one event with all hosts on it as equal attendees.

• Reads real free/busy for every connected host: a freebusy.query per calendar, on every availability request.
• Writes one event with every host on it as a full attendee: optional: false, responseStatus: "needsAction", guestsCanSeeOtherGuests: true.
• sendUpdates: "all", so the invite, every update and the cancellation are delivered by Google, to everyone on the event.
• Cancelling in Setupp deletes that event and lets Google tell the room.
• Access tokens refresh 60 seconds before they expire, so a connection does not quietly die mid-week.

Same equal-invite behaviour for Microsoft 365 and Outlook.com calendars.

• Reads real free/busy for every connected host through Microsoft Graph's /me/calendar/getSchedule.
• Writes one event on the connected mailbox with every host as a required attendee and the booker alongside them.
• A mailbox Graph will not answer for is treated as unknown rather than free, because an empty getSchedule row looks exactly like an open calendar.
• Times are sent as naive local values with the zone named separately, because sending an offset too makes Graph apply the timezone twice.

Generates the meeting link on the calendar event itself, so every host and the booker get the same one.

• The link is created on the calendar event itself, through conferenceData.createRequest. Hosts and booker read the same URL from the same invite.
• The conference request id is derived from the booking id, so a retried insert returns the same link instead of minting a second one.
• Nothing to connect separately. It comes with the Google Calendar connection.

Teams meeting links generated on the event, alongside Outlook.

• Requested on the Outlook event itself. No second connection, no second consent screen.
• A personal Microsoft account cannot grant OnlineMeetings.ReadWrite; the event is created without a link rather than failing the booking.

Zoom links created per booking and shared with every host.

• Connected per host, so the meeting is created on the account of the host who owns the booking.
• Created before the calendar invite, so the join link is in the invitation rather than a second email.
• Zoom rotates the refresh token on every use, so Setupp will not refresh one unless it can persist the replacement.
• Private intake fields are excluded from the meeting agenda.

New bookings posted to a channel with the Setupp Score, so the team sees who's coming.

• One write-only webhook for a single channel you pick on Slack's own screen. Setupp can read nothing and post nowhere else.
• Each booking posts the booker, their email and company, the event type and time, and the Setupp Score with its band.
• Slack answers failures with HTTP 200 and ok: false, so Setupp reads the body rather than the status code.

Every confirmed booking becomes a contact, with the intake answers and the Setupp Score attached as a note.

• Finds the contact by email first, so a returning booker updates rather than duplicating.
• Attaches a note with the Setupp Score, its reasoning and every non-private intake answer, labelled with the question you wrote.
• Writes contacts and notes only, never deals, companies or pipeline stages. Setupp does not make decisions about your sales process.
• Private intake fields are excluded, the same way they are excluded from the model prompt.