Invite Assistant Now
Put the assistant in this call now — the in-UI twin of the email lane.
Every way the assistant can silently miss a call (a meeting discovered too late for the sweep, attendance answered no and then reconsidered, a bot kicked by mistake, a capacity refusal that has since cleared) has the same fix from a rep’s point of view: “just join, I’m asking”. Until now the only door to that was mailing a link to the assistant’s address, which is a strange thing to do about a call you are already sitting in.
Adhoc lane, and therefore no attendance question: the click IS the answer, exactly as F23 reads an emailed request. What it does NOT override is the org’s own refusals — the reservation re-reads the kill switch and the adhoc switch (migration 156) and refuses there, which is why those two are also checked up front: a rep pressing a button deserves “recording is off for your organisation”, not a spinner and no bot.
Windowed to a call that is actually happening — 15 minutes before the start (people join early) until the end. Outside that, a 422 saying so beats booking a paid bot into an empty room.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Response
Successful Response
The response is of type Response Invite Assistant Now Meetings Meeting Id Invite Assistant Post · object.