Answers about WebsDocs AI agents, support systems, service eligibility, payments, and project paths.

Frequently Asked Questions

Practical answers for visitors, clients, and businesses reviewing WebsDocs services.

This FAQ helps explain the main WebsDocs service paths in plain language. It covers the AI Business Agent, AI Voice Agent, Industry AI Support Systems, free and paid activation flows, dashboards, support tickets, AI Credits, managed voice minutes, website services, documentation work, payment handling, and policy review.

Some answers are suitable for general public guidance. Other topics, such as billing status, refunds, invoices, activation mismatches, private account records, dashboard access, usage limits, technical issues, or legal and privacy questions, may require a support ticket or human review before WebsDocs can provide a final answer.

WebsDocs works with legitimate businesses, organizations, and projects that can be supported safely and lawfully. Service eligibility may depend on the client’s business activity, operating country, target market, regulatory environment, and the type of AI, website, voice, or support workflow being requested.

FAQ Sections

The FAQ is organized by service area so visitors can find the right answer faster.

Getting Started

Start with the service path that matches your business need: AI agent, voice support, industry system, website service, or support ticket.

What does WebsDocs actually do?

WebsDocs builds structured digital systems for real business use. The main service areas include AI Business Agents, AI Voice Agents, Industry AI Support Systems, website development, website optimization, documentation systems, research and knowledge portals, dashboards, support-ticket workflows, and structured digital infrastructure.

The goal is not only to create pages or tools, but to help businesses organize how visitors ask questions, understand services, move toward the right next step, and receive support through a clearer digital path.

Is WebsDocs only for websites?

No. Websites are one part of WebsDocs, but the broader work includes AI-powered website support, voice-based visitor support, dashboard visibility, support routing, documentation structures, knowledge systems, service guidance, and industry-specific support flows.

Some clients need a website. Others need a Chat Agent, Voice Agent, support workflow, documentation structure, customer inquiry path, or a more complete business support system connected to their website.

Do I need to know exactly what I want before contacting WebsDocs?

No. Many clients start with a business problem rather than a finished technical brief. It is enough to explain what you want visitors, customers, or internal users to do more clearly. For example, you may need better visitor answers, better lead routing, better support handling, clearer pricing explanation, voice support, dashboard visibility, or a more professional website structure.

WebsDocs can then help identify whether the better starting point is an AI Business Agent, AI Voice Agent, Industry AI Support System, website service, documentation system, support ticket, or formal scope review.

Can I start with a free Chat Agent first?

Yes. The Free Chat Agent Generator is intended as a starter path for businesses that want to create a basic, domain-bound Chat Agent and install snippet before moving into a managed paid setup.

The free path is useful for early testing and basic website AI direction. Paid plans add stronger setup, managed profile structure, dashboard access, approved business knowledge, support routing, care, and usage control. You can start here: Free Chat Agent Generator.

Where should existing clients get help?

Existing clients should use the Support Ticket page for activation issues, dashboard access, billing or usage questions, widget behavior, microphone or voice issues, installation problems, email delivery, domain mismatch, Site ID or Voice Site ID issues, refunds, invoices, or technical troubleshooting.

Support tickets create a traceable path for review, replies, screenshots, account references, and human escalation where needed. Open a ticket here: Support Ticket.

Enquiries and Project Start

Before work begins, WebsDocs reviews the right service path, scope, eligibility, and project-start basis.

Does sending a message, ticket, or enquiry start a project?

No. Sending a message, opening a support ticket, using a contact form, asking for pricing, testing a demo, or discussing an idea does not automatically create a binding project or service engagement.

A project or managed service normally begins only when WebsDocs confirms the service path, the required scope or plan is accepted, and the required commercial step has been completed. Depending on the service, that may be a setup payment, activation purchase, deposit, invoice approval, recurring plan start, support approval, or another written project-start basis. The full rule is in Terms: Service Enquiries and Project Engagement.

What usually happens before work actually begins?

