> ## Documentation Index > Fetch the complete documentation index at: https://docs.anycrm.anyreach.ai/llms.txt > Use this file to discover all available pages before exploring further. # 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. ## OpenAPI ````yaml /openapi-generated.json post /meetings/{meeting_id}/invite-assistant openapi: 3.1.0 info: title: anycrm-api version: 0.0.1 servers: [] security: [] tags: - name: Customer Intelligence description: >- Company research and ICP-fit scoring — create a research run, track its progress, and read back scored companies as leads. - name: Outreach description: >- The cold-email management console — domains, mailboxes, and campaigns — as a thin control plane over the SalesForge stack. - name: AnyCard description: >- Authenticated CRUD for AnyCard, the org's digital business-card / lead-capture product. - name: AnyCard Events description: >- Event-attribution analytics for AnyCard — which captured leads converted, broken down by source, owner, and deal. - name: AnyCard Share Links description: >- Unauthenticated endpoints reached by anyone who scans a QR code or opens a shared AnyCard link. - name: AI description: >- A streaming (SSE) AI chat endpoint with account-commit actions it can take on the caller's behalf. - name: Analytics Assistant description: >- The natural-language analytics assistant — a guarded text-to-SQL loop (SSE) that answers ad-hoc questions over the org's CRM data as a least-privilege, read-only database role. - name: Account Readiness description: >- Account Readiness Profiles — AI-scored signals on whether an account is ready for outreach or expansion, computed via a Temporal workflow. - name: Integrations description: >- Pipedream Connect — issuing connect tokens and managing the org's connected third-party accounts. - name: Feedback description: >- User-submitted platform feedback (bug reports, feature requests) — global, not scoped to one organization. - name: Public Media description: >- Unauthenticated image reads for publicly-embeddable assets (card photos, inline email images) — allowlisted by key shape; everything else in the storage bucket stays private. - name: Service Health description: Service liveness. paths: /meetings/{meeting_id}/invite-assistant: post: tags: - Meetings summary: Invite Assistant Now description: >- 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. operationId: invite_assistant_now_meetings__meeting_id__invite_assistant_post parameters: - name: meeting_id in: path required: true schema: type: string title: Meeting Id responses: '200': description: Successful Response content: application/json: schema: type: object additionalProperties: true title: >- Response Invite Assistant Now Meetings Meeting Id Invite Assistant Post '422': description: Validation Error content: application/json: schema: $ref: '#/components/schemas/HTTPValidationError' security: - HTTPBearer: [] components: schemas: HTTPValidationError: properties: detail: items: $ref: '#/components/schemas/ValidationError' type: array title: Detail type: object title: HTTPValidationError ValidationError: properties: loc: items: anyOf: - type: string - type: integer type: array title: Location msg: type: string title: Message type: type: string title: Error Type type: object required: - loc - msg - type title: ValidationError securitySchemes: HTTPBearer: type: http scheme: bearer ````