Skip to main content
Answers to common questions about setting up Famulor’s AI voice assistants, phone numbers and call latency, pricing and compliance, and white-label or enterprise use.

Getting started

Famulor is built for teams automating inbound or outbound voice work with AI — from a straightforward appointment line to a multi-step qualification and transfer flow. See Assistants for the range of what one assistant can do.
No — you can build an assistant from the dashboard with a system prompt or the visual flow builder, and connect it to your other tools through Automations, all without writing code. For deeper integrations, the REST API and MCP endpoint are available when you need them.
Yes — you can connect a CRM or other app as a reusable Automation connection, connect a scheduling provider under Calendar & booking so assistants can book mid-call, give an assistant a callable tool from Agent Tools, or connect an external MCP server for a whole toolset in one step.

Phone numbers & telephony

Yes — you can bring your own SIP trunk to keep your existing numbers, import numbers in bulk from a supported carrier, or buy a new number directly in the platform.
Latency is shaped mainly by your assistant’s engine mode: Realtime is the fastest, Pipeline trades a little speed for the most control, and Half-Cascade pairs realtime listening with the voice you choose. Network quality and prompt or tool complexity also affect latency, so test with a real voice call before going live.
Yes — concurrency and daily call limits both scale with your plan. These are two different limits: see Outbound call limits for the daily cap and how to request an increase, and Concurrent Lines for how many calls can run at once and the paid add-on that raises it.

Pricing & compliance

Usage is billed from a prepaid credit balance: your plan includes credits that renew with each billing period, and top-ups cover anything beyond them. See How usage is billed for exactly what a call consumes and how it’s charged.
Famulor gives you the controls: a configurable consent announcement and recording toggle, universal or per-channel opt-outs and suppression lists, data retention windows, and quiet hours per channel. Final legal and regulatory validation for your jurisdiction and use case should still go through your own legal/compliance team.

Enterprise & white-label

Yes — any workspace can be granted the white-label entitlement to run under its own domain, branding, and pricing, and resell to its own customers. See White-label administration.
Yes — enterprise plans can include dedicated support channels and SLA commitments. See Support → Enterprise support for what’s included and how to get started.