The general terms governing WebsDocs services, AI agents, voice systems, dashboards, support workflows, and digital projects.

Terms and Conditions

General terms for using WebsDocs, requesting services, activating AI products, and working with WebsDocs support systems.

These Terms and Conditions set out the general rules, conditions, and working principles that apply to the WebsDocs website, public pages, free resources, AI Business Agent services, AI Voice Agent services, Industry AI Support Systems, support-ticket workflows, dashboards, activation pages, payment pages, website services, documentation systems, research portals, and custom digital work.

WebsDocs provides a combination of public information, free tools, paid activation paths, managed AI services, voice services, support systems, dashboards, business websites, documentation structures, and custom project work. These areas do not all operate in the same way. Some pages are informational, some are self-service or guided setup paths, some involve generated outputs, and some work begins only after scope review, payment, activation, support approval, or another written project-start basis.

These terms should be read together with any page-specific service notes, pricing guidance, FAQ explanations, Payment Information, Privacy Policy, support-ticket instructions, activation-page notices, dashboard notices, quotes, invoices, Scopes of Work, or other project documents that may apply to a particular service. Where a separate written agreement is entered into for a specific project, that written agreement may supplement or override parts of these general terms to the extent expressly stated for that project.

By using the WebsDocs website, accessing public materials, submitting an enquiry, opening a support ticket, using an activation page, accessing a dashboard, making a payment, using an AI Business Agent or AI Voice Agent, or engaging WebsDocs for work, you acknowledge that you have reviewed these terms and agree to use the website and related services on that basis.

If you are an existing client with an activation issue, dashboard issue, billing or usage concern, widget problem, microphone or voice issue, invoice question, refund-review request, or account-specific support matter, use the Support Ticket page so WebsDocs can review the request with the correct context.

Website Use

The WebsDocs website is intended for lawful browsing, reasonable use, genuine service review, and legitimate support interaction.

Visitors may use the WebsDocs website to explore services, review public pages, access available free materials, compare pricing direction, use planning or guidance features, test public demos, access activation paths, open support tickets, and contact WebsDocs regarding legitimate project, product, or service-related matters.

The website is intended to support clear public information, structured service exploration, AI Business Agent guidance, AI Voice Agent guidance, Industry Solutions review, website service enquiries, support-ticket handling, and practical client communication.

You agree not to use the website, AI tools, voice tools, dashboards, forms, support tickets, activation pages, demos, or service pathways in any unlawful, abusive, deceptive, malicious, automated, or disruptive manner. This includes attempting to damage the website, interfere with service operation, gain unauthorized access, submit fraudulent or misleading requests, impersonate another person or business, transmit harmful code, overload infrastructure, abuse support channels, scrape or copy materials in an excessive or exploitative way, or use the website in a way intended to harm WebsDocs, its users, its systems, its providers, or third parties.

You also agree not to misuse contact forms, support tickets, project-start pathways, planning tools, calculators, dashboards, demos, AI agents, voice agents, or activation systems. These features are intended for genuine enquiry, service use, support review, project planning, reasonable evaluation, and normal website interaction. They must not be used for spam, automated abuse, false requests, hostile testing, extraction of confidential working methods, manipulation of usage, or conduct designed to disrupt normal business operation.

WebsDocs may monitor, restrict, suspend, block, rate-limit, investigate, or refuse access where there is a reasonable belief that use is abusive, unlawful, technically harmful, fraudulent, excessive, unsafe, misleading, or inconsistent with the intended purpose of the site or service. WebsDocs is not obligated to preserve access to any page, tool, dashboard, activation route, support workflow, or resource where misuse is suspected or where operational protection reasonably requires restriction.

Website content is provided to help visitors understand the business, explore service fit, and choose the right next step. Public pages may contain general descriptions, guidance, pricing direction, examples, demos, service explanations, plan structures, support paths, or planning routes, but they do not create a service contract merely by being viewed. Browsing the website, reading a service page, using a public planning feature, or testing a demo does not by itself guarantee acceptance of a project, priority handling, technical support, dashboard access, activation approval, or delivery of paid work.

Service Enquiries and Project Engagement

An enquiry, demo use, support ticket, or service discussion does not by itself create a binding engagement.

Visitors may contact WebsDocs to ask questions, discuss possible work, request an estimate, review pricing direction, explore service fit, test a demo, open a support ticket, or begin a project conversation. These early interactions are part of the general enquiry, support, and assessment process. They help identify whether there is a reasonable fit, what type of service may be needed, and whether the request can be structured appropriately.

