01
Inbound, one-off test and controlled outbound calls
AiUse Voice AI
A Voice AI agent for SIP telephony
The phone agent is a separate implementation, not a mode of the web widget. It handles inbound calls or approved outbound flows only after the SIP settings, number ownership, consent rules and human handoff route are verified.
- Inbound, one-off test and controlled outbound calls
- Up to four SIP accounts with separate roles and policies
- Schedules, allowlist/blacklist, anti-flood, DNC/opt-out and human handoff
A WebRTC widget and a SIP agent are different products
A live conversation in the visitor’s browser over WebRTC — no phone number, SIP or PBX. A separate implementation for inbound and controlled outbound telephone calls.
| AiUse Voice AI Widget | AiUse Voice AI for SIP |
|---|---|
| Visitor’s web browser | Telephone network over SIP |
| A live conversation in the visitor’s browser over WebRTC — no phone number, SIP or PBX. | A separate implementation for inbound and controlled outbound telephone calls. |
| Learn more: AiUse Voice AI Widget | Learn more: AiUse Voice AI for SIP |
What the business receives
The manager receives qualification, contact details and a concise Telegram summary; the full conversation goes to email or an agreed CRM.
02
Up to four SIP accounts with separate roles and policies
03
Schedules, allowlist/blacklist, anti-flood, DNC/opt-out and human handoff
How launch works
Verify the carrier, codecs, authentication, routes and right to use the number.
Agree the script, operating hours, lists and immediate handoff conditions.
Run a closed telephone pilot on a controlled sample.
After acceptance, enable the approved flow and error monitoring.
Who this fits and when
Voice AI is useful when the same first-line questions recur every day, response speed affects the sale, and a manager needs context before joining personally. It is not a replacement for a negotiator: the agent handles first contact, routine explanation, qualification and a deliberate handoff.
By default the workflow retains a transcript rather than raw audio. Retention, recipients and deletion are agreed before launch; transcripts, phone numbers, emails, keys and RAG content are excluded from advertising analytics.
What happens inside the system
The voice interface is only the visible layer. Behind it sit speech recognition, the dialogue model, retrieval from the approved RAG knowledge base and speech synthesis. Each component can fail differently, so acceptance uses real questions and tests factual accuracy, response delay, language switching, contact capture and human handoff separately.
A knowledge base is not an indiscriminate copy of the website. We separate verified facts from promotional claims, remove stale prices, establish source priority and state what the agent does not know. Instructions found inside uploaded material are treated as untrusted content, never as commands that can silently change the agent’s policy.
After launch, raw conversation count is not the success metric. We inspect whether the visitor understood the offer, whether the required qualification fields were captured, whether usable context reached the manager and whether a failed session can be explained. Transcripts support controlled improvement while personal data stays out of advertising systems.
Control, security and honest limits
Quality depends on the microphone, browser, knowledge base and chosen model. The AI must not invent prices, terms or promises; complex cases need a human handoff.
Scope and price are confirmed after the call flow, integrations, languages and expected conversation volume are checked.
Questions and answers
Do you support every carrier?
We do not promise that before a technical check. Compatible SIP parameters, codecs and network conditions are required.
Can it run mass autodialling?
Only a controlled outbound flow with schedules, limits, DNC and the rules of the target market.
Where does the demo run?
The public demo runs in the browser over WebRTC. A telephone pilot starts only after setup and number-owner confirmation.
Who reviews the knowledge base?
AI prepares the draft, but an administrator reviews facts, sources, allowed answers and human-handoff rules before launch.
How is usage spend controlled?
Daily sessions, concurrent conversations, rate limits, maximum duration and pause are configured for each widget or calling workflow.
Build a demo from my website
The phone agent is a separate implementation, not a mode of the web widget. It handles inbound calls or approved outbound flows only after the SIP settings, number ownership, consent rules and human handoff route are verified.