Meet Support Playbook

Use this playbook when support staff investigate Meet cases. It is for internal investigation guidance and should not be pasted directly to customers.

Classify the case

Common Meet categories are room access, participant identity, camera failure, microphone failure, speaker output, echo, screen sharing, captions, translation, mobile layout, and meeting recording control.

Minimum safe context

Collect the meeting room link or name, workspace ID or name, affected account email, browser, operating system, device type, approximate time, source and target language if relevant, and whether the issue affects one participant, one room, one workspace, or multiple tenants.

Investigation order

Check room access first, then participant connection, then local device permissions, then network symptoms, then caption state, then translation state, then recording control or post-meeting handoff to Record.

Customer-safe answer shape

Explain the likely visible cause, give one or two customer actions, ask for missing customer-safe details, and set expectations for captions or translation quality. Do not expose provider names unless already public, provider credentials, raw vendor responses, internal logs, private participant metadata, or unsupported claims about language accuracy.

Escalation

Escalate to engineering or an owner/action-capable admin when many rooms are affected, media connection failures spike, caption or translation provider health appears degraded, privacy or consent is disputed, or support needs access beyond ordinary room metadata.