Build your first assistant

You need an organisation owner or administrator account, a connected model provider, and speech providers for voice. Check billing for the balances required by your plan. A microphone test also needs HTTPS or localhost.

Choose a starting template

Open Build → Assistants → Create Assistant. Give the assistant a name, choose its type and select a suitable published template, or start with custom instructions. A template supplies a starting prompt; it does not connect provider accounts or publish the assistant.

For a first test, choose one small task: explain opening hours, collect a support request, or answer from one reviewed document. Add your actual business information before saving.

Connect your providers

Open your organisation's Integrations. Save the credentials for your providers and run Test saved configuration. Choose the model, transcriber and voice in the assistant editor. See provider setup for configuration and test requirements.

Provider invoices are separate from Sigsen credits and runtime charges.

Ground answers in your documents

In Knowledge, upload a file, wait for processing and inspect its extracted text. Select it for the assistant. Customer-facing sources also need Approve public use.

Choose Validated documents only if factual answers must pass evidence checks against reviewed sources. This mode needs a separate document review and Pipeline speech. Follow knowledge and reviewed answers, including a question whose answer is absent from the library.

Define behaviour and guardrails

Define the task, language, information to collect and when to clarify. Set the first message and timezone. Use the Visual preview to check expanded variables.

For required intake fields, configure a conversation flow. Instructions alone cannot enforce collection or authorize an external action.

Connect tools and MCP

Add only the required tools in Tools. Connect your organisation's integration credentials and select the published tool version or installed MCP operations. Test approval, refusal and success. See tools and approvals.

You can complete the first conversation without an external tool. Add booking or CRM actions only when their actual integrations are configured.

Choose channels and test

Select Save, then Talk. Talk uses the saved draft; save again after editing. Confirm microphone access, answers, interruption recovery and that End call releases the microphone.

Open Logs and inspect the revision, state, usage and tool failures. Evaluation suites repeat checks after changes.

Publish deliberately

Open Advanced → Versions and publishing → Publish to create a release. Saving alone does not update customer channels.

Connect a website widget, phone number or WhatsApp channel, then test from that channel. Use the production checklist before launch.