Skip to main content

Tab: Call Log

Context

Tab in Calls. Displays past calls from the organization's telephony backend.

How to Open

  1. Open "Calls" in sidebar
  2. Switch to Call Log / History tab
  3. List appears, sorted by date (newest first)

Content per Entry

ElementDescription
Type iconIncoming, outgoing, missed, voicemail
ParticipantName or number
TimeDate and time
DurationFor completed calls
DetailsClick opens detail view (if available)

Actions

ActionDescription
Call backStart new call to contact
Add to Speed DialQuick access under Calls → Speed Dial
Open detailsFull info, possibly transcript

Transcripts

Live captions during a meeting and the stored transcript in the details drawer are different: captions are visible to everyone in the room; a persisted transcript in call history requires the right server setup (transcriber, database on the Vista node where applicable).

For supported calls (depends on backend):

  • Full text / raw transcript (e.g. Vista node with PostgreSQL)
  • Summary and action items (e.g. Sparks Conf) when provided by the backend

Multiple meetings in the same room: Persistent Matrix chats (e.g. a team channel) can host back-to-back meetings. Each call-log entry and the transcript in Details refer to that meeting—not earlier calls in the same chat (Vista node with local call log and PostgreSQL, as of May 2026).

Reconnects: If you briefly disconnect and rejoin the same meeting within about five minutes, the server typically reuses the same call-log entry instead of creating a duplicate row (same user, same LiveKit room).

Post-meeting sharing (moderators): In the call detail drawer, appointment moderators can share with participants after the meeting ends:

  • Participant protocol — who joined this meeting instance (attendance-style list)
  • Transcript — stored meeting transcript (when created and saved for the appointment)

Recipients see a shared entry in their call log with limited access (protocol only, transcript only, or both). Shares can be revoked. Organizer options allow post-meeting share of protocol and allow post-meeting share of transcript control whether moderators may grant each type (see Event meeting options).

Operations note: Who may read stored transcripts is controlled by server policy. After the meeting ends, sessions are finalized and temporary buffers cleared.

  • Search field above list
  • Filter by name, number, or time range
  • Results filtered live

Requirements

  • Typical: OIDC; call log from the organization’s telephony / Conf backend
  • Alternative (self-hosted): local call log on the Vista node with Matrix identity / token—ask your administrator
  • Without suitable authentication: Tab may be empty or limited

📸 Screenshot: Call Log

📸 Screenshot: Post-meeting sharing