Agent Cycle™.
Build it. Run it. Make it better.

Technical capabilities / verified September 14, 2026

Conversational management.
Detailed technical control.

How you issue an instruction and what the platform can configure are different questions. A plain-language request can result in a precise change to a voice, timing threshold, tool or integration. You can specify the outcome you want, name an exact supported setting, or write an API request. The available controls depend on the engine, voice provider and interface.

The controls behind the conversation

The public Update assistant API documents concrete configuration fields. These extend beyond prompts and model selection.

Latency tuning involves more than choosing a model. Engine mode, transcription, turn detection, synthesis, tool response time and prompt design all affect the experience. Luna and Terra are listed model options; they are not the platform's only tuning mechanism. Model availability varies by engine and plan. A sensitivity value is not a promise of a particular end-to-end response time in milliseconds.

Yes: SIP trunking, two-way DTMF and warm transfers

• SIP trunking: connect a supported carrier or PBX using a phone number or extension. Bring-your-own routes support inbound and outbound calling, with carrier routing and authentication configured for the connection.
• Receive DTMF: the Collect keypad input tool captures digits entered by the caller, such as a reference number or menu selection.
• Send DTMF: the separate DTMF input tool lets the assistant send keypad digits to navigate an IVR or enter an extension.
• Warm transfers: the assistant can hold the caller, call a human recipient, brief them using configured summary instructions, and connect the call. Hold audio, briefing and connection messages are configurable.

For a SIP warm transfer, the outbound route must work with the outbound proxy disabled. Reusing the same number requires sufficient carrier concurrency for the additional call leg; a different outbound number can be used. Cold transfers use SIP REFER and require carrier support. These are configuration requirements for supported features.

Use plain language. Or use the API.

An operator can ask: “Review the calls where the agent interrupted the customer, inspect its interruption settings, propose a targeted change and test it.” A developer can inspect the configuration and update supported fields directly at PUT https://app.supported.tech/api/user/assistant/{id}.

This illustrative request body adjusts four settings on an existing compatible pipeline agent. Values should be selected for the actual voice and use case, then tested.

{
  "speech_speed": 0.95,
  "voice_stability": 0.7,
  "interrupt_sensitivity": 0.5,
  "min_interrupt_words": 3
}

Agent Cycle is the workflow for inspecting, changing, testing and verifying the result. It does not mean every casual request automatically retrains a model or triggers a complete rebuild. Connected accounts, permissions, compatible settings and explicit test steps still determine what can be executed. A successful configuration update and a successful real-call test are separate pieces of evidence.

Compare the actual engineering requirement

Retell documents a custom LLM WebSocket for exchanging live transcripts and generated responses with your own server. That is a specific integration capability worth evaluating. It does not establish that Supported.tech lacks API access or detailed voice controls.

Retell's own setup guide describes its service as managing acoustic interactions while your response system supplies the reasoning. A custom LLM connection is not, by itself, evidence of unrestricted access to the provider's underlying audio infrastructure.

For raw waveform processing, custom audio-buffer sizes, model-weight fine-tuning or self-hosted call infrastructure, require documentation for that exact capability. This page establishes Supported.tech's documented configuration and integration controls; it makes no claim of raw-audio access, identical feature coverage or universal performance superiority. Compare the endpoints, engine constraints and measured call results that your application needs.

Data portability & vendor choice · Updated 16 September 2026

Vendor lock-in and data portability.

Choosing an AI agent platform should include a practical question: what can you keep, retrieve and reconnect if your needs change? Here is the documented position, including the work a migration may require.

What portability covers

Your data and retrieved configuration can support a move. The Supported.tech software and underlying technology remain proprietary under section 12 of the Terms. Data ownership does not grant a downloadable copy of the hosted runtime, model weights or third-party voice licences. No universal one-click migration or identical behaviour on another platform is promised.

A practical exit path

1. Collect before closing. Contact describe@supported.tech about export before account closure. Retrieve the available configuration and records you need, and keep your original knowledge files and business records.
2. Reconnect and validate. Map prompts, settings and workflow steps to the destination. Reconnect your systems and credentials, then test calls, actions and handoffs before changing live routing.
3. Complete cancellation. Follow your accepted cancellation terms and review numbers, add-ons and other chargeable services separately. Turning off an agent does not cancel a subscription or release a chargeable number; accrued usage remains payable.

This is a summary of the current published documentation. Your accepted Terms, order, applicable retention settings and third-party provider requirements govern your account. Request export while the data is still available.