Add a multilingual AI Voice Agent to your business website.

The WebsDocs AI Voice Agent is a website voice support layer that lets visitors speak with a business website instead of only typing into a chat box. Visitors can ask questions by voice, receive spoken answers, understand services, ask follow-up questions, and move toward contact, booking, support, sales follow-up, or human review.

It is not only a voice button. The system includes managed setup, a business voice profile, an install snippet, local profile file output, voice usage control, prepaid credits, support handoff direction, and Voice CRM Dashboard visibility.

RTD means Real-Time Duplex. In WebsDocs, it describes a live voice flow where the visitor can speak naturally, ask another question, continue the conversation, or interrupt while the AI is responding.

This is different from an old phone menu where the visitor must wait for a full prompt to finish. RTD voice is designed for more natural turn-taking, cross-talk tolerance, and live conversational flow.

Yes. WebsDocs RTD Voice is cross-talk tolerant. Visitors can ask a new question, correct themselves, or continue speaking while the AI is responding. The Voice Agent can detect the new speech turn and continue the conversation in context.

Actual voice behavior can vary by browser, microphone quality, network condition, selected voice model, language, device, and setup configuration.

Yes. Voice Pro, Voice Business, and Voice Enterprise all include RTD voice flow. The difference between plans is not whether RTD exists. The difference is operating depth.

Plans differ by included voice minutes, profile depth, routing rules, dashboard visibility, support scope, storage and recording options, retention guidance, handoff depth, operational review, and usage capacity.

WebsDocs AI Voice Agent can be planned for supported multilingual voice conversations depending on the selected voice model, browser behavior, microphone quality, and setup configuration. Language availability is not treated as “all languages guaranteed.” It is planned around the target market and tested during setup where needed.

Supported language planning may include English, Hindi, Malay, Indonesian, Spanish, French, Dutch, Japanese, Korean, Chinese, Arabic, and other available languages depending on the selected voice setup.

For business use, the best setup is not only “can the AI speak the language?” The better question is: can the Voice Agent answer with the right business knowledge, tone, fallback rules, support path, and handoff behavior in the language your visitors are likely to use?

WebsDocs can configure language direction inside the voice profile. This may include auto-detect behavior, preferred primary language, multilingual mode, greeting style, short-answer rules, and support escalation rules for cases where the AI should not continue in a language or topic.

For Chinese, setup may need more specific review, such as Mandarin or Cantonese availability where supported. For Malay and Indonesian markets, language handling can be planned around Bahasa Melayu and Bahasa Indonesia. For Japanese and Korean markets, the setup should be tested with real visitor-style questions before launch.

In supported setups, the Voice Agent may handle multilingual behavior or respond according to the selected language mode. The setup can be planned for auto-detection, one primary language, or multi-language behavior.

For production business use, WebsDocs recommends testing the target languages before launch. Voice recognition, pronunciation, accent handling, and answer quality can vary by language, device, microphone, browser, and model capability.

After choosing Voice Pro, Voice Business, or Voice Enterprise, the client completes checkout with the correct client or business name, email address, and approved website URL. These details are important because they are used for the order record, activation-code email, approved website setup, dashboard record, and support path.

After payment is confirmed, WebsDocs provides the paid activation path. The client uses the activation code to create the AI Voice Agent profile, generate the install snippet, download the local profile file, and open the Voice CRM Dashboard access path.

The client should provide the correct client or business name, working email address, and approved website URL. These details should be accurate before checkout is submitted.

If the client name, email address, or website URL is missing, incorrect, suspicious, or does not match the order, the activation code may be held for manual review before release.

When checkout is confirmed and the client details are correct, activation access can normally be issued quickly. In a clean automated flow, the activation code may arrive by email within about 1 minute after confirmed checkout.

If details are missing, incorrect, or require review, the order may go to manual review. Manual review is used to protect the client, the approved website, and the WebsDocs activation system.

Once the activation code is validated and the client details are ready for copy-paste, one Voice Agent setup record can be created within seconds after submitting the activation form.

If the business profile, greeting, services, FAQs, support rules, language direction, and handoff details are prepared, the full setup output — including snippet, dashboard access, usage wallet, and profile file output — can normally be created within a few minutes.

After the setup is created, the client receives the generated install snippet and the voice-company-profile.json file. Upload the profile file to /data/voice-company-profile.json on the approved website, then paste the generated snippet on the pages where the Voice Agent should appear.

Once the snippet and profile file are installed correctly, the Voice Agent launcher can appear on the website immediately. If it does not appear, check the snippet placement, profile file path, domain match, browser cache, and console errors before opening a support ticket.