No binding project or managed-service engagement is created merely because a person uses a contact form, sends an email, opens a ticket, asks for clarification, appears interested in a service, uses a planning tool, tests a demo, receives a general response, discusses possible scope, or reviews a public pricing page.

Formal engagement normally begins only once the relevant service has been sufficiently defined and accepted through one or more of the following: written scope confirmation, approved quote, invoice approval, deposit payment, setup payment, activation purchase, activation-code issuance, recurring plan start, dashboard setup, explicit written acceptance, signed agreement, or another clearly documented basis for starting work.

For AI Business Agent and AI Voice Agent services, the engagement may involve plan selection, payment, activation handling, profile generation, domain review, dashboard record creation, install snippet generation, AI Credits, voice-minute entitlement, and support handling. Service access may depend on successful activation, lawful-use review, payment status, domain conditions, provider availability, and completion of required setup information.

WebsDocs reserves the right to decide whether a proposed project, client, business category, support request, or service use is suitable for acceptance or continuation. Acceptance may depend on clarity of requirements, practical feasibility, service fit, schedule availability, technical conditions, communication quality, legal or policy concerns, platform constraints, provider restrictions, payment-provider limits, AI-provider rules, jurisdictional eligibility, and the appropriateness of the requested work relative to the WebsDocs service model.

WebsDocs is not required to accept every enquiry, approve every activation, continue every preliminary discussion, support every business category, or convert every support ticket into a paid or custom-service obligation. Where a service is accepted, the engagement will generally be limited to the scope, plan, support level, usage allowance, dashboard access, or deliverable actually described and accepted.

Informal discussion, exploratory comments, early suggestions, public page content, demos, FAQs, general pricing, or broad service examples should not be treated as automatic inclusion of additional features, support, deliverables, integrations, credits, voice minutes, custom routing, legal review, or obligations that were not expressly accepted as part of the service or project.

Payments, Deposits and Paid Activation

Paid work, activation, managed service access, and substantial setup normally begin only after the required payment step is completed.

WebsDocs provides a mixture of public service pages, free starter tools, paid activation paths, AI Business Agent plans, AI Voice Agent plans, support workflows, dashboards, website services, documentation systems, managed services, and custom digital work. Because these paths are different, payment structures may vary by service.

Some work may be handled through fixed setup pricing, some through paid activation, some through AI Credit or managed voice-minute usage, some through recurring care or support plans, some through staged custom scope, and some through a hybrid structure that combines setup work with later ongoing service. Regardless of the structure used, WebsDocs generally reserves the right to require payment, deposit payment, activation payment, recurring payment, or another confirmed financial commitment before beginning substantial work or enabling paid service access.

For AI Business Agent services, payment may relate to setup, activation, company profile generation, dashboard record creation, domain-bound install snippet generation, support-routing setup, managed care, AI Credits, usage visibility, or related service access. For AI Voice Agent services, payment may relate to voice setup, voice profile generation, Voice Site ID records, Voice CRM Dashboard access, managed voice minutes, voice entitlement, handoff configuration, usage visibility, and related support.

For custom project work, an upfront payment or deposit is normally required before active implementation begins. Unless a different arrangement is clearly stated in writing, this upfront payment is commonly treated as the amount required to reserve working capacity, begin structured planning, allocate project time, perform setup review, and move the work from general discussion into an actual service phase.

The existence of a quote, estimate, pricing page, demo, project discussion, support ticket, or public plan description does not by itself obligate WebsDocs to begin work, create an activation record, generate a profile, issue a dashboard, provide credits, enable voice access, or continue support before the relevant payment and required setup steps have been completed.

Where a project is divided into a starting payment and a remaining balance, the remaining balance will generally become due before final delivery, final file transfer, launch support completion, public release, deployment handover, dashboard handover, generated setup release, or comparable end-stage release of the work, unless another schedule has been agreed in writing.

Managed services, support arrangements, credit-based services, voice-minute services, and ongoing service plans may be billed on a recurring or usage-related basis according to the plan selected or agreed. Continued service may depend on continued payment, active entitlement, sufficient credits, available managed voice minutes, billing status, provider availability, and compliance with acceptable-use requirements.

WebsDocs may suspend, reduce, limit, or discontinue ongoing service activity where recurring charges are unpaid, overdue, reversed, disputed without good-faith basis, usage allowance is exhausted, credit balance is insufficient, managed voice-minute allowance is consumed, billing records require review, or payment integrity concerns require verification.

