Skip to main content
Some things are easier to type than say. In-Call Chat gives the participant a chat panel during the meeting where they can send text messages, paste links, or upload files the AI will read on the fly. The AI sees both sides of the conversation — what’s said over voice and what’s typed in chat — so it can respond to either naturally.

​
What it does

Text messages

The participant types; the AI responds in voice. Useful for spelling out names, sharing URLs, or asking a clarifying question without interrupting.

File uploads

The participant drops in a resume, a brief, a contract, or any supported doc. The AI reads the extracted text and can reference it for the rest of the meeting.

​
How files work

When the participant attaches a file:
  1. The chat UI shows the file chip: Uploading → Reading → Ready (or Failed if the file can’t be parsed).
  2. Backend extracts text from the file.
  3. The AI receives a notification that a new file is available, plus the extracted text.
  4. The AI can reference the file’s contents for the rest of the meeting.
Files are transient to that meeting only — they don’t get added to the scenario’s Knowledge Base, and the next meeting from the same scenario doesn’t see them.

​
Supported formats and limits

​
Use cases

Resume Screening

Candidate uploads their resume mid-call. The AI interviewer immediately tailors questions to their experience.

Sales Discovery

Prospect drops in their RFP or current vendor contract. The AI rep references specific clauses while pitching.

Document Review

Legal/medical/financial review meetings where the participant brings the document and the AI walks them through it.

Async Clarification

Participant pastes a URL or types a hard-to-pronounce term mid-meeting without breaking flow.

​
Privacy

Chat messages and file uploads are scoped to that single meeting. They don’t persist beyond the session, they aren’t visible to other participants of other meetings, and they don’t pollute the scenario’s Knowledge Base. If you need files to persist across meetings of the same scenario, attach them to Knowledge Base instead.
  • Knowledge Base — scenario-wide files, persistent across meetings
  • Present File — the AI shows files; the inverse of chat upload
  • Consent — pre-meeting consent capture for sessions that handle sensitive uploads