Macro is a unified workspace for teams: email, chat, docs, tasks, agents, calls, and CRM — @-linked together with shared AI memory.
Calls
Calls — /app/calls
The Calls list starts with the Calls TutorialRow (from features/video-tutorials) once that video is in its catalog; it sits below the touch inset, outside the virtualized rows.
On desktop a collapsible sidebar starts with the shared outlined New button,
with Search calls immediately left of collapse. Search reveals its field above
New. The sidebar also holds
the views All / Missed / Unattended, a Type section (Internal /
External; External means at least one guest without a Macro account joined),
a Channels section listing channels seen in loaded calls, and Tags. Choosing
a type, channel, or tag shows only that one; choosing it again clears it. These
refinements carry across the three views. The desktop header uses one row:
title, an outlined filter group, a view-options group, New, and an expandable
Search icon. Command-F expands and focuses search; Close or Escape clears it
and restores the icon. Phones keep pill tabs and the header search.
With enable-quick-calls enabled, New call opens a menu with Start an instant call, Call a channel or contact, and Manage call links; without the flag it
opens the recipient picker directly. Start an instant call opens /app/meet/new
without creating a meeting, the same setup reached from New Call beside
Calendar's New event or Create → Call (C C). Scheduled calls are created
through Calendar and can be shared with people who do not have a Macro account.
The channel/contact option opens the recipient picker. Starting a channel call
connects the creator without waiting for recording, transcription, or recipient
notification delivery. Verify that a second participant still receives the ring
and can join, and that leaving immediately does not leave a recording running.
Recordings, transcriptions
and summaries appear here; empty state notes "Calls are available to agents."
Opening a recording uses /app/calls/call/<callId> inside the Calls view,
with one breadcrumbed header (Calls > <recording name>). Choose Calls to
return to the list with its search, filters, focus, and scroll position preserved.
The desktop sidebar remains available; choosing a view or filter, or focusing
search, returns to the list. Phones show the same detail and return breadcrumb
instead of switching to Drive. Shift+Enter and Open in new split open
the recording in a second Calls view.
Old copied /app/call/<callId> links redirect to the Calls detail without losing
the transcript target. Existing /app/drive/call/<callId> links still work.
The detail shows a loading state, recording/transcript/summary, Share, and a call
side panel below the breadcrumb header; a failed load shows Retry.
While the call is in progress, a Join call button under the title joins it
(desktop and phone); it is hidden once you are in that call.
call_transcript_id=<segmentId> seeks the matching video segment after loading.
Check a direct link, both old link formats, a Calls-list click, a second split,
the breadcrumb return, browser Back/Forward, and clicking the same transcript
search hit twice after playing elsewhere. On phones, recorded call headers omit
Call Again.
Imported Granola meetings
Adding Granola in Settings → Agent connections (Pipedream Connect, Granola
Business or Enterprise API key) is the only setup; there are no sync controls.
Within about 30 seconds the backend registers a Granola webhook at the widest
scope the key allows, and removing or disabling the connection stops sync. Notes
whose first summary is generated, edited, or shared after that are imported as
private calls about a minute after Granola finishes the summary, and appear in
Soup lists without a refresh; history is not backfilled. Imported calls appear
in All and Attended, never in a channel's Calls tab, and open in the
normal call detail with title, summary, attendees
(shown as guests), and transcript but no recording. Rename and delete do not
apply to imported calls yet. Webhooks require a public HTTPS cognition callback origin (CognitionPublicUrl);
on a laptop stack, expose the webhook path with a tunnel such as Tailscale Funnel.
A channel's Calls tab lists that channel's recordings with the same rows, filtered
by the channel id. Its search field matches call names and transcripts in that
channel.
The desktop Chat sidebar lists every live channel call and quick call in a Live
section above the conversations. Each row reads Join, or Open when you are
already in that call, which returns to the channel's Call tab. A channel call that is
still ringing for you also shows a Dismiss button, which declines it like the
conversation row's Decline. To see the section
without starting a real call, answer /call/active and /call/<channelId>/active
with a fake call through CDP Fetch interception.
Calls whose discussion is a channel thread
With the enable-call-channel-thread server flag on for the caller, a new call in a channel stores
channel_thread as its discussion, and CallRecord.discussion says so. Past channel calls, calls
already running, and calls with no channel keep call_chat, and behave as described elsewhere here.
In the channel, the call is a row at its start time: <name> started a call, the call time, live
avatars and Join (or Return to call), with the thread collapsed under it, which replies like any other thread.
When it ends the line says how long it lasted. While the live row is
off screen, the banner above the composer shows a message count and scrolls to the row.
In the call, the panel opens on desktop and tablet, closed on phones. Its first tab is the channel's name. It shows the channel up to the call's row, opened on the blank slate when the thread is empty and at the newest message otherwise. The composer is pinned to the call thread and returns there after replying elsewhere; nothing posts top-level from the panel. A popup counts top-level messages others have sent to the channel since you joined, and View swaps to the Messages tab with the call still connected. On the meeting page it navigates to the channel.
People connected to the call get no notification from its thread, mentions included; they stay followers, so later replies reach them after they leave. The call's root accepts replies and nothing else: no edit, delete or reactions. On a call's record the chat is read-only with Open in channel, and absent for anyone who can't read the channel. Deleting a record leaves the thread in the channel.
To verify, turn the flag on for your test user in PostHog, start a call in a channel from one account, and open the channel from a second. Check replying from each side, a quote reply inside the thread, that no notification reaches the person in the call, and that ending the call updates the row.
While you are in a call, a green phone button (Return to call,
data-sidebar-next-item="active-call") sits at the bottom of the desktop rail,
above Settings. It opens the channel's Call tab, or the meeting page for a quick call.
In the native iOS call drawer, the horizontal participant row excludes the person shown in the large video. While holding or scrolling the row (including momentum), the displayed primary and row membership stay fixed; speaking indicators still update. The latest primary and membership update together after scrolling settles, preserving a surviving participant's position where possible. Verify that dragging does not pin someone, tapping pins the displayed person, and a participant who leaves during a held touch cannot be selected. Exercise speaker changes and departures during row gestures on a physical iPhone as well as the simulator.
Leaving a native iOS call is final. The drawer's Leave and CallKit's end button both end the CallKit call, its LiveKit room, the drawer and PiP, even when the native session has already lost track of the call. PiP and the drawer appear only while a call is active, so restoring a PiP left over from an ended call dismisses it instead of opening an empty drawer. A call the user left is never rejoined automatically: a native snapshot that still reports it is ended natively, and only tapping Join in that channel lets the call back in. A CallKit answer handled more than 60 seconds after it was fulfilled is dropped rather than joined. Verify on a physical iPhone that Leave from the drawer, from the lock screen, and right before backgrounding the app each end the call without a PiP or drawer returning, and that tapping Join afterwards still rejoins a call that is still running.
Native call logs go to the unified log (subsystem: the app's bundle id,
category CallKit) at notice level, so they survive on the device. Collect
them from a connected iPhone with
sudo log collect --device-udid <udid> --start '<time>' --output calls.logarchive
and read them with log show --predicate 'category == "CallKit"' calls.logarchive.
They never contain identities, names, or device names; participants appear
as LiveKit SIDs. The app's call_action analytics record callId on joined
and left, what started each join (trigger: user, deep_link, restore,
auto_rejoin), and why each leave ran (leaveReason: user_initiated,
native_ended, join_cancelled, stale_native_session).
If a recording fails to play, reload the page to obtain a fresh recording link, or use Open or download recording. The playback warning does not assume that the failure is caused by an unsupported media format.
Where a call shows the block header's "…" menu (Rename, Delete), that menu
also offers Download when the call has a recording. It saves the recording
under the call's name with the recording's extension (<name>.mp4), through the
same download flow and confirmations as Drive files.
Call links and guests — /app/meet/join/:shareToken
These routes require enable-quick-calls for both signed-in users and guests.
In Calendar, create an event with Macro call selected (the default).
The composer waits for the quick-call flag to load before choosing its default.
Saving creates the call and includes its link in the invitation;
the room starts on the first join. Use Calendar to edit the event or invite guests.
Teammate rings require a live call; selecting teammates during new-call setup
sends invitations after the call connects.
New call → Manage call links lists your standalone links with Join call, Copy link, and Revoke link. Revocation prevents new joins; it does not delete calendar
events or disconnect current participants. Each active channel call also shows its
URL and Copy link. A channel call's link stops working when that call ends.
Guests can use standalone meeting links without a Macro account. Links to channel
calls only admit signed-in Macro users; visitors without an account see a sign-in
prompt instead of the guest name form. Inside a channel call, the shareable link is
created on request via Get shareable call link.
New calls use /app/meet/new; shared links open setup at
/app/meet/join/:shareToken. A successful connection replaces the URL with
/app/meet/:shareToken without restarting the call. For signed-in participants,
hangup opens the call record when the server confirms the call ended (the last
participant left). Leaving an ongoing channel call opens its channel; leaving
an ongoing scheduled call opens Calendar. Ongoing instant calls return to Calls.
Guests return to Macro without opening a private call record.
An unexpected disconnection returns to setup so the user can retry.
Opening or reloading an in-call URL returns to setup and requires a deliberate
join; existing shared links continue to work.
Guests enter Your name, choose their microphone and camera preferences, and
press Join call. Setup requests microphone permission and waits until that
prompt finishes before requesting the camera, then previews video locally;
sharing starts only after joining.
Permission denial leaves the affected device off and still allows joining.
Shared-link setup shows the people currently connected, with avatars, names, and
an attendee count. It refreshes every 15 seconds while setup is open; guests see
this only for standalone links. Empty calls show No one else is here yet; a
failed roster request leaves joining available. Transcription agents and past
attendees are excluded.
The preview and full-width join button retain their size while joining. The call runtime preloads while setup is open. New-call setup also reserves an empty room, without starting a meeting, recording, or invitations. Leaving setup cancels that reservation; abandoned rooms expire after five minutes. Starting still works if preparation fails or expires. Entry waits for the room connection; teammate invitations continue afterward. For a newly started call, transcription and recording start in the background instead of delaying join credentials. Copying the meeting URL is available after joining, in the in-call header.
The creator presses Start call; invitees press Join call. Loading the page or
completing authentication never joins automatically, including old ?join=true
URLs. Back to Macro exits setup.
Channel-linked calls require sign-in. While authentication is loading or the
viewer is signed out, setup must not request microphone or camera access; the
guest name form is available only for standalone meetings.
The call page shows a recording/transcription notice. It uses the normal call controls
for audio, video, device selection, screen sharing, and effects. Leave call uses
the destinations above after the server confirms whether the call ended.
Check channel, scheduled, and instant calls with another participant remaining
and as the last participant, including at phone width. During a delayed leave,
the page shows Leaving call… without flashing setup; navigating elsewhere must
not be undone when cleanup finishes. Inline channel call controls return to
Messages on leave and stay in the channel, even when that hangup ends the call.
Copy Meeting Url is available during the call.
Rejoining from a new page waits for the prior page's pending leave cleanup before
requesting another connection, so a slow leave cannot disconnect the replacement.
Leaving the last participant archives the session first and tears down its media
in the background, so the next call does not wait for that room to be deleted.
It keeps its label and shows a checkmark for a few seconds after copying, then
restores the copy icon.
Guest access is limited to the call room and its live text discussion; joining does not expose the channel or grant anonymous access to saved transcripts and recordings. Guest names are preserved in the host's call history. Signed-in attendees receive access to that session's saved call without gaining access to the channel.
The join screen, in-call participant tiles, and incoming direct-call badges use
profile pictures; initials are the fallback when no photo is available.
In-call participant tiles fill their grid cell but are never wider than 16:9,
so a wide window centers them instead of cropping cameras; check a single remote
participant in a wide window and at phone width.
Participants with the LiveKit macro.program attribute show an Agent badge
beside their name on video tiles, screen shares, and in the Participants list,
including on phones.
The join screen has microphone, camera, and background effects buttons over the
preview, with pill selectors below for microphone, speaker, camera, and
backgrounds. The background button over the preview toggles the selected effect
off and back on; when no effect has been selected, it enables Strong blur.
Backgrounds use a simple menu with None, Light blur, Strong blur, and image upload
(JPG, PNG, or WebP, up to 10 MB). Dot icons distinguish the two blur strengths.
Selected devices and backgrounds carry into the call; unsupported browsers use
the system speaker. If a background cannot be applied, the camera stays off
until the user retries or chooses None. The screen uses a gray join
button. During a desktop or tablet call, Copy Meeting Url sits at the
bottom-left; narrow panes show only its copy icon. Active phone calls fill the
available viewport, retaining header islands for Back and Copy Meeting Url.
The header shows the current local time before the call name. Owners can click the name
to rename it, then Save or press Enter; Cancel or Escape discards the edit. Guests and other participants see a
read-only name.
Join-preview and in-call controls use the standard Macro icon buttons. In a
call, a fully rounded toolbar contains the controls. The microphone and camera
are split buttons (ButtonGroup): the left half
toggles the device, with a failure-colored slashed icon when off, and the caret
opens a settings menu above the toolbar on click only; hovering opens nothing.
Audio settings lists microphones, speakers (when the browser can choose one),
and a noise suppression switch with its label on the left.
Video settings lists cameras and the background effects as tiles: None,
Light blur, Strong blur, a selected custom image, and Upload. Screen share is
also a split button: the left half starts or stops sharing (pressed while
sharing), and Screen share settings holds Share audio, off by default,
saved per device, and locked while sharing. With it on, the browser picker offers
tab audio (and system audio where Chromium supports it), and other participants
hear it alongside microphones, even away from the Call tab. Leave call is a
separate button. Live channel calls also include Call sharing in the toolbar:
its menu offers Team sharing and Private, each with a short explanation
and a checkmark on the current choice. The icon changes between team and lock.
Audio settings, video settings, screen share settings, and call sharing use
bottom drawers on phones, with a handle and scrollable options; desktop and
tablet keep dropdowns.
The sharing icons align with the option titles, with short descriptions below.
Click outside or press Escape to close and return focus to the opener. The
controls also work by keyboard and touch.
The floating mobile New action is hidden while the call view is open and
returns when you leave the call view. Phone calls also hide the app's bottom
navigation and channel Invite action, but keep the channel header island visible.
Invite returns when you leave the call tab, including in the block-hosted channel
header; Invite remains available on setup screens, desktop, and tablets. Back
returns to the app without hanging up; when a channel has no navigation history, Back opens its
Messages tab instead. Only Leave call ends participation.
Focus is unavailable when you are the only participant. Otherwise, click or tap a participant, including your own tile, to focus them. Focusing someone else keeps your own tile in the small picture-in-picture window; focusing yourself moves the remote participant grid into that window instead. Tap a tile in the small window to switch focus, or use the solid Back to grid button on the focused tile to restore the grid. If that participant leaves, the grid returns automatically. Focus changes keep the existing video tracks mounted. A talking participant has an accent-colored border above their video or avatar.
While someone shares their screen, Maximize screen share at the share's top-right hides the participant strip so the share fills the call area, and Show participants brings it back. Video tiles stay mounted and audio keeps playing. The choice lasts while the call view is open, so a later share also opens maximized; check it on desktop and at phone width, and when the share stops.
Open Chat and Participants from the button beside the media controls. The sidebar and phone drawer share a compact grouped section switcher at the top. Participants shows the live attendee count and a scrollable roster, including you and connected guests but excluding recording agents. Rows show names, avatars, microphone and camera state, and a speaking indicator. Off microphones and cameras use the failure color. Known users use the shared user icon: hover it on desktop or tap it on touch to open the profile card; guests use the shared avatar fallback. This is the current call roster, not the channel member list. Participant media controls remain read-only. The roster remains available when chat is unavailable, without starting message queries.
On phones, the fully rounded control bar fits its buttons instead of filling the
available width. Controls have 8px gaps, expanding to 12px in roomy bars and
contracting on narrow phones so all controls fit. The sidebar button stays
separate on the right with a 48px tap target and the row keeps its side gutters.
On phones at most 416px wide, the sidebar button moves below the bar so the
additional screen-share settings control fits without clipping. Controls wrap
on smaller available widths without shrinking their split-button segments.
On desktop, the sidebar button stays at the bottom-right and Copy Meeting Url
stays at the bottom-left, without horizontal padding on the footer row. On
phones, Copy Meeting Url uses the shared CopyButton in a standard 40px
header island, without custom button colors or sizing. Media controls occupy a
separate row below the video, never over it. Controls remain visible while idle;
auto-hide is disabled for now. Header islands also stay visible. Check 320px
phones, safe-area insets, and rotation.
In wide desktop panes, the sidebar fills the call content height alongside the video and controls, with a rounded, raised background. Drag its divider, or focus the divider and use the arrow keys, to resize it between 280px and 480px while leaving at least 320px for the call. It starts at 360px and retains its resized width when closed and reopened. Narrow desktop panes overlay the sidebar; phones use the shared bottom sheet instead of a resize handle.
Both presentations have a Close chat and participants button beside the tabs. Dismiss the sheet with that button, its handle, backdrop, or Escape; desktop also closes with Escape. Opening and closing animate unless reduced motion is enabled. The desktop sidebar stays anchored to the right edge and closes to the right, without crossing the call area. Closing returns focus to the footer button. Switching tabs, closing, and resizing preserve the message draft and scroll position. Tab changes keep keyboard focus on the selected tab instead of moving it into the composer; reopening retains the existing autofocus behavior. Message hover actions stay within the chat's scroll viewport. The toolbar wraps its action groups when the sidebar is narrow, keeping the final actions inside the visible surface. Check the first and last visible messages while scrolling, with every action available. Check both signed-in and guest calls.
In the macOS desktop app, Screen share opens Macro's own Share your screen picker (screens first, the main display preselected, then open windows), since its Chromium has no system picker. Share publishes the chosen source; Cancel leaves sharing off. Without macOS Screen Recording access the picker says so and macOS shows its prompt; the user reopens Macro after allowing it. A refused or failed capture shows its reason under the call controls. Browsers and older desktop builds keep the browser's own picker. Verify on a Mac by sharing a display and a window, stopping, and cancelling the picker.
Programs in calls
An agent account joins with its own API key through the SDK. Starting a channel
call uses POST /call/{channel_id}; joining an existing call uses
POST /call/record/{call_id}/join, which never starts one. Meeting joins use
POST /call/meetings/join/{token}. When only programs have remained in a call
for 60 seconds, the call ends automatically.
Work in a call
Behind enable-agent-work, the call panel gains a Work tab, after Chat and
Participants, while any other participant has registered work you can open.
Chat stays the default tab. Each participant with work gets a section; rows keep
their order, and clicking one opens the session in a new split so the call stays
live. Registering is SDK-only (session.registerAsWork()).
A dot marks the Work tab while you're elsewhere and the panel button while the panel is closed. A View active work prompt with the participants' pictures appears above your video tile when someone's work first shows, for eight seconds or until dismissed; clicking it opens the tab. It belongs to the call rather than the toast system.
Browser call diagnostics
Browser OpenTelemetry requires enable-browser-otel (or
VITE_ENABLE_BROWSER_OTEL=true) and a configured exporter. PostHog deliberately
drops events on private call-link routes; it is not a substitute for these traces.
Existing call_action, audio-processing, and receiver-health analytics describe
other parts of the call, not waiting-room permission outcomes.
Find meeting.join by call.id, then use its meeting.setup.id to find that
page's earlier call.media.capture spans, including guest attempts. The setup ID
is random and scoped to the page owner; it is not derived from the share token.
Each capture records the device, whether it was enabled, the trigger, outcome,
and whether the captured stream was retained. Camera permission can succeed
while its toggle remains off. A pending request cancelled by navigation ends
with cancelled; a camera constraint fallback emits call.media.constraints_retry.
Join records final meeting.join.microphone_access / camera_access, enabled
flags, and whether each live preview track was handed to the call.
Failures include an allowlisted error.type: NotAllowedError or SecurityError
indicates blocked access (browser, OS, or policy), not proof the user explicitly
clicked Deny. NotFoundError, NotReadableError, and OverconstrainedError
help distinguish missing devices, capture failures, and unsupported constraints.
Unknown provider errors are redacted. Raw error messages, device labels/IDs,
guest names, and bearer URLs/tokens are not attributes.
call.connect and background call.media.setup are children of the join flow.
call.media.publish_prejoin, enable, and toggle expose publishing/capture
failures after admission; enumerate and background cover waiting-room
device lists and effects. call.media.screen_share records which picker ran
(native or browser), Screen Recording access, the source count and kind,
and whether the user cancelled; failures add the underlying
call.media.screen_share.error_type. A completed join/setup does not imply every device
worked: inspect its media children. Later toggles and connection-state samples
are searchable by call.id. call.connection.disconnected records the SDK's
numeric reason when available. These spans cover the browser LiveKit path,
not the native CallKit media implementation.
Verify allowing and blocking each device, joining with both off, granting access on retry, and leaving while a prompt is pending. Confirm setup and join share the setup ID and that media failures remain visible when join succeeds.
Sharing a call
With quick calls enabled, channel calls use the same Copy Meeting Url button as instant and scheduled calls. Clicking it creates the share link and copies it; opening the call tab alone does not create a link. If loading fails, click again to retry. If clipboard access fails, a selectable URL appears below the button.
A channel call's Share dialog has a Team access control (None or View) for the same canonical
team share. Its side panel has a Sharing section with one Share with team checkbox.
While a call is live, the controls bar instead has a Call sharing dropdown with
Team sharing and Private options. Each option explains the resulting team
access under its name; choosing the current option does not save again. Controls
are disabled while connecting or saving. Team sharing is canonical view access
(the same Team access model documents and AI chats use), enabled by default for
channel calls. Any participant with edit access can change it, and other
participants see it update live. When the call ends, Team sharing lets the
creator's team open the recorded call, read the transcript and AI summary, and find
it under Calls and in search; Private grants no automatic team access.
Afterwards only the call's creator can change it; everyone else sees the
side-panel checkbox read-only with a note saying so.
Team sharing is independent of channel access and of link sharing.
Standalone instant and scheduled calls are excluded from team memory. They have no
team-sharing or Team access controls during the call or on the saved recording.
Signed-in participants keep direct access to their recordings, transcripts, and summaries;
joining a standalone call never makes its content available to the wider team.
Android native channel calls
Android channel calls use a native call activity rather than browser media. After joining, the themed drawer shows a large participant tile and a horizontally scrolling participant strip without the transcription agent; tap a strip tile to make it primary. Speaker toggles speaker mode (hold it for headset/Bluetooth routing), Mute and Video control capture, and Leave ends the call. The local primary video tile exposes Switch camera. Swipe the drawer handle down, tap outside the drawer, or use Back to shrink it to a thumbnail over Macro, as on iOS: tap it to reopen the drawer, drag it to another corner, or drag it past a side to tuck it away (an edge tab brings it back once someone else is in the call). Leaving the app continues the call in system PiP (you and the active speaker); tapping PiP shows Android's menu with Mute, Leave and expand, which reopens the drawer. Open call controls in the web call controls also reopens the drawer. Leaving the channel does not end the call. While ringing, a locked phone opens a full-screen incoming-call screen when permitted, with caller initials/name, channel context and large Answer/Decline controls. Back hides this screen and leaves the call available in its notification. Incoming calls also expose Answer/Decline in the Calls notification channel, including while locked/backgrounded. When full-screen access is unavailable, the notification remains usable; Answer opens the call screen directly for microphone permission and retry errors. Verify allowed/denied full-screen access, missing microphone permission, cancellation/expiry and stale notification actions after a replacement call arrives. While Android 14+ blocks full-screen notifications, a toast offers Allow (system setting) or Dismiss; returning to Macro with access granted removes it. PiP is a native, device-dependent flow. Browser-only tests cannot validate Telecom, FCM wakeup or background media; follow the hardware matrix in Android development.
Synthetic emulator captures: incoming screen, notification fallback, and microphone permission after Answer.
Native Android call spans use service android-calls and the opaque call.id.
The existing telemetry gate also controls cold calls. W3C context connects the
push producer, notification/activity, permission and answer phases, and status
HTTP requests; connection and cancellation outcomes end the incoming trace.
For local collector verification and the exporter fixture, see
native call tracing.