Payments must be made through the payment method, invoicing route, checkout flow, activation route, or billing arrangement approved by WebsDocs. A payment may be refused, delayed, reversed, or subject to verification where fraud concerns, chargeback risk, technical payment issues, duplicate-payment review, inconsistent account information, or provider restrictions reasonably require additional confirmation.

Unless expressly stated otherwise, published prices, quotes, ranges, and plan amounts relate to the WebsDocs service component itself and do not necessarily include all third-party costs that may arise. This may include hosting, domains, premium assets, external subscriptions, API usage, model-provider usage, voice-provider usage, licensed software, plugins, platform fees, payment processing charges, taxes, or other external service costs where applicable.

Where a pricing page, estimator, package structure, AI plan, voice plan, activation page, or support path refers to a setup payment, activation payment, deposit amount, monthly care, annual care, AI Credits, managed voice minutes, or project-start amount, that payment or allowance should be understood according to the relevant service path. It is not a guarantee that all possible later additions, expansions, integrations, provider usage, high-volume usage, post-scope requests, or custom support are included automatically.

WebsDocs reserves the right to pause work or limit access where invoices, deposits, activation payments, recurring charges, usage top-ups, credit purchases, or other required payments remain unpaid beyond a reasonable period. A payment delay may affect delivery timing, review scheduling, dashboard access, support continuity, activation, launch preparation, AI response availability, voice availability, or the order in which work is handled.

Timelines and Delays

Timing depends on scope, activation readiness, client inputs, provider availability, payment status, and support review requirements.

WebsDocs may provide timing guidance through service pages, pricing material, project discussions, estimates, quotes, planning tools, support tickets, activation pages, or direct communication. Unless a specific delivery deadline is expressly confirmed in writing as binding, timing statements should be understood as working estimates only.

Timing guidance reflects a reasonable expectation based on the information available at the time, not an unconditional guarantee that work, activation, dashboard setup, profile generation, support review, voice setup, or delivery will be completed by a particular date regardless of later changes, third-party issues, missing information, usage issues, billing review, or project complexity.

Project and service timing may depend on many factors, including scope clarity, content readiness, business-profile completeness, AI profile requirements, voice profile requirements, domain review, dashboard creation, activation-code verification, provider setup, hosting or platform conditions, AI or voice configuration, integration depth, revision volume, approval speed, account access, third-party dependencies, support-ticket volume, external outages, and whether the service remains within the originally expected scope.

WebsDocs is not responsible for delay caused by client-side inaction or client-side change. This includes delays arising from missing content, incomplete business information, missing approvals, delayed feedback, unavailable decision-makers, unshared credentials, changed instructions, changed service expectations, provider-account issues, domain problems, hosting limitations, legal or compliance approval delays, payment delays, billing review, or circumstances where progress depends on the client or the client’s environment.

WebsDocs is also not responsible for timing disruption caused by third-party systems beyond its reasonable control. This may include hosting platforms, registrars, infrastructure providers, email systems, payment gateways, AI providers, voice providers, browser changes, API changes, external platform restrictions, plugin or software issues, network outages, payment-provider reviews, or other external service problems.

If the project or service is materially expanded after work begins, the original timing assumptions may no longer apply. Additional features, added pages, broader integrations, heavier review activity, new business logic, more AI knowledge work, new voice workflows, extra content preparation, more advanced routing, more languages, new technical environments, or newly introduced deliverables may all extend the timeline.

Where delay or interruption continues for a meaningful period, WebsDocs may reclassify the project, activation, setup, support case, or managed-service request as paused, inactive, rescheduled, or subject to a revised start window. A project is not guaranteed uninterrupted daily progress merely because it has begun. Work may move in phases and may depend on review intervals, provider availability, and required client input.

If a client needs a specific fixed delivery date, launch window, activation date, support response commitment, or critical timing requirement, that requirement should be raised clearly before the service is accepted. WebsDocs will only be bound by a fixed timing obligation where that obligation is expressly accepted in writing as part of the relevant project or service arrangement.

Pauses, Cancellation, Activation, and Service Termination

Cancellation handling depends on the service stage, payment type, activation progress, generated outputs, usage, and completed work.

A client may decide not to proceed, or a project may become inactive, delayed, paused, or effectively abandoned because of missing materials, missing approvals, changed priorities, payment failure, communication breakdown, incomplete activation, unresolved support issues, or other practical causes. These terms set a general baseline for how those situations are handled.

If a paid service is cancelled before substantial work has begun, WebsDocs may review the request based on the payment type, order status, service path, and whether any administrative handling, payment processing, activation-code creation, entitlement reservation, scheduling, provider preparation, or setup review has already begun.

