Who Checks What AI Publishes?
AI risks for business begin when generated text or code becomes a promise to a customer. AI can speed up work, but it needs accurate information about your prices, services and rules. Delegate tasks with clear boundaries, human review and your approval. Agree who will fix problems after launch.
We are the Webdelo team. Clients have approached us after building websites with AI tools and freelancers. Some owners could not explain exactly what had been published on their own sites. If your website shows a discount nobody approved, who notices first - your team or a customer?
In McKinsey's 2025 State of AI survey, 51% of respondents from organizations using AI reported at least one negative consequence. That measures reported experiences, not the share of failed projects or an AI tool's error rate. It should not be treated as a finding about all small businesses.
Source: McKinsey, The state of AI in 2025, Exhibit 19. Respondents from organizations that regularly use AI in at least one function, n = 1,753, survey June 25 - July 29, 2025. This is not an AI error rate or a share of failed projects.
Where AI Limitations Become Business Problems
The main risks of AI in business are commercial, legal, technical and reputational. Missing business facts and missing review can turn a plausible answer into a public error. These are categories to check, not a statistical ranking of danger.
Commercial risks: an offer you never approved
AI-generated content can introduce a discount or service package that your business never agreed to provide. A customer who relies on that offer may expect you to honor it. Your staff then have to explain the mismatch.
In digital marketing, the same offer can spread across a landing page and campaign messages. Keep an approved version of the offer, including its conditions and expiry date, so every channel uses the same facts.
Legal risks: claims, consent and responsibility
In the United States, objective advertising claims need evidence. The FTC's advertising guidance distinguishes factual claims from subjective exaggeration, often called puffery. Calling a business "the best" is not automatically unlawful. The meaning, supporting context and industry rules matter.
Voice automation needs a separate legal check. In its February 2024 ruling FCC 24-17, the FCC confirmed that AI-generated voices count as artificial voices under the Telephone Consumer Protection Act. Covered advertising or telemarketing calls using an artificial voice generally require prior express written consent, subject to applicable exceptions.
Legal responsibility depends on the applicable law, the facts and the contract. It can be shared between parties. The US rules discussed here do not establish permission to advertise or call customers in Germany or elsewhere in the EU. Those markets require a separate review of local requirements before launch.
Technical risks: working demos, broken transactions
AI-written code can look convincing while mishandling a real transaction. On an ecommerce website, for example, a payment retry could create a duplicate order. This is an illustrative failure scenario, not a reported Webdelo client incident.
A developer familiar with the project should review the code and test failure paths. Quality assurance means checking what happens when a payment fails or an external service stops responding, as well as whether the normal purchase flow works.
Reputational risks: confident, incorrect statements
AI hallucinations are plausible statements that are wrong or invented. A website might describe a service your staff cannot provide. Generic wording can also hide the details that help customers understand your actual expertise.
Content prepared for seo, or search engine optimization, needs the same factual review as any sales page. The same applies to geo, which concerns visibility in AI-generated answers. Neither activity guarantees rankings or AI citations.
AI Mistakes Customers Take Seriously
The AI mistakes described in our client experience include unapproved offers and inaccurate service descriptions. Customers read those statements as information from the business. The following anonymized situations come from an interview with Webdelo co-founder Andrei Jumatii.
Promotions the owner never approved
A client's website displayed commercial offers and promotions the owner had not agreed to. Visitors then requested services at a fraction of the actual price and pointed to the website. The published offer gave them a concrete reason to expect different terms.
"The best" without an agreed basis
Another client's text called the business "the best" without agreement on what supported that wording. The practical question was straightforward: what did the claim mean, and could the owner explain it? A factual description of the service would have given readers something clearer to assess.
A treatment the doctor did not provide
In a medical project, the website described a treatment method the doctor did not use. A patient arrived requesting that approach. Specialist review needed to confirm that the text matched the doctor's actual practice.
Illustrative examples: stores, chatbots and calls
The scenarios below are examples for planning checks, not additional client cases. The suggested approval roles describe a review process. They do not determine legal liability.
| Situation | Possible consequence | What to check | Who approves |
|---|---|---|---|
| An online store shows incorrect stock availability. | A customer orders an unavailable product. | Stock updates, simultaneous orders and behavior when the inventory connection fails. | The technical reviewer confirms test results. The owner approves customer-facing stock rules. |
| A chatbot invents a refund policy. | A customer expects a refund outside the agreed terms. | Approved policy sources and escalation to a person when the answer is unclear. | The owner approves the policy. The contractor checks the bot's behavior. |
| An AI voice campaign calls previous customers. | Unwanted calls prompt complaints or potential regulatory exposure. | Consent, do-not-call requests, calling hours and applicable calling restrictions. | A legal advisor reviews requirements. The owner authorizes the campaign. The contractor verifies controls. |
For US campaigns, an existing customer relationship is not blanket permission for AI calls. The FTC's Telemarketing Sales Rule guidance describes a National Do Not Call exception for live sales-agent calls based on an established business relationship. Relevant periods include 18 months after a qualifying transaction and three months after an inquiry or application. A request not to receive calls from that specific company overrides this exception.
Those periods do not authorize artificial-voice calls. Before a campaign starts, review the following separately:
- Consent requirements for the call's purpose and technology.
- Opt-out handling and company-specific do-not-call requests.
- Permitted calling hours.
- Federal, state and industry-specific requirements.
AI Risk Management Starts with Your Own Promises
You can check many customer-facing AI risks without technical skills. Read the material as a customer would, then compare its promises with what your business actually provides. Ask a qualified specialist to review statements outside your expertise.
On a corporate website, service descriptions deserve the same attention as prices. Would your staff recognize every service listed? Could they deliver it under the conditions shown?
- Offers: verify prices, discounts, eligibility conditions and expiry dates.
- Claims: ask what supports wording such as "fastest" or "guaranteed results."
- Specialist information: have the relevant medical, legal or financial professional confirm accuracy.
- Publishing access: know who can change the site and who authorizes publication.
- Business data: ask what customer or confidential information enters AI tools and who can access it.
Request a preview of the actual page before approving it. A correct draft can still become misleading when combined with a headline, price label or button.
Make AI Accountability Specific
AI accountability becomes practical when your contractor identifies who reviews work, what you approve and who handles issues after launch. Ask for a clear explanation of the process and written responsibilities. The reviewer's relevant skills matter more than the size of the team.
- Where do you use AI? Ask separately about content, code and customer-facing automation.
- Who checks its output? Ask what they verify and how they record unresolved issues.
- How do you collect our business facts? Find out where approved information lives and how changes reach the project team.
- What do we approve? Agree on review stages and how approval is recorded before publication.
- What happens after launch? Confirm the contact route, support coverage and the process for urgent issues.
A useful answer describes concrete work: a developer tests checkout failures, an editor checks claims, and the owner approves commercial terms. "We check everything" leaves too much undefined. Put the agreed division of work in the contract or project scope.
How We Keep Human Oversight in the Process
At Webdelo, AI-assisted work starts with the client's business facts and includes human proofreading and client approval. We maintain project instructions and use AI to help check work against them. Support continues within the agreed scope, with timing based on the issue and the work required.
- Interview and knowledge base. We clarify services, prices and terms with the client and record them in the project knowledge base.
- Preparation. Texts, pages or code are prepared with AI assistance based on the project facts.
- Specialist review. A specialist checks meaning, claims and functionality and proofreads the text.
- Client approval. The client confirms the business details and approves the result.
- Launch. Only the approved result goes live.
- Support. After launch, we correct issues and adjust the work within the agreed scope.
If the specialist or the client has remarks, the work returns for correction and goes through review again before approval.
Interview and project knowledge base
We interview the client to clarify services and commercial conditions. Each project has a business knowledge base: a shared record of facts and instructions for the work. This gives reviewers a reference for checking whether a generated statement belongs in the project.
For Web Development, that context helps connect what a page promises with what the product must do. An offer needs both accurate wording and a working customer journey.
Critical review and human proofreading
Our process separates responsibilities for critical checking, review and coordination. We use AI to help compare work with project instructions. Human proofreading is mandatory to catch errors in meaning and remove template-like language.
This is a practical human in the loop approach: a person reads the result before it is accepted. Automated checking supports that judgment. It does not establish that every statement is correct.
Client approval and ongoing support
We keep clients informed about the stages of work and ask them to check and approve results. Their input is essential for confirming business details that an outside team cannot safely assume.
After launch, we stay in touch to correct issues, adjust the work and restore operation when needed. Response and restoration terms depend on the agreed scope and the task. We aim to act promptly, without promising zero errors or instant recovery.
A Short Checklist Before Anything Goes Live
Before launching AI-assisted work, confirm the business promises, technical checks and support arrangements. Record any unresolved issue and decide who must address it before publication.
- Prices, offers and promotions have your approval.
- Factual quality claims have supporting evidence.
- Specialist service descriptions match what the professional actually provides.
- A person has tested forms, payments and relevant integrations.
- Bots and calling campaigns have appropriate consent and opt-out checks for the target market.
- You have reviewed the customer-facing version and authorized publication.
- You know who handles post-launch issues and how to reach them.
Discuss Development, Support and Promotion with Webdelo
A useful project discussion establishes responsibilities, your involvement and the review steps before work begins. Development, ongoing support and promotion should share accurate business information and clear approval rules.
Discuss your project with Webdelo so we can walk through how results will be checked, what you will approve and what support you need. We will agree on the scope and responsibilities before committing to delivery or support terms.
Keep Business Decisions with Informed People
AI can help execute tasks while informed people retain control over business promises and release decisions. Our client experience shows how a short, unapproved statement can create a real customer expectation. Clear review responsibilities and a workable correction process reduce that exposure.
Start with the promises on your own website. Know who checked them, what you approved and who will help if something needs fixing.
Frequently Asked Questions
Can AI be trusted with business tasks?
AI can speed up tasks such as drafting texts or code if it works with accurate facts about your prices, services and rules. Offers, service descriptions and other customer promises still need human review and your approval before publication. Agree in advance who will fix problems after launch.
Who is responsible if an AI mistake on my website costs money?
Legal responsibility depends on the applicable law, the facts and the contract. It can be shared between the business, the contractor and other parties. Customers usually read a published offer as information from your business, so an unapproved discount can make them expect those terms. Write down in the contract who reviews content, who approves publication and who corrects errors after launch.
Does AI-generated text need human proofreading?
Yes. AI can produce plausible statements that are wrong or invented, often called hallucinations, and generic wording that hides your real expertise. A person should check prices, claims such as "the best" and specialist information, ideally together with the relevant medical, legal or financial professional. Also review the final page preview, because a correct draft can become misleading next to a headline or price label.
How should AI-written code be checked before launch?
A developer who knows the project should review the code and test both the normal flow and failure paths. Important checks include what happens when a payment fails, when an external service stops responding or when two customers order the last item at the same time. Ask the contractor to share test results and list unresolved issues before you approve the release.
Is it safe to use AI chatbots or AI voice calls with customers?
Chatbots should answer only from approved sources, such as your actual refund policy, and pass unclear questions to a person. In the US, the FCC confirmed in February 2024 that AI-generated voices count as artificial voices under the TCPA, so covered marketing calls generally need prior express written consent. An existing customer relationship does not automatically allow AI calls, and campaigns in Germany or the EU need a separate review of local rules.
What does a human team do if AI already does much of the work?
The team supplies business context, checks results and fixes consequences. In practice, that means interviewing the owner about services and terms, keeping a project knowledge base, proofreading texts, testing payment errors and supporting the system after launch. This human in the loop approach reduces exposure to errors, but it does not guarantee zero mistakes.
How do I choose a contractor for AI-assisted website or software work?
Ask where the contractor uses AI, who checks its output, how your business facts are collected and what you approve before publication. A useful answer names concrete work, such as a developer testing payment failures or an editor verifying claims. The reviewers' relevant skills matter more than team size. Confirm support coverage and the route for urgent issues, and put the agreed responsibilities in the contract or project scope.
Frequently Asked Questions
Can AI be trusted with business tasks?
AI can speed up tasks such as drafting texts or code if it works with accurate facts about your prices, services and rules. Offers, service descriptions and other customer promises still need human review and your approval before publication. Agree in advance who will fix problems after launch.
Who is responsible if an AI mistake on my website costs money?
Legal responsibility depends on the applicable law, the facts and the contract. It can be shared between the business, the contractor and other parties. Customers usually read a published offer as information from your business, so an unapproved discount can make them expect those terms. Write down in the contract who reviews content, who approves publication and who corrects errors after launch.
Does AI-generated text need human proofreading?
Yes. AI can produce plausible statements that are wrong or invented, often called hallucinations, and generic wording that hides your real expertise. A person should check prices, claims such as "the best" and specialist information, ideally together with the relevant medical, legal or financial professional. Also review the final page preview, because a correct draft can become misleading next to a headline or price label.
How should AI-written code be checked before launch?
A developer who knows the project should review the code and test both the normal flow and failure paths. Important checks include what happens when a payment fails, when an external service stops responding or when two customers order the last item at the same time. Ask the contractor to share test results and list unresolved issues before you approve the release.
Is it safe to use AI chatbots or AI voice calls with customers?
Chatbots should answer only from approved sources, such as your actual refund policy, and pass unclear questions to a person. In the US, the FCC confirmed in February 2024 that AI-generated voices count as artificial voices under the TCPA, so covered marketing calls generally need prior express written consent. An existing customer relationship does not automatically allow AI calls, and campaigns in Germany or the EU need a separate review of local rules.
What does a human team do if AI already does much of the work?
The team supplies business context, checks results and fixes consequences. In practice, that means interviewing the owner about services and terms, keeping a project knowledge base, proofreading texts, testing payment errors and supporting the system after launch. This human in the loop approach reduces exposure to errors, but it does not guarantee zero mistakes.
How do I choose a contractor for AI-assisted website or software work?
Ask where the contractor uses AI, who checks its output, how your business facts are collected and what you approve before publication. A useful answer names concrete work, such as a developer testing payment failures or an editor verifying claims. The reviewers' relevant skills matter more than team size. Confirm support coverage and the route for urgent issues, and put the agreed responsibilities in the contract or project scope.