WebsDocs Support Center

Support for active RTD, RTC, ASG, Business Automation, billing, and account access.

Create one private support record for an active WebsDocs service, then continue the same issue through its ticket dashboard, replies, attachments, and status history.

Support access

New issue or existing ticket? Open a new ticket for a new issue. Use Ticket Login to continue an issue that already has a Ticket ID and access code. Open Support Ticket

WebsDocs Client Support Workspace

One support record for one issue, with the complete client and support history kept together.

This is the verified support workspace for active WebsDocs services. It keeps the request, service references, attachments, replies, status, and previous ticket records connected to one private support case.

Use it for RTD Business Agent, RTC Business Automation, ASG Sales Gateway, Business Automation, dashboards, installation, domains, account access, billing and credits, Website Health, messages, privacy requests, or an existing managed-service issue.

After ticket creation, WebsDocs sends the Ticket ID and access code to the email used in the form. Those details reopen the same dashboard so the conversation continues without starting over.

RTD Business Agent

Voice, Widget Chat, Human Inbox, recordings, domains, installation, usage, credits, billing, and RTD workspace access.

RTC Business Automation

Agent behavior, conversations, Handoff Inbox, domains, Knowledge Search, Website Health, usage, billing, and RTC account access.

ASG Sales Gateway

Client Portal, profile publication, AI Registry, gateway discovery, domains, Website Health, credits, billing, support messages, and buyer-routing records.

Business Automation

Workflow setup, cases, routing, automation behavior, dashboard access, usage, billing, service configuration, and managed workflow questions.

Billing, credits & account access

Payments, invoices, credits, top-ups, subscription state, login, OTP, authenticator, workspace access, and account-record questions.

Privacy & service records

Privacy requests, transcripts, recordings, data access, lawful-use review, service eligibility, and record-specific questions through a tracked support path.

Ticket created

Your request, references, and attachment are stored as one private support record.

Access details sent

Your Ticket ID and access code are sent to the email used during submission.

Support review begins

The ticket is checked, categorized, routed, and linked to the available WebsDocs records.

Continue in dashboard

Read replies, add details, upload another file, and follow the status until completion.

Create Ticket

Open a new support ticket for a new issue.

Use this path for an existing WebsDocs service. Give the exact affected product or workspace and attach a small screenshot, log, document, or JSON file when it helps explain the issue.

RTD, RTC, ASG, or Business Automation issue
Dashboard, domain, installation, login, or account-access problem
Billing, credits, usage, email delivery, or support-message problem
Existing client setup, Website Health, routing, or technical support

Read FAQ

How To Use The Ticket Dashboard

Your dashboard is the main record for the complete support conversation.

Email notifications help you know when activity occurs, but the ticket dashboard remains the authoritative place for the full request, replies, files, status, and support history.

Confirm the ticket summary

Review the Ticket ID, subject, topic, priority, creation date, and current status before replying. This confirms that you opened the correct support record.

Read the latest activity first

The conversation area prioritizes the newest messages. Use the full-conversation control when you need the original request, earlier support replies, or older updates.

Reply inside the same ticket

Continue the existing issue through the reply form. Add test results, corrected references, screenshots, logs, or clarification without opening another ticket.

Use attachments with context

Explain what the file shows and where the problem appears. A screenshot without context may not identify the affected service, page, account, or expected result.

Review previous client records

The client-history area helps you recognize earlier tickets, repeated topics, and the status of previous support records linked to the same client email.

Keep access details private

Your Ticket ID, email, and access code open the private support dashboard. Do not publish or share them in public posts, screenshots, or unrelated conversations.

Ticket Status Guide

Understand what the current status means.

Open

The request has been received and is available for support review.

In Review

The issue is being checked, linked to records, or routed to the appropriate support path.

Waiting for Client

More information, a reference, a test result, or confirmation is needed from you.

Resolved

A resolution, explanation, correction, or next-action path has been provided.

Closed

The support conversation is complete and no further action is currently expected.

Best practice: Keep one issue inside one ticket. If the subject changes into a different problem, open a new ticket so both issues keep a clear history, priority, and resolution path.

Support Process & Service Boundaries

Send the information that helps us diagnose the issue — and nothing that should remain private.

WebsDocs support covers active RTD, RTC, ASG, Business Automation, billing, account, installation, and connected-service issues. New development or work outside the active service may require a separate commercial review.

GOOD TICKET

Include the facts we can act on.

Affected product, page, dashboard, domain, or workflow
Exact error text or unexpected behavior
What you expected to happen instead
Approximate time the issue occurred
Recent installation, payment, configuration, or content change
RTC Site ID, RTD Site ID, ASG Client ID, or transaction reference when relevant

NEVER SEND

Keep security credentials out of tickets.

Passwords or account login credentials
Private keys, API secrets, or full access tokens
Card numbers, CVV codes, or banking passwords
One-time passwords or verification codes
Unrelated confidential client or employee records
Personal data that is not required to investigate the issue

PRIORITY

Describe impact, not urgency alone.

Critical: Active service unavailable or major access failure.
High: Important workflow blocked with no practical workaround.
Normal: Configuration, billing, setup, behavior, or service review.
Low: Improvement, wording, or non-urgent question.

NEW TICKET

Separate different issues.

The issue affects a different WebsDocs service
The earlier ticket is already resolved or closed
The new request has a different subject or expected result
A separate billing, privacy, or lawful-use review is required
A different website, domain, Site ID, workspace, or client account is involved
The request is for a new package, estimate, or custom development scope

One Issue · One Support Record

Continue an active issue in its ticket. Open a new ticket when the issue changes.

Keeping one issue inside one support record preserves references, replies, files, status changes, and resolution history without duplicate review.

ACTIVE ISSUE Open Existing Ticket Return with your Ticket ID, email, and access code. SELF-SERVICE Read Support FAQ Check setup, billing, security, and troubleshooting answers.