Last updated: Aug. 29, 2025
Getting great results often comes down to picking the right engine settings. Use this checklist when configuring a Famulor assistant.

1. Pick a Mode

ModeWhy choose it?Notes
Speech-to-Speech (Multimodal)Fastest turn-taking and most natural flowRecommended starting point. Try the Gemini 2.5 engine (beta) for the lowest latency, but note it’s experimental and may be less stable.
PipelineMaximum control over voice and long-form repliesIf you select Pipeline, continue to the Transcriber step below.
Want to know more about the differences? See the Assistant Modes guide.
Record the same scenario in both modes and compare response time and caller satisfaction.

2. Choose a Transcriber (Pipeline only)

TranscriberAccuracyLatencyBest for
Azure⭐️⭐️⭐️⭐️⏱️⏱️⏱️ (slower)Highest transcription fidelity
Gladia⭐️⭐️⭐️⏱️ (faster)Good all-rounder for most languages
Deepgram⭐️⭐️⭐️⏱️ (faster)Solid alternative—test which performs better for your language and audio setup
Different languages, accents, and background noise can affect each engine differently. Run a quick A/B test and keep the best performer.

3. Select an LLM Model

ModelStrengthsTrade-offs
GPT-4oSmartest reasoning, handles complex promptsSlightly higher latency and cost
Gemini 2.5-Flash-LiteBlazing-fast, still highly capableMay miss nuance in very complex tasks—test for your use case
If speed is critical, start with Gemini 2.5-Flash-Lite. For sophisticated reasoning, use GPT-4o and offset latency by shortening replies.

4. Noise Cancellation

If callers are on speaker phone or in a quiet environment, keep noise cancellation ON. If your call volume is low or some words are “clipped,” turn it OFF so the transcriber gets the full waveform.
If the assistant isn’t hearing you well, try turning noise cancellation off.

5. Conversation Timers

ParameterRecommendedWhy
Re-engagement≈ 30 sGives callers enough time to think. Lower values can feel pushy.
Max silence duration≈ 60 sPrevents premature hang-ups while still ending truly silent calls.
Test different values in real calls—too low can interrupt, too high leaves awkward gaps.

6. Initial Message

ModeHow it’s usedBest practice
PipelineRead exactly as written (converted by TTS)Write the greeting verbatim: “Hello, this is Alex from …”.
Speech-to-SpeechInterpreted as a prompt by the modelInclude instructions like “Greet the customer and say …” or prepend say exactly: to ensure literal output.

7. Ambient sound

Ambient sound adds subtle background noise to the assistant’s voice and is enabled by default.
If the assistant isn’t hearing you well, turn off ambient sound or lower the ambient volume.

8. Endpointing sliders

Control when your assistant starts talking with the endpointing sensitivity slider at the bottom of assistant settings.
SettingEffectUse when
Lower sensitivityAssistant responds faster after caller stops speakingYou want snappy, quick-turn conversations
Higher sensitivityAssistant waits longer before respondingCallers give longer, more detailed replies
If your assistant cuts off callers mid-sentence, increase sensitivity. If responses feel sluggish, decrease it.

9. Debug using the call transcript

1

Open Call history

Go to the Call history page in your dashboard.
2

Select your latest test call

Open the most recent call you placed for this assistant.
3

Inspect transcript and function calls

Review the transcript, function calls, and parameters to identify timing or logic issues.
Confirm the assistant is using the expected mode, model, and tools per your configuration.

10. Still have questions?

If you need help, contact our support team via the chat widget inside the app.