If an activation code has already been created, issued, reserved, or connected to a paid Chat Agent, Voice Agent, or related service path, the order has usually moved beyond a simple unstarted enquiry. A created but unused activation code may be reviewed differently from a used activation code, but code creation may still involve administrative handling, payment processing, entitlement preparation, setup capacity, and provider or support preparation.

Once a Chat Agent profile, company-profile.json, dashboard record, domain-bound install snippet, setup output, support routing structure, or related generated output has been created, the setup or activation work is normally treated as started or delivered in part. In that situation, setup or activation payments are normally non-refundable because the core preparation output has already been created for the client’s website or business.

Once a Voice Agent profile, voice-company-profile.json, Voice Site ID, Voice CRM Dashboard record, voice install snippet, voice entitlement, handoff configuration, or voice setup output has been created, the voice service is normally treated as started or delivered in part. Later cancellation may stop future support, care, updates, or managed service continuation, but it does not automatically reverse completed setup work.

Free self-service regeneration of profile files does not change the refund position for paid setup already performed. A client may be able to regenerate a profile file themselves, but WebsDocs-managed activation, dashboard creation, install output, entitlement setup, provider preparation, support review, and manual work already performed may still be treated as completed service activity.

Consumed AI Credits, used voice minutes, provider-backed usage, processed conversations, voice sessions, generated outputs, and already-delivered support work are normally not refundable. If a client believes a usage charge, credit deduction, duplicate payment, or billing event is incorrect, the issue should be raised through a support ticket with the relevant website URL, client email, Site ID or Voice Site ID, payment reference if available, and a short explanation.

If custom work is cancelled after work has begun, the client remains responsible for payment relating to work already performed, project time already allocated, planning already completed, review effort already undertaken, generated outputs already created, and any non-recoverable third-party cost already incurred in connection with the project.

Where a project or service has progressed beyond its initial phase, WebsDocs may also invoice for additional work completed but not yet paid for if the value of completed work exceeds the amount already received. This may include custom implementation, documentation work, structured drafting, design work, technical configuration, provider setup, AI knowledge preparation, voice setup, content alignment, revision effort, or other service activity already carried out in good faith.

A project, activation, support case, or managed service may also be treated as paused or inactive where the client stops responding, repeatedly delays approvals, fails to provide materials, does not complete required payment, becomes unavailable for a prolonged period, fails to complete activation, or otherwise prevents the work from moving forward in a normal way.

If a paused project or service later resumes, WebsDocs may revise the timeline, working window, pricing basis, support status, activation status, or technical assumptions to reflect the practical reality at the time of reactivation. This may be necessary where the prior working slot has been lost, service records have become stale, provider rules have changed, billing status needs review, or re-entry requires renewed checking.

WebsDocs may terminate, suspend, or refuse continuation where there is abusive conduct, unlawful requested use, repeated payment failure, persistent bad-faith behaviour, impossible working conditions, misuse of staff time, platform abuse, provider restriction, payment-provider concern, AI-provider restriction, or material non-cooperation that makes the service impractical or unsafe to continue.

Intellectual Property, Profiles, and Materials

Ownership, usage rights, and transfer depend on the type of material, service output, and accepted scope.

WebsDocs may work with a mixture of client-supplied materials, WebsDocs-created materials, generated profile files, reusable internal frameworks, support workflows, public infrastructure, third-party tools, and custom project outputs. Because those categories do not all carry the same ownership position, this section explains the general basis on which rights are understood unless a separate written agreement provides a more specific arrangement.

The client generally retains ownership of materials they validly owned before the project and that they provide to WebsDocs for use in the service. This may include business names, logos, photographs, approved copy, documents, datasets, policy text, existing brand materials, internal reference content, customer-facing content, service descriptions, FAQs, and other assets supplied by the client or on the client’s behalf.

By providing those materials to WebsDocs, the client grants WebsDocs the right to use, adapt, structure, format, process, store, index, and configure them to the extent reasonably necessary to carry out the requested service, including website work, documentation work, AI Business Agent setup, AI Voice Agent setup, Industry AI Support Systems, dashboard records, support-ticket handling, profile generation, and related service delivery.

The client represents that they have the right to supply any material submitted for use in the work and that its use as instructed will not knowingly infringe the rights of another party. WebsDocs is not responsible for independently verifying rights in every asset provided by the client. If a dispute arises because the client submitted material they did not have the right to use, responsibility for that issue remains with the client to the extent caused by the client’s unauthorized submission or instruction.

