Floating RTC widget
Install the universal loader once on the approved website.
<script src="https://rtc.websdocs.com/rtc-agent.js" data-site-id="assigned-after-publish" defer></script>
Step 01
Validate Activation
Confirm the authorized activation record before profile setup begins.
✓
Authorized activation confirmed
Congratulations, your company
Your WebsDocs RTC setup is approved. Continue to verify ownership and build the business profile.
CompanyNot loaded
Website—
Plan—
Email—
Login limit—
StatusWaiting
Authorized entry
Validate activation
Use the activation code, registered email and approved website URL from WebsDocs.
Identity anchors are verified by Paid-Control. “Clear fields” only empties the form. “Start new activation” securely closes the current Setup Studio session before a different activation code or email is used.
Ownership
Verify the registered email
A one-time code is sent directly through the RTC email service.
No code requested.
Dashboard security
Create the permanent dashboard password
The password is hashed before storage and linked to the verified email after publication.
Use at least 12 characters with uppercase, lowercase, a number and a symbol.
Server permissions
Workspace readiness
Review the server-provided plan, domains, model modes and simultaneous dashboard login allowance.
The account, site ID, agreement and published runtime are created together after final approval. This prevents half-created live agents.
Structured profile
Business identity
Build the official business truth layer used by the RTC agent.
Public contact routes
Contact, locations and operating hours
Add only information the business wants visitors and the RTC agent to use.
Agent knowledge
Services
Each service becomes a structured item the agent can explain.
0 / —
Commercial structure
Products and offers
Add public packages, subscriptions or offers only when they are real and current.
0 / —
Safe commercial wording
Pricing rules
Control what the agent may state and what requires human confirmation.
Approved answers
Frequently asked questions
Real questions and approved answers reduce uncertainty and expensive live reasoning.
0 / —
Safety boundary
Policies and blocked topics
Define public rules, limitations and topics that must be handed to a human.
Human safety route
Handoff rules
Tell the agent when and where to escalate.
Private R2 assets
Company logo and agent avatar
PNG, JPEG or WebP. The default WebsDocs RTC assets remain active when no upload is provided.
Global agent configuration
Agent appearance and greeting
The same rtc-agent.js renders the approved configuration for every plan.
AI
Company AssistantOnline
Hello! How can we help you today?
Type a message…
Origin enforcement
1 / —Approved domains
The activation origin stays primary. Business and Enterprise may register additional origins now up to the plan allowance.
The primary activation origin is verified immediately. Additional origins are registered as pending and must complete domain verification before the widget can run there.
Capacity mode
Swift, Focus and Apex
Actual provider models remain internal. Clients choose only approved public capacity modes.
Trial and Pro are locked to Swift. Business and Enterprise may switch modes later in the dashboard. Multipliers: Swift 1×, Focus 3×, Apex 6×.
Three delivery options
Installation handover preview
The final Site ID is assigned only after OTP verification and the typed ACTIVATE confirmation.
Prominent Ask AI button
Place a visible launcher in a hero, navigation, pricing, support or footer section.
<button type="button" class="rtc-ai-cta" data-rtc-open>Ask AI</button>
Hosted RTC page
Use a direct WebsDocs-hosted Agent link for email, QR codes, campaigns or websites that cannot install JavaScript.
https://rtc.websdocs.com/agent/assigned-after-publish
After publication, the client email, verified success page and Dashboard Installation tab all receive the same authoritative installation package.
Digital contract chain
Agreement
The Contracts Worker creates and emails the RTC agreement when the site is published. The agreement records the monthly billing cadence separately from the 12-month commitment term.
Commercial policy12-month service commitment, billed monthly.Monthly payment is the billing cadence. The commitment term remains twelve months. Included credits are granted for each successfully paid monthly period.
Before public approval
Review the complete setup
Save the server draft and inspect the structured profile, plan and publishing boundaries.
Structured profile JSON
Final authority
Activate the RTC Agent
A fresh email OTP and the exact word ACTIVATE are both required. Nothing is created until the server validates both controls.
1Save the final profilePlan volume and domain limits are checked by Paid-Control.
2Verify the fresh OTPThe final code is sent only to the registered client email.
3Type ACTIVATEThis confirms creation of the account, site, agreement and live profile.
No final code requested.
During activation the complete setup is locked. The server verifies the OTP and confirmation, creates the live RTC resources, prepares every installation snippet, sends the client handover email and issues the verified success receipt. Manual RAG indexing remains separate and chargeable.
Verified handover
RTC Agent activated
The server-created installation package appears here briefly before the verified receipt page opens.
✓
Ready for verified publication receipt
Complete the Final OTP step. Manual visits to the receipt page do not fire the conversion.
✓
RTC Agent activated
Opening the verified handover page…
Site ID—
Hosted Agent—