What should I prepare before starting the setup?
Prepare the activation code, registered client email, official company name,
client or contact-person name, approved website address, business summary,
services, products, public offers, frequently asked questions, opening greeting,
language instructions, human handoff rules and approved appearance assets.
Enter only information that the business has approved for customer-facing use.
Having these details ready helps prevent incomplete profiles, conflicting answers
and repeated editing during publication.
What is the difference between Company name and Client name?
Company name is the public business, organization or brand name
that customers may see in the Studio, published handover, dashboard and Voice
Agent experience.
Client name is the owner, manager, administrator or contact person
responsible for the account. The client name should not replace the company name
in public branding.
Which email address should I enter?
Enter the exact email address connected to the activation code. The activation
code and registered email are validated together.
A different email address may cause an activation-code mismatch even when the
activation code itself is correct.
What should I enter as the company name?
Enter the official customer-facing business or brand name. Use the spelling,
capitalization and punctuation the business wants displayed publicly.
Do not enter the owner's personal name, email username, website address or a
temporary project label unless that is the approved public company identity.
What should I enter as the client name?
Enter the name of the business owner, authorized representative, account manager
or operational contact responsible for the Voice Agent account.
This field is separate from the public company name and may be used for account,
administrative or support communication.
What website should I provide?
Enter the primary approved website where the Voice Agent will be connected.
Use the complete public address, including https://.
The website is used for domain binding and installation direction. Check the
spelling carefully and avoid entering a private dashboard, temporary preview,
unrelated domain or unsupported local development address.
What should the business summary contain?
Write a clear description of what the business does, who it serves and what makes
its services useful. The summary should help the Voice Agent understand the
business without relying on vague promotional language.
Include approved facts such as the business type, service area, target customers,
core capabilities and important operating context.
How should I enter services or products?
List the services, products or solution categories customers may ask about.
Use clear names and short approved explanations.
Avoid adding services that are planned but not yet available. Do not include
internal-only details, supplier information or unsupported performance claims.
What information should be included for each service?
Include the service name, what it is for, who it is suitable for, the main outcome,
important limitations and the next action a customer should take.
Add only details that the Voice Agent is permitted to explain publicly. Complex,
regulated or custom cases should be directed to a human representative.
How should offers, packages or promotions be entered?
Add only active and approved public offers. Clearly state what is included,
eligibility, important conditions and any known expiry information.
Do not let the Voice Agent invent discounts, extend promotions, negotiate custom
terms or promise exceptions. Requests outside the approved offer should be handed
to a person.
Can the Voice Agent promise prices or discounts?
Only approved public prices and clearly defined offers may be explained.
The Voice Agent should not negotiate, guarantee a quotation or create a discount.
Custom pricing, refunds, legal commitments, contract changes, exceptional terms
and account-specific decisions should be routed to an authorized person.
How should I write the frequently asked questions?
Add real questions customers commonly ask, followed by concise and approved
answers. Each answer should directly address one question.
Good FAQ topics include availability, service process, booking, delivery,
eligibility, general pricing direction, preparation requirements, support and
next steps.
Avoid combining several unrelated topics into one answer, and do not add
information the business has not confirmed.
How should unknown questions be handled?
Configure a clear fallback response explaining that the Voice Agent does not have
enough approved information to answer confidently.
The fallback should offer a human handoff or another approved contact method.
The Voice Agent should never invent facts, policies, prices, availability or
commitments outside its approved knowledge.
What should I enter as the opening greeting?
The greeting should identify the business, welcome the visitor and invite a clear
question. Keep it natural, brief and appropriate for both voice and text use.
Avoid long sales introductions, unsupported claims or asking for sensitive
information before the customer explains what they need.
How should language instructions be configured?
Specify the preferred customer-facing language and the expected tone, such as
professional, friendly, concise or formal.
Add direction for multilingual requests only when the business supports them.
The Voice Agent should not claim fluency, translation support or regional service
that has not been approved.
What are human handoff rules?
Human handoff rules define when the Voice Agent should stop trying to complete
the conversation alone and transfer or escalate the customer to a person.
Common handoff reasons include pricing exceptions, complaints, refunds, legal
questions, emergencies, account access, sensitive personal matters, unsupported
requests and repeated failure to understand the customer.
What information should the handoff collect?
Collect only the minimum approved information needed for follow-up, such as the
customer's name, contact method, reason for contacting the business and a short
conversation summary.
Do not request passwords, payment-card details, authentication codes or unnecessary
sensitive information.
Can I enter information the business has not approved?
No. Add only verified business facts, approved public policies and operating
instructions that the Voice Agent is authorized to communicate.
Unverified information can create misleading answers, customer disputes and
incorrect commitments.
Should I copy text directly from the website?
You may use approved website information, but review and simplify it before adding
it to the profile.
Remove navigation text, outdated promotions, duplicate content, legal boilerplate
and information that does not help the Voice Agent answer customer questions.
Can I save an incomplete setup and return later?
Use the Studio draft controls when available. Review all restored fields before
continuing because website information, offers or business instructions may have
changed since the draft was saved.
Does the Studio store my activation code?
No. The activation code remains in JavaScript memory during the active Studio
session and is not written into the local profile draft.
Keep the activation code private and do not include it inside business summaries,
FAQs, greetings or other profile fields.
Why must the activation email match exactly?
The activation code is connected to the registered email for account verification
and ownership protection.
Using another email can cause the Setup Worker to report that the activation code
or registered email could not be matched.
What browser checks happen before creation?
The Studio checks required fields, supported formats, profile limits and basic
consistency before sending the final request.
Passing browser checks does not replace backend validation. The Setup Worker and
related authorities still perform the final security, identity, plan and domain
checks.
When is the Voice Agent workspace created?
The workspace is created only after the profile passes Studio checks and the
Setup Worker accepts the final activation request.
Entering an activation code or saving a draft does not by itself create the
production workspace.
Does workspace creation mean the agent is already live?
Not necessarily. Agreement acceptance, domain verification, profile placement,
loader installation and controlled testing may still be required.
Follow the Complete and Published handover instructions before treating the
Voice Agent as publicly available.
Where are plan limits enforced?
The Studio limits the browser payload to improve clarity and prevent oversized
submissions.
Final plan, credit, domain, recording, storage and operational limits remain under
the authority of the Setup Worker and connected backend services.
Are transcripts and recordings the same thing?
No. Transcript storage and audio recording are separate controls.
Audio storage is available only when the active plan, configuration and applicable
policy allow it. Enabling text conversation history does not automatically mean
audio is recorded.
Can I upload a logo, banner and separate avatar?
Yes. The Studio may accept separate business branding assets for the final
production profile.
Selected images are sent with the final creation request. When no avatar is
selected, the included RTD default avatar is used.
What image files should I use?
Use clear, approved business images with suitable dimensions and file size.
Logos should remain readable at small sizes, banners should not contain essential
text near the edges and avatars should have a clear central subject.
Do not upload copyrighted, misleading, confidential or unapproved images.
Can the client choose the widget panel color?
Yes. Panel, text, launcher and accent colors are stored in the production profile
appearance settings and shown in the live preview before creation.
Choose colors with sufficient contrast so text, buttons, controls and status
messages remain readable.
Does the live preview guarantee the final website appearance?
The preview shows the selected profile and appearance direction, but the final
presentation may also be affected by the published loader, website layout,
available screen space and browser environment.
Test the installed widget on desktop and mobile before public release.
What should I review before pressing Create?
Confirm the company name, client name, registered email, website, summary,
services, offers, FAQs, greeting, languages, handoff rules, contact information,
branding and appearance.
Also confirm that no field contains passwords, activation codes, private notes,
internal instructions or unapproved claims.
What happens after successful creation?
The Studio remains on the Complete screen while the protected Published handover
opens in a separate tab after the Setup Worker returns a successful response.
The handover provides the next approved publication, installation and operational
directions for the created workspace.
What should I do if the Published handover does not open?
Check whether the browser blocked the new tab, then use the available Published
or continuation control from the Complete screen.
Do not repeat workspace creation unless the Studio clearly reports that creation
failed.
Where do I manage the agent after setup?
Use the Voice Dashboard to review workspace status, domains, agreement direction,
wallet usage, conversations, handoffs, installation and operational controls.
The Studio is primarily for setup and creation. Ongoing management should be
completed through the authorized dashboard.
Can I edit the agent after creation?
Use the supported dashboard and profile-management controls for approved updates.
Some identity, domain, publication or agreement changes may require additional
verification.
Avoid creating a second workspace merely to correct a small profile detail unless
the system specifically instructs you to do so.
What should I do before making the Voice Agent public?
Test common customer questions, unknown questions, service explanations, handoff
behavior, contact collection, mobile layout, desktop layout and failure messages.
Confirm that the Voice Agent does not invent answers, expose private instructions,
promise unauthorized terms or continue when human assistance is required.
WebsDocs RTDReal-Time Duplex Voice Agent