WebsDocs retains ownership of its pre-existing methods, frameworks, internal systems, reusable logic, modular design patterns, development processes, drafting methods, business structures, estimators, workflow systems, pricing models, technical approaches, reusable code components, prompt structures, service templates, profile-generator logic, support workflows, billing logic, dashboard systems, RAG/indexing methods, internal documentation methods, and other know-how that existed before the project or forms part of the broader WebsDocs operating system.

A client engagement, activation purchase, generated profile, dashboard setup, or support request does not transfer ownership of the underlying WebsDocs framework, worker logic, admin tooling, billing system, support system, prompt methods, profile generator, RAG/indexing process, database structure, reusable software stack, or internal operating methods unless such transfer is expressly agreed in writing.

Where WebsDocs creates custom material specifically for a client project, the client’s right to receive and use the final agreed deliverable will usually arise upon full payment of the relevant project amount, subject to the project’s actual scope, selected plan, and any stated exclusions. Draft-stage work, unpaid work, withheld deliverables, unapproved material, or internal working assets may remain under the control of WebsDocs until the commercial conditions for transfer or release have been met.

For AI Business Agent, AI Voice Agent, and Industry AI Support System services, a client may receive the right to use generated profile files, install snippets, dashboard access, approved knowledge structures, voice profile outputs, or other client-facing service outputs according to the active plan, payment status, activation status, and service scope. This does not mean the client owns the underlying WebsDocs technology, generator logic, worker code, model gateway structure, billing logic, admin tooling, or support infrastructure.

Unless expressly agreed otherwise, WebsDocs is not required to transfer every draft, unused version, internal working file, modular code fragment, prompt structure, source preparation file, admin script, database schema, deployment method, internal planning asset, or intermediate system component generated or used during the project. The transfer obligation is generally limited to the final agreed deliverable or agreed handover level, not to all internal materials used in getting there.

WebsDocs may retain the right to display or reference completed public-facing work in a portfolio, case example, capability context, or other business presentation unless the parties have agreed in writing that the work will remain confidential or not be used in that way. This does not authorize WebsDocs to disclose confidential internal business information where a project clearly required confidentiality, but it does permit normal business-level reference to public work unless excluded.

Acceptable Use of Submitted Content and Business Information

Content, business details, support materials, and profile inputs submitted to WebsDocs must be lawful, authorized, accurate, and suitable.

Clients, enquirers, and other users must not submit material to WebsDocs that is unlawful, infringing, deceptive, malicious, abusive, defamatory, unauthorized, misleading, technically unsafe, or inappropriate for the intended service relationship. This includes material that violates intellectual-property rights, privacy rights, confidentiality obligations, data-protection obligations, sanctions restrictions, criminal law, provider policies, or the legitimate rights of another person or business.

Submitted content may include website content, service descriptions, FAQs, policies, screenshots, documents, customer support material, business claims, product information, voice instructions, profile-generation inputs, support-ticket evidence, payment references, dashboard references, or other information used for WebsDocs services. The client remains responsible for the substance, legality, accuracy, and authority behind submitted material.

WebsDocs may refuse to use, host, process, structure, publish, index, convert into an AI profile, convert into a voice profile, include in support knowledge, or work with content where there is a reasonable basis to believe that the content is unlawful, improperly obtained, materially misleading, technically unsafe, commercially abusive, reputationally dangerous, provider-prohibited, jurisdictionally restricted, or materially inconsistent with responsible service use.

The client remains responsible for the substance of the content they ask WebsDocs to include, structure, publish, use in an AI profile, use in a voice profile, use in an industry support flow, or use in a customer-facing support process. This is especially important where content concerns legal claims, medical claims, financial claims, regulated statements, public promises, public guarantees, compliance-sensitive positioning, adult or age-restricted business categories, sector-specific restrictions, or other areas where accuracy and authority depend on the client’s own responsibility.

WebsDocs may support lawful, legitimate businesses where the client’s activity is permitted in the client’s operating jurisdiction and target market and can be supported safely within applicable provider, payment, platform, and AI/voice service rules. Where a business activity is unlawful, restricted, prohibited, high-risk, misleading, or not supportable in the relevant jurisdiction or provider environment, WebsDocs may decline, limit, pause, or require additional review before providing or continuing service.

If the client requests use of content that requires licenses, permissions, model/provider permissions, legal rights, content approvals, customer consent, or third-party authorizations, the client must ensure those permissions exist before asking WebsDocs to proceed. If disputes arise because the client submitted or instructed use of material without adequate authority, the client remains responsible for that issue to the extent it arose from their unauthorized or improper instruction.

