Launch your business-aware RTC Agent in about five minutes.

RTC can use the structured business profile and approved public knowledge connected to the published site. This may include the business name, summary, services, offers, public pricing guidance, locations, hours, contact details, FAQs, policies, important pages, service routes, aliases, support instructions, and fallback behavior.

Approved website context helps the Agent stay aligned with the real public business environment. The company can identify important pages such as services, pricing, contact, FAQ, booking, support, or policy routes and keep those paths connected to the RTC profile.

The business remains responsible for keeping published information current. When services, prices, policies, contact details, or support rules change, the RTC profile should be updated so the Agent does not rely on retired information.

RTC does not automatically receive unrestricted access to private customer records, invoices, payment accounts, passwords, databases, private files, or internal business systems. Public plan and billing rules can be explained when they are part of the approved knowledge, but private account facts require the correct protected route.

When a visitor asks for an account-specific refund, invoice, payment change, private order detail, or another protected action, RTC should explain the boundary instead of pretending it completed the request.

The conversation can then move into Human Handoff for business-team review, or the verified RTC customer can use Direct RTC Messages to contact WebsDocs Billing, Support, Projects, or General operations from the dashboard.

Human Handoff connects the website visitor with the RTC customer’s team. When a conversation needs human authority, the Agent can stop trying to resolve the issue and create a handoff case with the relevant conversation context.

The visitor remains in the same website conversation experience while the business team sees the case inside the Human Handoff Inbox. An authorized team member can start handling the case, review why it was transferred, reply into the visitor widget, and mark the case resolved.

Handoff is especially useful for private billing questions, sensitive support issues, custom commercial decisions, complex project requirements, complaints, uncertainty, or any situation where a person should take responsibility.

Direct RTC Messages are the communication path between the verified RTC customer and WebsDocs. They are different from Human Handoff, which connects the business team with its own website visitor.

From the protected RTC dashboard, the customer can route a message to Support, Billing, Projects or Maintenance, or General operations. The message remains attached to the authenticated RTC account identity rather than relying on a separate anonymous mailbox session.

The customer can review incoming replies and sent history inside RTC. This keeps operational communication closer to the relevant site, plan, profile, billing, support, or maintenance context.

RTC Website Health is primarily a public website structure and business-readiness assessment. It reviews signals that affect how clearly the website presents the business and whether visitors can find useful contact, support, trust, lead, Agent, and ecommerce paths.

Checks may cover business identity, service clarity, headings, links, images, forms, calls to action, contact details, About and policy routes, accessibility hints, response information, public security headers, performance structure, lead readiness, support readiness, RTC Agent readiness, and ecommerce readiness where relevant.

It is not a penetration test, legal-compliance certification, complete private-system audit, or replacement for specialized Lighthouse and technical SEO platforms. The useful RTC difference is the workflow: scan the approved site, review priorities, receive the report, compare history, and request WebsDocs maintenance.

With the required business information prepared, the guided setup can usually be completed in about five minutes. The activation path is designed to move from checkout through identity verification, business setup, final confirmation, publication, installation, and dashboard access.

The activation email normally arrives quickly, but WebsDocs should not promise an exact inbox-delivery second. Spam filtering, email-provider delays, incorrect customer details, OTP delivery, payment review, or website-origin conflicts can affect timing.

The fastest setup happens when the customer already has the business summary, services, FAQs, policies, locations, hours, contact routes, important website pages, and preferred Agent presentation ready.

Prepare the public business name, short summary, primary market, services, offers, service areas or locations, business hours, contact details, preferred visitor next steps, and approved website address.

Strong RTC setup also includes frequently asked questions, privacy and commercial policies, payment or refund guidance where applicable, support boundaries, booking or quote paths, important website pages, Human Handoff instructions, and fallback behavior for uncertain questions.

The information should describe what the business actually provides now. Avoid loading the profile with retired services, unapproved guarantees, private customer details, or internal information that should not be used in public visitor conversations.

After successful activation, RTC creates the published site relationship and provides an installation package connected to the RTC Site ID and approved website origin. The customer can place the provided loader on the approved website according to the installation instructions.

The publication receipt can also provide access to the hosted Agent path and the protected RTC dashboard. The dashboard is where the customer manages the profile, appearance, domains, conversations, Human Handoff, Messages, Website Health, credits, billing information, and activity.

The site ID should not be copied to unrelated domains. Approved-origin controls help prevent the published Agent from being reused outside the websites authorized for the active RTC account.

