Your website should do more than wait to be read.

RTD is a website conversation and business-operation product that brings Voice, Chat, approved company information, visitor intent, lead creation, Human Inbox continuation, transcripts, recordings, website deployment, and operating controls into one connected workspace.

The website Agent responds from an approved business profile and remains connected to the Voice Dashboard, where the business can review activity, outcomes, usage, domains, publication status, and account controls.

RTD Studio is where the business profile is prepared, reviewed, approved, and published. It defines what the Agent is permitted to communicate about the company, its services, processes, policies, routes, and business information.

The Voice Dashboard is the operating workspace used after setup. It shows live and previous conversations, leads, Human Inbox cases, transcripts, recordings, Domain Agents, Website Audit results, usage, credits, Support Messages, team access, and settings.

The business-facing experience is built around the approved RTD profile and the information authorized for that Domain Agent. The purpose is to keep responses aligned with the company’s approved services, terminology, policies, processes, and visitor routes.

Changes to important business information should be reviewed and published through RTD Studio so the live Agent continues to reflect the approved company position.

Yes. A Domain Agent can provide Voice, Chat, or both, depending on the selected plan, published configuration, website experience, and enabled channels.

Both channels remain connected to the same approved business profile and operating workspace, allowing the team to review visitor intent, conversation context, actions, outcomes, and usage without separating the business record.

The interaction can continue through Human Inbox when the request is sensitive, uncertain, qualified, account-specific, or requires an authorized company officer.

The officer receives the available conversation context, including visitor intent, previous messages, the Agent’s summary, routing destination, and relevant contact details. The case can then be accepted, assigned, replied to, noted internally, resolved, closed, or returned to the Agent.

When a visitor expresses qualified intent and provides appropriate contact details or permission, RTD can create a visible lead record connected to the original conversation.

The lead can contain contact information, project or service interest, qualification answers, conversation context, source channel, Domain Agent, assignment, status, notes, and follow-up history. This allows the business to move from conversation to accountable sales work.

A Domain Agent is the approved RTD operation assigned to a specific website or domain. It connects that website to its published profile, enabled channels, language coverage, deployment method, connection status, usage, and recent activity.

Businesses operating multiple approved websites can manage those Agents separately while keeping them inside the same protected workspace and shared account structure.

RTD can be deployed as a Premium iframe, Floating Agent, Button Agent, JavaScript SDK integration, or protected Hosted Agent page. These methods give the website team control over how and where the visitor experience appears.

A business can also use Dashboard Platform Settings for supported managed connections. The selected route remains tied to the approved Domain Agent and its publication controls.

Deploying means placing the Agent through a supplied website format such as an iframe, floating launcher, existing button, SDK, or hosted destination.

Connecting means authorizing a supported website platform through Dashboard Platform Settings. That route can handle platform authorization, configuration, verification, connection status, and managed installation from the protected workspace.

The product experience presented here supports managed connection routes for WordPress, Shopify, Wix, Squarespace, Webflow, and Google Tag Manager.

The available authorization and installation steps can differ by platform. Connection status, domain verification, selected Domain Agent, deployment format, and publication readiness remain visible through Dashboard Platform Settings.

Eligible Voice, Chat, and Human Inbox activity uses credits from the workspace’s shared prepaid wallet. The Dashboard shows the available balance, usage by channel, monthly credit delivery, top-ups, transaction history, and estimated remaining activity.

Actual consumption depends on the active product channel and the applicable plan rate. The pricing and usage areas should be used for the current allowance, included features, and credit terms.

Conversation transcripts remain connected to the relevant conversation record when available under the product operation. Audio recordings are separate and appear only when recording is enabled for the plan, Domain Agent, and applicable conversation.

The business should configure recording and retention according to its operational requirements, customer communications, applicable permissions, and account controls.

Website Audit provides a structured view of website readiness, visible business risks, category scores, findings, supporting evidence, affected pages, recommendations, and audit history.

It helps the business understand whether the website clearly supports visitor pathways, company positioning, trust, support, conversion, and the wider RTD operation. It does not automatically replace business review or implementation decisions.

The workspace is designed to keep Agent status, profile version, domain state, connection, installation, and publication controls visible after launch.

An authorized user can review the relevant configuration, update approved business information through RTD Studio, verify the website route, and publish the appropriate version. Availability can also be controlled when the business does not want the Agent accepting new conversations.