Phone numbers and calling

You need an organisation owner or administrator account, a provider-owned number, a published voice assistant and working model/speech credentials. Number rental and carrier usage are separate provider charges.

Connect a number

1. Open Integrations and configure an available telephone provider using your organisation's account.
2. Run Test saved configuration and confirm that the number belongs to that account.
3. Open Build → Phone numbers. Import an owned number or use the available provider purchase workflow. Enter numbers in E.164 format, such as a leading + and country code.
4. Select the published assistant for incoming calls and save the route.
5. Complete any provider routing or ownership requirements shown for the number. Saving a connection does not itself buy or provision a number.
6. Call the number from an ordinary telephone and review the resulting call log.

Telnyx and Vonage support purchase workflows where available. Africa's Talking numbers are requested through that provider's dashboard or support, then imported. Account eligibility, number availability and actual carrier routing need verification with your connected provider.

If credentials verify but the number does not ring into Sigsen, ask support to check the number's routing. Provide the number, provider, call time and timezone; omit credentials.

Place an outbound call

Enable outbound routing and the permitted destination prefixes on your route. Use Call, enter the destination and confirm the charge before starting. Use End call to stop it. The supported manual outbound workflow bounds calls to five minutes.

Outbound campaigns require an owned active route, a published assistant, E.164 contacts, a scheduled window and explicit charge confirmation. Pausing or cancelling stops future calls; calls already in progress continue. Interrupted dialing is recorded without automatic redial.

Transfers, capacity and privacy

Configure allowlisted transfer destinations and tools in the assistant. Transfers require caller approval and outbound routing. Validate warm transfer with a real operator before relying on it.

Phone, browser, API and WhatsApp voice share the organisation's concurrent-call allowance. Connecting and ringing calls occupy lines. An optional configured overflow route can send excess incoming calls to an allowed external destination; without successful overflow, excess calls end.

Recording and analysis require the configured spoken consent. Caller ID does not verify identity. Check billing, call logs and the production checklist before launch.