The trial provides seven days of Pro entitlement with no charge today. A valid card is required. The trial uses Swift mode and includes 250 RTC Credits, one approved domain, one user, up to four sessions, 90-day retention, and access to the Human Handoff Inbox.

The trial is intended to test the real RTC experience, including the business profile, website Agent, dashboard visibility, approved-domain controls, conversations, and human escalation path.

The customer should review the checkout terms for the billing date, cancellation rules, current price, and the plan that will continue after the trial. The live checkout catalog remains the commercial authority.

Swift, Focus, and Apex are RTC operating modes. They describe the depth and resource position used for a conversation rather than exposing raw model-provider names to the customer.

Swift is the fast everyday mode for common questions, service guidance, normal support, and lead capture. Focus supports deeper structured explanations and comparisons. Apex is the highest-depth option for more complex or high-value conversations that require broader approved context.

Swift uses the 1× RTC Credit position, Focus uses 3×, and Apex uses 6×. Trial and Pro operate in Swift. Business and Enterprise can switch among all three modes, subject to the active entitlement, site, origin, wallet, and runtime checks.

RTC Credits are the prepaid service units used by the RTC runtime. The active site, origin, plan, selected mode, and available wallet are checked before billable generation. This helps prevent uncontrolled provider usage outside the customer’s entitlement.

Pro includes 1,000 credits per successful monthly billing period, Business includes 4,000, and Enterprise includes 12,000. Annual customers pay the annual price but still receive the included credits monthly after successful billing. The full annual amount is not granted as one immediate lump sum.

Credit use depends on the selected operating mode and the work performed. Swift is the 1× base position, Focus is 3×, and Apex is 6×. The dashboard provides balance and usage visibility so the customer can see the operating position.

Monthly billing pays for one service month at a time. Annual billing prepays the annual service period and provides 12 months for the price of 10 at the published annual rate.

The annual discount changes the payment schedule, not the monthly operating rhythm of included RTC Credits. Credits continue to be granted monthly after successful billing rather than being deposited as a full 12-month quantity on the first day.

The current checkout page remains the final price and billing authority. Customers should review renewal, cancellation, refund, payment, and service terms before confirming the order.

Pro supports one approved domain, Business supports up to three, and Enterprise supports up to six. The domain allowance applies to the websites authorized for the active RTC account and publication record.

A domain is not simply a decorative dashboard entry. The approved-origin relationship helps control where the RTC Site ID and published installation can operate. This reduces the risk of an installation being copied to an unrelated website.

Requirements beyond the public Enterprise allowance need a custom review rather than an unsupported promise. The customer can contact WebsDocs for Enterprise or custom deployment assessment.

Yes, within the active plan allowance. The customer can manage approved domains from the protected RTC Control Center, but adding or removing an origin is treated as a protected account change.

The domain change must pass verified-account identity confirmation before it is applied to the draft. The customer then publishes the change so the approved-site relationship and live operating record remain traceable.

Removing a domain can affect an existing installation. The customer should confirm that the Agent is no longer needed on that website and review any related operational consequences before publishing the removal.

Yes. The protected RTC Control Center allows the customer to maintain the published business profile after activation. This includes business identity, public summary, services, offers, locations, hours, contact routes, FAQs, policies, important pages, appearance, and operating mode.

Changes should be reviewed before publication because the live Agent may use the updated information when guiding visitors. A draft and published state helps distinguish edits being prepared from the profile currently connected to the live RTC site.

Frequent updates are especially important when pricing guidance, services, policies, hours, locations, contact details, or support instructions change.

RTC should not convert uncertainty into a confident invention. When the approved profile does not contain the required fact, the Agent can explain the limitation, ask a useful clarifying question, guide the visitor to an approved public route, or offer Human Handoff.

Sensitive requests may include private billing, legal decisions, complaints, account access, payment execution, confidential information, high-value custom commitments, or anything requiring a responsible person to review the facts.

Runtime conditions can also lead to a limited, routed, or blocked result. Unauthorized origins, disallowed modes, an empty wallet, or abuse patterns should not continue as normal billable generation.

RTC is designed for protected customer and team operation rather than one invisible browser-only session. Authorized team access can support Human Handoff handling, operational review, profile work, messages, reports, and account activity according to the available team-member pipeline.

The dashboard can show active sessions and traceable events such as profile publication, domain identity verification, Human Handoff actions, Direct RTC Messages, Website Health reports, and other account operations.

Records are not promised as unlimited permanent storage. Conversation, message, report, session, and activity retention follows the active plan, product rules, and applicable service conditions.