Choose how customers will reach Sondel.

Start with the customer entry point

Choose where the conversation will appear and what your team can configure. Current support depends on your tenant and use case. Confirm each required route, credential, identity check, permission, confirmation, and handoff before launch.

Website widget

Put the conversation on your own site. You need a configured tenant, permitted site origins, reviewed sources, an identity method, and a working handoff destination.

Server API

Use your own customer interface. You need scoped server-side credentials and an interface that preserves identity, permissions, confirmations, sources, and handoff states.

Task specification

Import an OpenAPI specification as a starting point for task declarations. You must still review the operation, credentials, identity, permissions, effects, and confirmation response before testing it.

Know the current limits

These paths exist in the reviewed app source. A source review does not prove that your production setup or task is ready. It also does not promise every route, region, service level, or connector. Confirm current support before you plan a launch.

No named helpdesk connector is claimed as available here. A generic HTTP API is different from a supported native connector or marketplace listing. Sondel will name an integration after its setup and limits have been verified.

Read the Agentic CX guide for the difference between an answer-only chatbot and an approved support action.