## TL;DR

If users report they cannot join a live room, check whether max_participants is set too low - remember the face consumes one slot. For 1:1 calls leave room for exactly the human plus the face.

## Fix

1. If users report they cannot join a live room, check whether max_participants is set too low - remember the face consumes one slot.
   Expected: You see the expected output instead of the problem.

## When to use

- You are setting up or using this Tavus max_participants counts faces feature.
- The symptom matches: the replica takes a seat.

## When NOT to use

- Unrelated Tavus max_participants counts faces issues (different feature, different failure).
- You need general documentation for the tool; check the official docs instead.

## Compatibility

Reported against Tavus max_participants counts faces.

## Variant phrasings

### the replica takes a seat

## Why it happens

Tavus max_participants limits room capacity, and faces count as participants (official docs). With max_participants: 2 you get one human participant plus one face - the replica itself occupies a seat. When the limit is reached, additional users cannot join. Set it when creating the conversation: POST https://tavusapi.com/v2/conversations with pal_id, face_id, and max_participants.

## Edge cases

- If your error message differs even slightly, this is probably a different issue; search the exact text.
- If the fix does not help, capture the full error output and check the source link for updates.