The usual path depends on the service. For public product paths such as AI Business Agent or AI Voice Agent, the process may involve plan selection, payment, activation code, business profile details, domain review, setup output, install snippet, and dashboard access. For custom website, documentation, industry, or integration work, the process may involve enquiry review, fit check, scope clarification, pricing direction, quote approval, payment step, and working setup.

Some paths are faster because they follow a defined product workflow. Others need more review because they involve custom business logic, industry-specific support, integrations, compliance concerns, complex content, or technical dependencies.

What does WebsDocs usually need before starting?

Requirements depend on the selected path. For AI Business Agent setup, WebsDocs may need business name, website URL, services, FAQs, contact direction, preferred assistant name, support rules, approved knowledge, and domain information. For AI Voice Agent setup, WebsDocs may also need voice profile details, intended voice use, page location, browser/device context, voice support rules, handoff direction, and Voice Site ID or activation details where applicable.

For custom services, WebsDocs may need project goals, content, brand assets, platform details, access coordination, existing materials, technical limitations, business rules, and clear approvals. If the project depends on a client-owned platform, provider, domain, hosting account, payment tool, AI provider, or third-party service, the client may need to provide access or coordination. The formal rule is in Terms: Client Responsibilities.

What if I am still not sure which WebsDocs path is right?

That is normal. Many visitors are comparing a few possible paths: Free Chat Agent, paid AI Business Agent, AI Voice Agent, Industry AI Support System, website development, website optimization, documentation system, research portal, or custom scope review.

If you are a new visitor, start with the public product or pricing pages. If you already have an activation code, dashboard issue, billing concern, widget issue, microphone issue, usage question, or technical problem, use the Support Ticket page so the request can be reviewed with the right context.

Payments, Activation and Usage

Payments may start a service path, but activation, setup, usage limits, and support rules still matter.

Do I usually have to pay before work starts?

Yes, in most paid-service situations there is a required payment step before substantial setup, custom work, managed activation, or implementation begins. That payment may be a setup payment, activation purchase, deposit, recurring plan payment, milestone payment, or another approved starting arrangement.

The purpose of the starting payment is to confirm that the request has moved beyond general discussion and into an actual service path. The formal wording is in Terms: Payments and Deposits.

Does payment automatically create the finished AI agent or Voice Agent?

No. Payment may start the paid activation path, but the finished agent still depends on the required activation and setup process. For a paid AI Business Agent, the client may need to complete activation with the approved website, business details, service information, support rules, FAQs, and profile requirements. For a paid Voice Agent, the client may need to complete the voice activation path, voice profile details, domain review, setup output, and install snippet process.

Activation problems, code mismatches, missing dashboard details, domain issues, or account-specific setup problems should be handled through the Support Ticket page.

What are AI Credits?

AI Credits are usage-control units for AI Business Agent conversations. They help separate setup and care from live AI usage, so clients can better understand and control consumption instead of assuming unlimited provider-backed usage.

If a credit balance is low, exhausted, or unclear, the assistant may show limits or require billing/support review. Account-specific credit status should be checked through the dashboard or Support Ticket path, not guessed from a public FAQ.

What are managed voice minutes?

Managed voice minutes are the client-facing usage unit for AI Voice Agent plans. Voice plans may include a defined number of managed minutes, and extra usage may be charged per minute depending on the selected plan and active service terms.

Voice usage, voice credits, call records, handoff state, microphone issues, dashboard visibility, or account-specific voice billing should be reviewed through the Voice CRM Dashboard or Support Ticket page.

Is the deposit, setup payment, or activation payment refundable?

Not automatically. Refund review depends on the service, payment type, project state, activation status, generated setup output, dashboard creation, profile generation, work already performed, duplicate charge review, and applicable legal requirements.

Once WebsDocs has created activation records, setup outputs, install snippets, dashboard details, company profiles, voice profiles, custom work, or other service outputs, payments may be treated differently from a simple unstarted enquiry. Refund, invoice, duplicate payment, or dispute questions should be handled through support review.

What if I am on a managed plan or recurring service arrangement?

Managed plans normally depend on the selected setup, care cycle, usage rules, support scope, and continued payment status. If the plan is monthly, yearly, or otherwise recurring, continuation of the service may depend on that recurring structure remaining active.