Where WebsDocs receives material that appears unsafe, inconsistent, incomplete, unauthorized, or unsuitable, WebsDocs may ask for clarification, decline to use it, delay implementation, limit support, or recommend a different working approach. This is part of responsible service handling and should not be treated as a breach of service merely because WebsDocs chooses not to implement content blindly where a legitimate concern exists.

Limitation of Liability

Liability is limited to a reasonable level connected to the actual WebsDocs service relationship and the specific service involved.

To the maximum extent reasonably permitted by applicable law, WebsDocs will not be liable for indirect, incidental, special, consequential, punitive, exemplary, or remote losses arising out of or related to use of the website, reliance on public materials, free resources, demos, profile generators, AI tools, voice tools, support workflows, dashboards, public pricing, third-party provider failure, interruption of external services, client delay, misuse of delivered assets, or business decisions made by the client or by other parties outside WebsDocs control.

This includes, without limitation, loss of profit, loss of revenue, loss of opportunity, lost data, reputational loss, search-ranking loss, conversion loss, business interruption, platform-change loss, provider-outage loss, payment-provider issue, AI-provider issue, voice-provider issue, or loss arising from external circumstances beyond the direct scope of the agreed service.

Where WebsDocs has entered into a paid service relationship with a client, any direct liability legally established against WebsDocs in connection with that specific service will, to the maximum extent reasonably permitted, be limited to the amount actually paid by the client to WebsDocs for the specific service, project, phase, activation, billing period, or scoped engagement giving rise to the claim. Liability for one service does not extend to unrelated work, unrelated billing periods, unrelated projects, or unrelated service paths.

WebsDocs will not be liable for losses caused by client-supplied content, inaccurate business information, unlawful client instructions, client-owned accounts, client delays, missing approvals, unauthorized submitted material, domain or hosting issues, third-party provider policy changes, registrar issues, AI provider outages, voice provider outages, payment-gateway issues, browser/platform changes, microphone or device conditions, security issues in systems not controlled by WebsDocs, or other external or client-side causes outside the direct operational control of WebsDocs.

WebsDocs will not be liable for problems caused by a client using generated profile files, free templates, free tools, starter materials, AI outputs, voice outputs, or public guidance without reviewing whether they are suitable for the client’s own business, jurisdiction, legal requirements, customer promises, technical environment, or operational reality.

Nothing in these terms is intended to exclude liability to the extent that liability cannot lawfully be excluded under applicable law. However, where the law allows liability to be limited, restricted, or allocated reasonably, these terms are intended to do so. The client agrees that any concern relating to a service should first be approached in good faith as a practical support, billing, delivery, or service issue to be clarified and narrowed before escalation.

The client further agrees that WebsDocs pricing, payment model, free-resource model, activation structure, AI Credit model, voice-minute model, and managed-service structure are set on the basis that liability is limited in this way. The commercial model is not designed around accepting unlimited exposure for downstream outcomes that depend on many external variables.

Contact and Terms Questions

Questions about these terms should be raised through the appropriate WebsDocs channel.

If you have a general question about these Terms and Conditions, you may contact WebsDocs through the normal contact pathways listed on the site. If the question relates to an active service, support ticket, dashboard access, activation code, billing record, AI Business Agent, AI Voice Agent, generated profile, invoice, refund review, usage record, or account-specific matter, the Support Ticket page is usually the better route.

If you are already engaged in an active project or paid service and believe a particular term is unclear in relation to that work, the correct approach is to raise the question in the context of the actual scope, quote, invoice, activation record, dashboard record, payment reference, or written arrangement involved.

WebsDocs may update these Terms from time to time to reflect operational change, service development, AI or voice system changes, payment structure updates, support workflow changes, legal adjustment, policy refinement, or broader business restructuring. Updated terms will apply from the point they are published unless a separate written agreement provides otherwise for a specific project already underway.

For active support, billing, activation, dashboard, AI, voice, invoice, refund-review, or account-specific questions, use Support Ticket. For general business enquiries, use Contact.

Last updated: May 25, 2026

Definitions

Certain words on this page are used in a general legal, technical, and operational sense.

In these Terms and Conditions, the words “WebsDocs,” “we,” “us,” and “our” refer to the WebsDocs business, website, service operation, AI systems, support systems, dashboards, and related service channels presented through the WebsDocs platform and web presence.

The words “you,” “your,” “user,” “visitor,” and “client” refer, depending on context, to the person, business, organization, or entity using the website, accessing materials, making an enquiry, opening a support ticket, using an activation path, accessing a dashboard, or engaging WebsDocs for work.

