Agent and widget support
Report incorrect answers, missing responses, routing problems, profile issues, widget loading, installation, domain validation, or visitor-facing behavior.
WebsDocs Support Center
Support for active WebsDocs services, AI assistants, dashboards, and billing.
Open a ticket for dashboard access, activation, AI assistant behavior, widget issues, billing or usage questions, email delivery, website integration, and existing setup problems.
Need WebsDocs support?
Create a new support ticket or log in to continue an existing support request.
Open Support Ticket
WebsDocs Client Support Workspace
Create one private support record and keep the complete issue history together.
This page is the official support workspace for active WebsDocs services. It connects your request, service references, attachments, replies, ticket status, and previous support records inside one private dashboard.
Use it for RTC Chat Agent, RTD Voice Agent, Industry Automation, activation codes, dashboards, billing and usage, email delivery, profile regeneration, installation, website integration, privacy requests, and existing managed-service issues.
After submission, WebsDocs sends a Ticket ID and access code to the email used in the form. Those details let you reopen the same ticket dashboard, read support replies, add files, clarify the issue, and continue the conversation without starting again.
Voice and realtime support
Report microphone access, call start failures, transcription problems, voice behavior, realtime connection issues, usage minutes, or Voice CRM visibility.
Dashboard and access support
Request help with dashboard login, access codes, client IDs, missing records, ticket visibility, case history, or account access.
Billing and activation review
Ask about activation codes, AI Credits, invoices, payment references, usage, top-ups, plan status, billing records, or refund review.
Profile and knowledge updates
Request company-profile.json, voice-company-profile.json, approved knowledge, response boundaries, routing, or managed profile changes.
Privacy and service records
Submit privacy, transcript, recording, data access, lawful-use, service eligibility, or account-record questions through a tracked support path.
1
Ticket created
Your request, references, and attachment are stored as one private support record.
2
Access details sent
Your Ticket ID and access code are sent to the email used during submission.
3
Support review begins
The ticket is checked, categorized, routed, and linked to the available WebsDocs records.
4
Continue in dashboard
Read replies, add details, upload another file, and follow the status until completion.
Create Ticket
Tell us what broke, changed, or needs support.
Use this support path for an existing WebsDocs service. Attach a screenshot, log, document, or JSON file if it helps us diagnose the issue faster.
- Dashboard, login, or activation issues
- AI assistant, chatbot, or widget behavior
- Billing, usage, email delivery, or integration problems
- Existing client setup or technical support
Ticket Created
Your ticket is ready.
Use the login panel to open your dashboard and view replies.
Support Ticket
Open a support ticket
Add the details below and attach a small screenshot or document if helpful.
Conversation
Latest support messages
Showing the latest 3 messages first. Open the history panel to review older records.
Login to load ticket history.
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 And Service Boundaries
Help us understand the issue clearly, safely, and without exposing sensitive information.
A useful support ticket explains what happened, what you expected, where it happened, and whether anything changed immediately before the problem started.
WebsDocs support covers active WebsDocs services and the connected setup paths described in your service. New custom development, major scope changes, unrelated third-party systems, or work outside the active service may require separate technical or commercial review.
A Strong Ticket Includes
- The affected service, page, dashboard, or workflow
- The exact error text or unexpected behavior
- What you expected to happen instead
- Approximate time the issue occurred
- Recent change, installation, payment, or configuration update
- Site ID, Voice Site ID, Client ID, or transaction reference when relevant
Never Send
- Passwords or account login credentials
- Private keys, API secrets, or full access tokens
- Card numbers, CVV codes, or banking passwords
- One-time passwords or security verification codes
- Unrelated confidential client or employee records
- Files containing personal data that is not needed for the issue
Priority Guidance
- Critical: active service unavailable or major access failure
- High: important workflow blocked with no practical workaround
- Normal: behavior, configuration, billing, or setup review
- Low: improvement request, wording change, or non-urgent question
- Use factual impact instead of marking every request urgent
- Add a safe workaround if one is currently available
When To Open A New Ticket
- The issue affects a different WebsDocs service
- The first ticket is already resolved or closed
- The new request has a different subject or expected outcome
- A separate billing, privacy, or lawful-use review is required
- A new website, domain, Site ID, or client account is involved
- The request is for a new package, estimate, or custom development scope
One Request, One Clear History
Open a new ticket for a new issue. Return to the dashboard for an active issue.
This keeps references, replies, files, status changes, and resolution notes connected in one support record and prevents duplicate review.