The setup fee covers the Voice Agent launch path, business voice profile structure, install snippet, dashboard setup record, billing wallet setup, initial credit grant, and activation flow for the approved website.

The setup also prepares the operational foundation: agent identity, greeting, services, FAQs, voice behavior rules, language direction, safe-answer boundaries, support paths, handoff preferences, and website install output.

Monthly or annual care covers ongoing system service, profile support direction, dashboard path, monitoring, support handling, and operational maintenance. It helps keep the Voice Agent path manageable after initial setup.

Annual care follows the simple promotional rule shown on the page: pay 10 months and receive 12 months of care.

Clients see usage in voice minutes because minutes are easier to understand. Internally, WebsDocs controls usage with voice credits, where 1 voice credit equals 1 billable voice second.

This means 60 voice credits equals about 1 voice minute. The dashboard converts credit balance into estimated remaining minutes so clients can understand usage without reading backend billing logic.

The first setup grant is tied to the selected plan. Under the launch promotional structure, Voice Pro starts with 7,200 credits, Voice Business starts with 30,000 credits, and Voice Enterprise starts with 90,000 credits.

These match approximately 120, 500, and 1,500 promotional voice minutes. Base and promotional grants may vary depending on the active offer, confirmed plan, and billing cycle.

The Voice CRM Dashboard can show remaining credits and estimated minutes. When usage becomes low or reaches zero, the system can warn, limit live voice responses, pause billable processing, or route visitors to contact or support until usage is topped up.

Top-ups are prepaid. Credits are added after payment confirmation and can be reviewed through the dashboard ledger where supported.

The Voice CRM Dashboard is the client command center for the AI Voice Agent. It helps clients review the active website, plan, credits, estimated remaining minutes, conversations, transcripts, handoffs, follow-up signals, installation status, billing state, setup records, and support direction.

The dashboard is opened with the Site ID and Voice Dashboard Access Code created during activation. These access details should be kept safe.

The dashboard can include overview details, connected website information, operating health, voice conversations, transcript details, follow-up signals, voice credits, handoffs, audio storage status, installation details, usage records, email records, billing state, plan access, and support direction.

Available dashboard details depend on the plan, active setup, usage events, storage settings, and system configuration.

Add the generated install snippet before the closing </body> tag on the website pages where you want the Voice Agent to appear. Upload the local profile file to /data/voice-company-profile.json on the approved website.

The website URL used during activation must match the approved website. If the profile file path or domain does not match, the launcher may not work correctly.

voice-company-profile.json is the local business voice profile file generated during activation. It contains the approved profile information the Voice Agent uses for the website setup.

The file should be uploaded to /data/voice-company-profile.json on the approved website so the widget can load the correct company profile when the launcher appears.

No. Audio storage is optional and plan-controlled. Some setups may keep transcripts and usage records even when audio recording storage is disabled.

Recording retention depends on the active plan, setup rules, storage configuration, and privacy requirements. Clients should avoid collecting unnecessary sensitive information through the Voice Agent.

No. The public Voice Sandbox runs from a separate WebsDocs demo profile and demo site ID. It is limited so visitors can preview the RTD voice experience without using a real client wallet.

Sandbox conversations may be logged for quality, abuse prevention, service improvement, and CRM review. Do not share passwords, payment details, private documents, or sensitive personal information during the demo.

The public Voice Sandbox is intentionally limited to protect the demo system from abuse and to keep preview usage fair. The 2-minute limit is enough to test the voice flow, cross-talk tolerance, answer style, and support direction before choosing a plan.

Enterprise adds advanced operating depth, not basic duplex access. It is designed for larger or sensitive websites that need advanced routing, multi-team escalation, stricter response boundaries, storage and retention guidance, higher usage capacity, deeper dashboard review, and custom operational support.

Enterprise may also be better for businesses that need sensitive-topic handling, multi-department routing, controlled escalation, advanced language review, or custom operational workflows.

Yes. Clients can move from Voice Pro to Voice Business or Voice Enterprise when they need higher usage, stronger routing, broader CRM visibility, optional recording controls, advanced support direction, storage controls, or deeper operational review.

Open a WebsDocs support ticket for activation help, snippet installation questions, dashboard access issues, billing or credit questions, microphone/browser behavior, language setup review, profile updates, or custom implementation support.

Include useful references such as your client email, approved website URL, Site ID, dashboard access reference, activation code reference, plan name, and a clear description of the issue.