The word “website” refers to the WebsDocs site and its related public pages, service pages, product pages, tools, forms, demos, resources, support paths, activation pages, dashboards, and related digital content made available through the WebsDocs web presence.

The word “services” refers to paid, structured, managed, support, or custom work offered by WebsDocs, including AI Business Agent services, AI Voice Agent services, Industry AI Support Systems, support-ticket workflows, dashboard access, website work, documentation work, research portals, activation handling, profile generation, managed care, usage-based services, and other digital service activity described through the business.

The words “AI Business Agent,” “Chat Agent,” or “Business Agent” refer to WebsDocs website-based AI assistant services that may use business profile information, approved knowledge, support-routing rules, install snippets, dashboard records, AI Credits, and related setup or managed service features.

The words “AI Voice Agent” or “Voice Agent” refer to WebsDocs voice-based website support services that may use voice profiles, voice install snippets, Voice Site IDs, Voice CRM Dashboard records, managed voice minutes, voice session handling, handoff rules, provider-backed voice processing, and related support or usage features.

The words “activation code” refer to a code, token, reference, or similar activation method issued, reserved, or used to start or connect a paid service path such as Chat Agent, Voice Agent, dashboard setup, entitlement, or related activation flow. Activation codes may have an expiry period. If an activation code is not used within the allowed timeframe, it may expire and require validation or revalidation before use.

Where WebsDocs allows free validation or revalidation of an unused activation code, that courtesy may be limited to three attempts or three validation events unless WebsDocs states otherwise. After that, or where there is excessive delay, suspected misuse, payment uncertainty, entitlement mismatch, fraud concern, or account inconsistency, WebsDocs may require manual support review, reissue handling, additional verification, or a new activation arrangement.

The words “AI Credits” refer to usage-control units, allowance, or balance used for AI Business Agent activity where applicable. The words “managed voice minutes” refer to client-facing voice usage allowance or managed-minute units used for AI Voice Agent services where applicable. Actual usage handling may depend on the active plan, dashboard records, billing status, provider behavior, and support review.

The words “project,” “engagement,” and “work” refer to a service relationship or scoped service activity carried out or proposed to be carried out by WebsDocs. The word “materials” refers to content, files, data, documents, assets, access details, brand assets, submitted content, business information, support evidence, profile inputs, or other items provided by the client or otherwise used in connection with the work.

The words “provider,” “platform,” and “third-party service” refer to any external tool, API, host, registrar, software provider, payment gateway, AI provider, voice provider, browser feature, infrastructure service, model gateway, email provider, analytics service, or other system not owned or directly controlled by WebsDocs.

Where these terms use words such as “including,” “for example,” or “such as,” those words introduce examples and should not be read as limiting the wider meaning of the section unless the wording clearly requires a narrower interpretation.

Force Majeure and External Disruption

WebsDocs is not responsible for failure, delay, interruption, or reduced availability caused by events beyond its reasonable control.

WebsDocs will not be responsible for delay, interruption, reduced performance, temporary unavailability, failed activation, delayed dashboard access, delayed support response, reduced AI availability, reduced voice availability, or inability to perform where the cause arises from events beyond its reasonable control.

This may include major infrastructure failure, internet outage, hosting outage, DNS failure, registrar issue, cloud or provider disruption, platform suspension, API outage, AI provider outage, voice provider outage, payment network failure, email delivery failure, browser or platform change, cyberattack, labour disruption, government action, regulatory restriction, war, civil unrest, sanctions impact, natural disaster, severe weather, fire, pandemic-related disruption, or any comparable event that materially affects normal operation.

Where such an event occurs, WebsDocs may extend timelines, pause service, revise working order, delay launch, delay activation, restrict support handling, or otherwise adjust performance to reflect the actual operational conditions.

A force majeure event does not automatically cancel all obligations forever, but it may suspend, delay, or modify performance for the period reasonably affected by the event and its practical consequences.

If the impact becomes prolonged or materially changes the viability of a project, activation, support case, or managed service, WebsDocs may discuss a revised path, pause arrangement, staged continuation, alternative provider route, or closure of the matter on a reasonable basis.

Waiver

Delay in enforcing a term does not mean the term has been permanently given up.

If WebsDocs does not immediately enforce a right, condition, remedy, restriction, payment requirement, activation rule, support boundary, usage limit, or protective measure under these Terms and Conditions, that does not mean the right has been waived permanently.