If payment stops, billing status changes, usage allowance is exhausted, or the account requires review, support access, dashboard visibility, AI replies, voice availability, or managed service handling may pause, reduce, or require manual review.

Do WebsDocs prices include every third-party cost?

Not always. Some WebsDocs pricing covers WebsDocs setup, care, service work, profile structure, dashboard direction, support handling, or managed implementation. External provider usage, hosting, domains, paid assets, subscriptions, payment-provider fees, API costs, model usage, platform fees, taxes, or other third-party costs may remain separate.

This is especially important for AI Business Agent, AI Voice Agent, integrations, provider-backed workflows, and high-volume usage. The full formal position is in Terms: Third-Party Tools, Platforms, and Providers.

What happens if payment is late or a billing issue is unresolved?

If payment required for the current phase or plan is late, work may pause, the schedule may shift, delivery may be delayed, recurring support may be interrupted, service access may be limited, or the account may move out of active handling until the payment issue is resolved.

Billing status, invoice questions, refund requests, duplicate charge review, credit top-up, usage review, or private account records should be handled through the Support Ticket page with the relevant website URL, client email, Site ID or Voice Site ID if available, payment reference if available, and a short description of the issue.

Timelines

Timelines depend on scope, client readiness, platform access, provider availability, and review requirements.

Are WebsDocs timelines guaranteed?

Usually no, unless a specific delivery date has been clearly accepted in writing as a fixed obligation. Most timing guidance should be treated as a realistic working estimate based on the known scope, service path, required inputs, platform conditions, and provider availability at the time. The formal rule is in Terms: Timelines and Delays.

Why can a project, activation, or support review take longer than expected?

Timing can change because digital work depends on more than one step. A project may take longer if the scope expands, content is missing, approvals are delayed, client access is unavailable, domain verification fails, activation details mismatch, third-party platforms behave differently than expected, provider limits appear, or the real business logic is broader than the original request.

For AI Business Agent or AI Voice Agent work, timing can also be affected by profile completeness, approved knowledge quality, installation access, dashboard details, usage/billing status, microphone or browser conditions, provider availability, and support-ticket review requirements.

What most often causes delays?

Common causes include missing content, unclear instructions, delayed feedback, access problems, wrong domain information, activation code mismatch, incomplete business profile details, payment or billing issues, platform restrictions, third-party provider delays, changing requirements, and review rounds expanding beyond the original scope.

What if I have a strict launch date?

Tell WebsDocs as early as possible. A true fixed launch date should not be assumed. It needs to be reviewed, accepted, and documented clearly before the work is treated as time-critical or fixed-date delivery.

If the launch depends on client materials, platform access, payment completion, domain readiness, provider uptime, or third-party approvals, those dependencies must be realistic before a date can be treated as reliable.

What if the project, activation, or support process pauses for a while?

Then the original timing assumptions may no longer apply. A paused project may need to be re-slotted, re-reviewed, reactivated, or restarted under a revised working timeline. If the gap is long enough, information, provider rules, website conditions, pricing, billing status, or technical requirements may need to be checked again before continuing. The formal position is in Terms: Pauses, Cancellation, and Termination.

Cancellation, Activation and Service Pauses

Cancellation handling depends on the service stage, setup progress, generated outputs, usage, and support review.

What happens if I cancel before the service really starts?

If a paid service has not materially started, WebsDocs may review the cancellation request based on the payment type, order status, service path, and whether any administrative, activation, setup, scheduling, or provider-backed work has already begun.

Cancellation before visible delivery does not always mean that no work has started. Some services begin with order review, activation-code handling, profile preparation, dashboard record creation, domain checks, setup planning, provider preparation, or reserved service capacity. The formal wording is in Terms: Pauses, Cancellation, and Termination.

What if I cancel after an activation code is created?

If an activation code has already been created, issued, reserved, or connected to a paid service path, the order has usually moved beyond a simple unstarted enquiry. WebsDocs may review whether the code has been used, whether setup records have been created, whether the code is tied to a specific plan or domain, and whether any generated setup output already exists.

