Skip to main content
This guide takes you from an empty account to a live conversation with your own AI assistant — no phone number required for the first test.
New to Famulor? Core concepts on the Overview page, and the full Glossary, cover terms like Assistant, Flow, Campaign, and Phone number used throughout this guide.

1. Create an assistant

1

Open Assistants and select New Assistant

The Create assistant modal opens. Enter a name your team will recognize, e.g. Reception EN.
2

Choose the agent type

  • Single prompt — free-form conversations from one system prompt (best for most first assistants).
  • Conversational flow — visual flow builder for branches, data collection, and transfers.
3

Pick a template (or build from scratch)

Use Build from scratch, or apply a catalog template (filter by theme). Templates copy into the system prompt and optional first message — they are not live-linked.
4

Edit greeting and instructions

In the editor:
  • Prompt mode: greeting + system prompt on the canvas. Use Choose template anytime.
  • Flow mode: open the flow builder; the base instructions live under Settings → General → Advanced prompt (also collapsed on the canvas).
A solid starting prompt:
5

Pick a voice and models — or keep the defaults

The defaults (a low-latency pipeline with a recommended voice) work well out of the box. You can browse the voice library later and preview voices before switching.
6

Save

Your assistant is now ready to take calls.

2. Test it in the browser

Every test runs your assistant exactly as saved — same prompt, flow, tools, and knowledge base. Select the Test button in the editor header and pick how you want to test:
  • Chat — a text-only session, no audio. The fastest way to get wording and logic right without speaking out loud.
  • Web Call — a live voice call in the browser, no phone number involved:
    1. Allow microphone access.
    2. Talk to your assistant. Interrupt it mid-sentence — it should stop and listen.
    3. End the call, then open History to review the transcript.
  • Call — a real phone call, available once the assistant has an outbound number or a verified caller ID (step 3). Enter your own number and the assistant rings you.
  • Simulations — an AI-played caller works through a scenario you define and scores the result; see Simulations.
A good progression: Chat first to settle the wording and logic, Web Call to hear timing and interruptions, then a real Call before you go live.
Web and phone test calls consume voice-time credits like any other call. A Chat test places no call. See How usage is billed.
Iterate on the prompt between test calls. Short prompts with concrete rules (“keep answers under two sentences”, “always confirm the phone number by reading it back”) beat long essays.

3. Put it on a phone number

Chat and Web Call already run the assistant’s real logic — once both sound right, move to an actual number:
  • Buy a number in Phone numbers and assign the assistant to it — inbound calls are answered immediately.
  • Or connect your own SIP trunk (BYO SIP) to use existing numbers.
  • Or verify a number you already own as an outbound caller ID — enough for the Call test and for outbound calling, though it does not receive calls.
With an outbound number in place, use the editor’s Call test to ring your own phone — the same telephony path a live call uses. For volume, set up a campaign; see Inbound & outbound calls for how calls reach and leave an assistant.

Next steps

System prompt vs. flow builder

When a single prompt is enough — and when to switch to a visual flow.

Conversation quality

Background audio, interruption handling, filler phrases, guardrails.

Knowledge base

Let the assistant answer from your documents.

Engine modes

Pipeline, realtime, and half-cascade explained.