A waiver is only effective where WebsDocs clearly and expressly communicates that it intends to waive a specific right or requirement. A waiver in one situation does not operate as a waiver in another situation, and a partial waiver does not prevent later enforcement of the same or a related term where circumstances require it.

Governing Law and Dispute Handling

Disputes should first be approached in good faith through practical clarification and support review where appropriate.

These Terms and Conditions should be interpreted according to the governing law specified by WebsDocs in its formal business framework or, where no more specific governing-law statement is provided in a project-specific agreement, according to the law reasonably connected to the operating business context of WebsDocs, subject to any non-excludable consumer, data-protection, or mandatory legal protections that may apply.

Before starting formal legal action, the parties should first make a genuine effort to resolve any dispute through direct communication, support-ticket review where relevant, practical clarification, and good-faith discussion of the actual facts.

Many disagreements arise from scope ambiguity, payment status, activation-code use, dashboard access, usage records, timing expectations, review assumptions, provider dependency, or misunderstanding of the service structure. Those issues should be given a reasonable chance to be clarified before escalation.

Nothing in this section prevents WebsDocs from taking urgent protective action where necessary in relation to unpaid invoices, fraud, chargebacks, misuse of materials, infringement, unlawful conduct, security protection, provider abuse, account misuse, or misuse of the website, dashboards, AI services, voice services, or support systems.

Last Updated

Terms may be updated as WebsDocs services, AI systems, voice systems, support workflows, and business structure develop.

These Terms and Conditions may be revised from time to time to reflect changes in site structure, AI Business Agent services, AI Voice Agent services, Industry AI Support Systems, pricing logic, activation handling, dashboard systems, AI Credits, voice-minute handling, support-ticket workflows, payment processes, legal requirements, provider dependence, EU-region primary hosting, or wider business operation.

The most current published version should be treated as the active general terms unless a project-specific written agreement fixes a different arrangement for an already accepted project or service.

Last updated: May 25, 2026

Page Guide

Section guide for the WebsDocs Terms and Conditions page.

This page is written as a grouped reference document. The links below are provided to make it easier to move directly to the section most relevant to your question.

Project Documents and Service Records

Some projects or services may also be governed by a quote, invoice, activation record, dashboard record, support arrangement, or Scope of Work.

While these Terms and Conditions provide the general baseline across WebsDocs, some projects or services may later involve one or more project-specific or service-specific documents. Depending on the service, these may include a quote, estimate confirmation, invoice terms, payment reference, activation record, dashboard notice, support arrangement, managed-service note, premium package terms, or a formal Scope of Work document.

A project-specific document may define the exact service path being used, approved scope, pricing structure, payment schedule, activation requirements, support level, review stages, milestone structure, delivery model, provider arrangement, included and excluded items, usage allowance, and any special conditions that apply only to that project.

For AI Business Agent, AI Voice Agent, and Industry AI Support System services, service records may also include activation status, generated profile output, dashboard records, install snippet details, AI Credits, managed voice minutes, support-ticket history, entitlement records, billing records, and usage records where applicable.

Where such a document or service record exists and directly addresses a specific project or service point, it should be read together with these Terms and Conditions rather than in isolation.

Until such a project document or service-specific record is issued, accepted, activated, or verified, these Terms and Conditions remain the main general framework for understanding how WebsDocs approaches website use, service engagement, activation, payment structure, revisions, delivery, provider dependency, support, and related matters.

Formal Notice

These terms provide the general WebsDocs framework, while specific services may also depend on payment records, activation records, support records, or project documents.

WebsDocs operates across multiple page types, service paths, AI products, voice services, support workflows, dashboards, activation systems, free tools, paid plans, usage-based services, and custom work environments. No short summary can fully explain every possible service path, so these Terms and Conditions are written as a broader grouped document.

These terms are intended to address website use, free resources, paid activation, AI Business Agent services, AI Voice Agent services, Industry AI Support Systems, support tickets, dashboards, AI Credits, managed voice minutes, payment handling, project boundaries, timing assumptions, provider dependence, ownership logic, service eligibility, cancellation, delivery, and limitation of liability in a stable and reusable form.

A visitor using the website only for general browsing may only need a small part of this page. A client reviewing a paid activation, dashboard, managed AI plan, voice service, support case, billing issue, custom project, provider-backed workflow, or technical service may need to read it more fully.

If a particular project or service requires tighter wording, that should normally be handled through a project-specific quote, invoice, activation record, dashboard notice, support arrangement, managed-service note, or formal Scope of Work agreement rather than by rewriting the general terms for every service page.