A created but unused activation code may be reviewed differently from a used activation code. However, code creation may still involve administrative handling, payment processing, fraud checks, entitlement reservation, setup preparation, or support capacity. If any refund or cancellation is approved at this stage, WebsDocs may deduct applicable processing, administrative, activation, provider, or already-performed setup costs where permitted.

What if I cancel after the Chat Agent profile or setup output is generated?

Once WebsDocs has generated a Chat Agent profile, company-profile.json, setup record, dashboard details, install snippet, domain-bound configuration, support rules, or other setup output, the service is normally treated as started or delivered in part.

In that situation, setup or activation payments are normally non-refundable because the core preparation work has already been performed and the generated output has been created for the client’s website or business. Later cancellation may stop future support, care, updates, or managed service continuation, but it does not automatically reverse completed setup work.

What if I cancel after the Voice Agent profile or voice setup output is generated?

Once a Voice Agent profile, voice configuration, voice install snippet, Voice Site ID, Voice CRM Dashboard record, voice entitlement, or voice setup output has been created, the voice service is normally treated as started or delivered in part.

Voice setup can involve provider-backed preparation, dashboard records, profile generation, usage entitlement, installation guidance, testing, and support handoff configuration. For that reason, cancellation after voice setup generation is normally handled as a service stop or managed-plan cancellation, not as a simple refund of unstarted work.

Are AI Credits, usage, or voice minutes refundable?

Consumed AI Credits, used voice minutes, provider-backed usage, processed conversations, voice sessions, generated outputs, and already-delivered support work are normally not refundable. Unused plan balances, promotional minutes, included allowances, or remaining credits may be handled according to the active plan, payment page, support review, and any applicable legal requirement.

If a client believes a usage charge, credit deduction, duplicate payment, or billing event is incorrect, they should open a support ticket with the website URL, client email, Site ID or Voice Site ID if available, payment reference if available, and a short description of the issue.

What happens if I cancel after custom work has started?

Then payment already earned for planning, setup, implementation, review effort, provider preparation, generated outputs, support review, and completed work generally remains payable. In many cases, that means the deposit, setup payment, activation payment, or starting payment will be treated as earned where meaningful work has already happened.

If the value of completed work goes beyond what has already been paid, there may also be an additional amount due depending on the accepted scope, project stage, and work performed.

What if the project does not cancel but just goes quiet?

If a client stops replying, does not send needed materials, delays approvals, does not complete activation, fails to provide access, or leaves a support process inactive for too long, the project or setup may be treated as paused or inactive.

A paused service may need reactivation, re-review, updated billing review, new scheduling, renewed provider checks, or additional setup work before it can continue. Original timing, pricing, or plan assumptions may no longer apply after a long pause.

Can WebsDocs stop working on a project or service?

Yes. WebsDocs may pause, limit, refuse, suspend, or terminate work where there is repeated non-payment, unresolved billing issue, abusive conduct, unlawful requested use, misleading business claims, unsafe AI use, serious non-cooperation, provider restriction, policy concern, platform abuse, or a working condition that has become unreasonable or unsafe to continue.

WebsDocs may also pause or decline service where the client’s business activity cannot be lawfully or safely supported in the relevant operating jurisdiction, target market, platform environment, payment-provider context, or AI-provider policy environment. The formal rule is in Terms: Pauses, Cancellation, and Termination.

Ownership and Rights

Clients own their valid materials, while WebsDocs keeps its reusable systems, methods, frameworks, and internal operating logic.

Do I still own the materials I provide?

Yes, in general you retain ownership of materials you already owned and validly provided for use in the work. That may include your logo, business name, approved copy, internal content, documents, images, product information, policies, service descriptions, or other assets you had the right to use before the project started.

By giving those materials to WebsDocs, you allow WebsDocs to use them for the project, setup, profile generation, support knowledge, dashboard records, voice profile, documentation, or related service output, but that does not usually mean you lose ownership of those original materials. The formal wording is in Terms: Intellectual Property and Materials.

Who owns the final project or generated setup output?

