Sigsen documentation
Build, connect and operate voice and chat assistants in your workspace.
Start with one useful conversation. Connect your providers, give the assistant a clear task, test its answers and actions, then publish a version for your customers.
These guides cover your organisation's workspace and public developer APIs. You can follow the dashboard guides without writing code.
What would you like to do?
Build your first assistant
Follow the setup from a template to a successful test call.
Answer from your documents
Upload, review and test the sources your customers can use.
Connect your website
Publish a chat or voice widget and install its generated snippet.
Connect a phone number
Set up telephone routing and test real calls.
Connect WhatsApp
Verify your Business channel for messages, voice notes and incoming calls.
Add tools and actions
Assign published tools and test explicit customer approval.
Understand usage and billing
Learn how plans, AI credits and the USD usage wallet work together.
Build an integration
Use scoped API keys, browser voice sessions and signed webhooks.
Your path to production
| Stage | What to do | Ready when |
|---|---|---|
| Build | Choose providers, instructions, knowledge and tools. | Talk completes your task using the saved draft. |
| Test | Check ordinary requests, missing evidence and declined actions. | Your evaluation scenarios pass. |
| Publish | Create a release and attach it to a customer channel. | The channel uses the intended published version. |
| Operate | Review logs, outcomes, balances and delivery failures. | You can identify a failure and make a tested correction. |
Use the production checklist before inviting real customers.
Before you start
An organisation owner or administrator configures assistants, integrations and billing. Members have more limited access. Check the selected organisation before making changes: provider credentials, assistants and shared balances belong to that workspace.
Start with workspaces and permissions, or read how Sigsen works to understand the voice and knowledge pipelines.