> ## Documentation Index > Fetch the complete documentation index at: https://docs.famulor.io/llms.txt > Use this file to discover all available pages before exploring further. # Translate > Run a live interpreted conversation between two people, on the web or by phone **Translate** connects two people who speak different languages. Each person hears the other person's translated speech in their own language. For example, Tobias speaks German and Aleksandra speaks Polish: Tobias hears German, and Aleksandra hears Polish. Translate must be included in your current plan. The assistant editor keeps every engine mode visible; a locked mode opens its description and a link to the Plan page. The same workspace plan rule applies when rooms are created through the API or MCP. ## Prepare a conversation 1. Open an assistant and choose **Settings → Engine mode → Translate**. 2. Choose the spoken language and translation voice for both speakers. **Speaker 1** is the workspace user starting the conversation; **Speaker 2** is their guest. 3. Select **Open translation room**. The room opens in a new tab. 4. Choose how each person will participate, invite your guest, and select **Start conversation**. Translate uses its own language and voice settings. Prompt, flow, tools, knowledge, memory, and ordinary assistant conversation settings are hidden in this mode. Their saved values remain available when you switch back to another mode. The **Assistant status** switch and **Delete assistant** stay at the end of the settings, as in the other modes. While the assistant is inactive, no translation room can be started or joined. ## Choose voices The voice selected for a speaker represents that speaker in the **other person's language**. If Tobias is Speaker 1, Aleksandra hears the Speaker 1 voice speaking Polish. Tobias hears the Speaker 2 voice speaking German. Use an available library voice or an authorized [workspace voice clone](/assistants/voice-cloning-consent). The picker shows voices compatible with the listener's language. A private workspace voice can speak to a guest without giving that guest access to the voice library or the clone itself. ## Web and phone participation | Option | What happens | | - | - | | **Web** | Join from a browser using a microphone and headphones. | | **Call** | The host enters the person's international phone number. Starting the conversation calls that person. Either or both speakers can use a phone. | | **Dial in** | With an active incoming number connected to the translation assistant, Speaker 1 can start the room, call that number, and enter the displayed six-digit room code, including any leading zero. | **Call** requires a connected outgoing number. If none is available, call controls remain disabled. **Dial in** uses the incoming connection independently and does not require an outgoing number. Choose the country beside each destination number; the field includes its international dialing code. The guest can use Web or Call with any of Speaker 1's three options. For dial-in, the assigned number is shown while you prepare the conversation. The six-digit code appears after you start the room and remains visible beside the number. Code entry has a 30-second window, including the spoken prompts, with at most three incorrect attempts. Entering the correct code before the room starts does not use an attempt; the call explains that the host must start the room first. Each speaker uses one audio connection. When a person participates by phone, their browser becomes a transcript observer with its microphone and sound off. Leaving browser audio does not hang up a phone connection. The host can end the whole conversation with **End conversation**. Use headphones for browser calls. If the browser blocks playback, select **Enable translated audio**. If microphone permission is denied, allow it in the browser's site settings and try joining again. ## Invite a guest The host can copy a private invitation link or send an invitation by email. The guest does not need an account. Share the link only with the intended conversation partner. Guests can join their assigned side and read the live transcript. They cannot change the languages or voices, place phone calls, send invitations, or end the whole conversation. A guest joining before the host starts sees a waiting screen. ## Follow the live transcript The room displays each speaker's **Original** text beside its **Translation** as completed phrases become available. A browser can follow the transcript while its owner talks on the phone. Reconnecting reloads available conversation segments. Completed original and translated phrases are saved in **History** when the room ends. Open an active Translate entry from History to return to its live room. Translate does not play the other person's original audio. If translation cannot continue, the conversation reports the interruption instead of forwarding untranslated speech. A room that was opened but never started stays in History as **Queued** for up to 5 hours and is then closed as **Failed**. To close it sooner, open it from History and select **End conversation**. Deleting the assistant also ends its rooms that nobody is in; while a conversation is running, end it before you delete the assistant. ## Recording and consent Enable **Record calls** in the Translate assistant settings when you need an audio recording. Recording starts automatically when **Ask both speakers for consent** is off. When consent is on, each person first hears a recording notice in their configured language and answers verbally. Recording starts only if both people agree. If either person declines, the room follows the configured choice to continue without recording or end the conversation. The saved audio represents Speaker 1's side of the interpreted conversation: Speaker 1's original speech and the translated audio heard from Speaker 2. History shows the recording alongside the bilingual transcript when it is available. ## Usage and charges One shared conversation minute uses the normal voice rate plus the **translation surcharge** once. Having two speakers does not double this shared charge, and transcript observers add no charge. Phone participation adds the applicable carrier charge for each actual phone connection: none for web-to-web, one for web-to-phone, and two for phone-to-phone. Separate attempts can create separate carrier charges. With your own carrier connection (BYOC), carrier charges remain with your carrier; the conversation's voice and translation credits still apply. Your workspace's current rates are shown in **Usage**. Normal workspace credits and call limits apply to Translate. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.