The client’s right to receive and use the final agreed deliverable, generated setup output, or activated service normally depends on full payment of the relevant amount and the handover structure agreed for that service. Final custom deliverables are not treated the same way as unpaid drafts, withheld materials, unused concepts, internal working assets, or reusable WebsDocs systems.

For AI Business Agent or AI Voice Agent services, the client may receive the right to use the generated profile, install snippet, dashboard access, or service output according to the active plan and payment status, without acquiring ownership of the entire WebsDocs framework, worker logic, billing system, support system, prompts, admin tooling, RAG/indexing process, or reusable software stack.

Do I get every draft, concept, and internal file?

Usually no. A project does not automatically include transfer of every internal preparation file, every unused concept, every intermediate draft, every modular code fragment, every prompt, every automation rule, every admin function, or every internal system used during development.

Delivery usually covers the agreed final deliverable, agreed handover level, or active client-facing service output, not every internal material created along the way. The formal rule is in Terms: Intellectual Property and Materials.

Does paying for a project mean I own all WebsDocs methods or systems used in it?

No. WebsDocs keeps ownership of its pre-existing methods, frameworks, reusable systems, internal logic, structured workflows, templates, modular approaches, software components, AI orchestration methods, support workflows, billing logic, dashboard systems, and broader know-how unless a specific written agreement says otherwise.

A client may receive the agreed deliverable and the right to use it as part of the project or active service, without acquiring ownership of the entire underlying WebsDocs operating framework.

Can WebsDocs show public work in a portfolio or as an example?

Usually yes, unless a separate written agreement says the work will remain confidential or not be used in that way. Public-facing work, public websites, public AI agent examples, public service outputs, and non-confidential project outcomes may be referenced as part of normal business presentation. The full formal wording is in Terms: Intellectual Property and Materials.

Privacy, Submitted Materials and Support Data

WebsDocs uses submitted information to respond, provide services, operate support, prepare profiles, and manage requested work.

What happens to the information I send in an enquiry?

Information submitted through an enquiry may be used to understand the request, respond to the question, assess service fit, discuss a possible project, prepare next steps, or continue communication started by the visitor or client.

WebsDocs is not designed as a data brokerage business. The practical purpose of information handling is to support communication, website function, project review, support handling, activation, billing review, and service delivery. See Privacy Policy.

What about files, documents, screenshots, and project materials I submit?

Submitted materials may be used to review the project, understand the scope, prepare a website, generate or improve an AI profile, create support knowledge, investigate a ticket, review dashboard issues, check billing or usage problems, or support the service requested by the client.

Clients should only submit materials they have the right to provide and that are appropriate for the intended work. This may include text, documents, screenshots, business information, policies, service descriptions, product information, website URLs, support evidence, and technical context. See Terms: Acceptable Use of Submitted Content and Privacy Policy.

Does WebsDocs sell my data?

WebsDocs is not built around selling client or visitor data as a business model. Information is used for practical service purposes, such as responding to messages, operating website features, managing support tickets, preparing service outputs, processing activation, reviewing billing or usage issues, and delivering requested work.

Some third-party tools may process limited information where needed for hosting, payment, analytics, email delivery, AI processing, voice processing, support workflows, or other service infrastructure. See Privacy Policy.

Can third-party services process some information?

Yes. Modern digital services often depend on third-party infrastructure such as hosting, analytics, forms, payment systems, email systems, support tools, provider APIs, AI providers, voice providers, cloud services, and security tools. These services may process information needed to operate the requested function.

For example, an AI Business Agent may require business profile and conversation context to generate a reply. An AI Voice Agent may require voice session handling, microphone/browser interaction, transcript or call context where enabled, and provider-backed voice processing. Support tickets may require screenshots, website URLs, account references, or technical details to investigate the issue. See Privacy Policy and Terms: Third-Party Tools, Platforms, and Providers.

Where do I read the full privacy position?

Use the main Privacy Policy. That page is the formal place for information handling, contact information, submitted materials, website data, AI and voice service data, technical information, support-ticket data, and privacy-related questions.