Your paid Agent record is created
The activation code is validated and used to create the paid RTC Chat Agent record for your approved website. The code may be marked as used after successful creation according to its allowed usage rules.
Client Portal · Paid RTC Activation · LLM-Powered Agent Setup
Use the paid activation code sent by WebsDocs to create your RTC Chat Agent, connect it to the approved website domain, generate the install snippet, prepare the Agent profile, and receive CRM Dashboard access details.
Paid activation connects your Agent with approved business knowledge, services, FAQs, tone, fallback direction, support rules, usage control, and dashboard visibility. The Agent is built for controlled LLM-powered support, not a generic scripted chatbot setup.
This page is for clients who already have a valid WebsDocs activation code. If you do not have a code yet, open a support ticket and WebsDocs can guide you toward the correct setup path.
Next Process
After your paid RTC Chat Agent is created, WebsDocs uses the generated Agent record, approved website domain, business profile, install snippet, dashboard credentials, and support path to move the LLM-powered Agent from activation to website use.
The activation code is validated and used to create the paid RTC Chat Agent record for your approved website. The code may be marked as used after successful creation according to its allowed usage rules.
The details you enter become the Agent’s approved business context: company name, services, FAQs, policies, tone, contact direction, support rules, important pages, excluded pages, handoff direction, and fallback behavior.
The Agent uses controlled LLM reasoning inside the business profile and setup rules you provide. This gives the website a real RTC support layer instead of a generic scripted chatbot path.
The page returns a domain-bound install snippet for your website. This snippet connects your approved site to the WebsDocs RTC Chat Agent runtime using the generated Site ID and site token.
You receive the CRM Dashboard URL and Dashboard Client ID after Agent creation. These details are used to open the client dashboard for setup visibility, activity review, conversation records, usage signals, plan information, and related Agent status.
The generated company-profile.json can be downloaded and placed on your website where supported. The Agent can use the local profile first and fall back to the cloud profile if local JSON is not available.
The dashboard path helps you review conversations, usage activity, credits, lead signals, setup records, and operational status so the Agent is not running as a hidden chat bubble.
If you need help with installation, dashboard login, activation details, widget behavior, billing reference, usage questions, or technical issues, open a support ticket and include your Site ID, Dashboard Client ID, website URL, or activation reference.
Activation Form
Enter your activation details, confirm the selected plan, and create the paid LLM-powered RTC Chat Agent profile. The form unlocks deeper fields for Pro, Premium, Elite, and custom setup scopes so the Agent can carry the right level of approved business knowledge, service rules, FAQs, handoff direction, and support context.
After creation, the final profile is saved to the cloud profile store, indexed into the AI Brain where supported, and returned as company-profile.json for local website use.
Validate your activation code to unlock the correct plan fields.
Paid agent created
Existing Agent Update
If your paid AI Business Agent already exists and you only need to rebuild or replace the local company-profile.json file, use the separate Local Profile JSON Regenerator. This keeps first-time activation separate from existing profile updates.
The paid activation form creates a new paid assistant record, validates the activation code, generates the install snippet, prepares dashboard access, and creates the first company-profile.json output.
The Local Profile JSON Regenerator is for existing Site IDs and Dashboard Client IDs. It rebuilds the local company-profile.json file only.
Regeneration does not create a new assistant, change billing, create a new token, rewrite cloud KV, or reindex AI Brain from the browser page.
Important Disclaimer
A successful activation creates the paid RTC Chat Agent profile, install snippet, dashboard credentials, local profile output, and related setup record for the approved website. It does not automatically guarantee that the Agent is installed on the website, that all website content is complete, or that every future change, integration, provider usage, custom workflow, or expansion is included.
The Agent is designed for controlled LLM-powered support using the business information, services, FAQs, support rules, tone, fallback direction, and approved knowledge provided during setup. Incorrect, incomplete, outdated, or unclear business information can affect the quality of responses and may require profile updates or support review.
External AI provider, model, token, credit, or usage costs may remain separate unless a bundled usage arrangement is expressly included in the selected plan. Website access, platform conditions, content readiness, DNS, plugin conflicts, script placement, browser restrictions, or third-party service limits can affect installation, display, usage, and launch.
WebsDocs may request additional review, support ticket details, access information, updated scope, or prepared knowledge files if the website requires deeper implementation, custom logic, support-ticket routing, CRM dashboard review, RAG-ready knowledge preparation, industry workflow setup, or broader Context Orchestration.
Need Help?
If your activation code does not validate, your approved website URL is rejected, your dashboard details are missing, your install snippet does not work, or you are unsure where to place company-profile.json, please open a support ticket.
New clients can use support tickets for paid RTC Chat Agent activation, setup preparation, install guidance, profile questions, and dashboard access help. Existing customers can use tickets for widget behavior, billing questions, usage or credit concerns, conversation review, email delivery, integration support, and technical troubleshooting.
When possible, include your Site ID, Dashboard Client ID, activation reference, client email, approved website URL, screenshot, error message, or billing reference. Clear details help WebsDocs check the account, setup record, usage status, and support path faster.
Activation Note
After creation, copy and save your install snippet, Site ID, Dashboard Client ID, activation reference, and company-profile.json. These details may be needed for installation, dashboard access, support review, usage checks, billing questions, or future Agent updates.
For best results, review the generated paid RTC Chat Agent profile before installing it on your website. Make sure your services, FAQs, pricing notes, contact route, support rules, handoff direction, excluded pages, and fallback message are accurate before visitors use the Agent.
The Agent uses controlled LLM-powered reasoning inside the approved business profile and setup rules. Clear business information helps the Agent answer better, route visitors correctly, and stay aligned with your real support scope.