What Local Businesses Should Do When ChatGPT and Other AI Tools Go Down

An AI outage should not make your business unreachable

Reports of a major outage affecting ChatGPT, Claude, and Grok are a useful reminder: widely used AI services can be unavailable at the same time. That does not automatically mean your website is down, your forms have failed, or your business has missed inquiries. But it does mean local businesses should avoid placing essential customer-contact steps entirely behind one AI dependency.

If you use AI to answer website chat, draft replies, sort inquiries, summarize messages, or prepare follow-up, have a human-readable fallback ready. Customers who need a quote, an appointment, or an answer should still be able to see how to contact you and receive an honest response while a tool is unavailable.

News coverage documented the simultaneous availability problems with these major AI tools. Yahoo Finance reported on the ChatGPT outage, while 9to5Google covered outages involving ChatGPT, Claude, and Grok.

Table of contents

• First, separate an AI outage from a website outage
• Map every customer workflow that depends on AI
• Build a practical fallback for inquiries
• Test forms and notifications without the AI tool
• Use clear, honest customer communication
• Lead-response checklist for an AI outage
• Prepare before the next interruption

First, separate an AI outage from a website outage

An unavailable AI service and an unavailable business website are different problems.

Your website may still be working normally even when the AI tool you use to support it is not. A visitor may still be able to:

• Read your services, hours, and service area
• Call the number displayed on your site
• Submit a contact or quote form
• Use a booking link that does not depend on the affected tool
• Email your business directly

The risk is in the handoff. If a website chat assistant is the only visible way to ask a question, or if form submissions wait for an AI tool before someone sees them, a customer may be left without a clear next step.

Start by checking the customer-facing basics:

1. Open your site in a private browser window or on a phone.
2. Confirm your phone number, email address, and contact page are visible.
3. Submit a test inquiry using a real test email address.
4. Confirm the submission reaches a person or a monitored inbox.
5. Check whether a customer can still contact you if the chat widget is unavailable.

If the site itself is unavailable, use a broader website downtime response plan. If only an AI service is down, focus on maintaining the path from inquiry to human response.

Map every customer workflow that depends on AI

You do not need a complicated technology audit. Make a short list of moments when AI sits between a customer and a human on your team.

For each workflow, write down three things:

• What the customer is trying to do
• Which tool normally helps with it
• What happens if that tool is unavailable

A simple table can reveal fragile handoffs quickly.

Pay close attention to these common weak points:

A chat widget is the only contact option

A website chat assistant can be convenient, but it should not be the only route to your business. Put a clickable phone number, contact form, and email address where customers can find them without opening chat.

Your contact page should make the next action obvious, especially on a phone.

Form submissions are routed through an AI workflow

A form can appear to work while the notification or routing sequence after submission has stalled. Make sure at least one person can access the original submissions directly, rather than only through an AI-generated summary or downstream task.

Staff do not know what to say without AI

If team members normally rely on an AI tool to write every reply, they may delay responding while waiting for it to return. A short, approved message library helps them respond clearly without improvising.

The business has no named owner for new inquiries

The most reliable fallback is not another tool. It is a person who knows they are responsible for checking incoming messages and assigning follow-up.

Build a practical fallback for inquiries

A useful AI-outage plan should be simple enough to use on a busy day. It does not need to recreate every automated workflow. Its job is to make sure customers can reach a person and receive a timely, accurate next step.

Keep your essential contact paths visible

At a minimum, your website should clearly display:

• A phone number that can receive calls during your stated hours
• A contact or quote form
• A monitored business email address
• Current hours and availability information
• A clear confirmation message after a form is submitted

For service businesses, the best backup path is often a basic form that asks only for the information needed to start a conversation: name, preferred contact method, location or service area, service needed, and a short description.

Avoid making a customer complete a long conversational flow just to request a callback. If AI-assisted chat is unavailable, a short form can keep the inquiry moving.

For more guidance on the confirmation step, see what to put on a local business website thank-you page.

Assign one person to own the inbox

Choose a primary owner and a backup owner for incoming website inquiries. Both should know:

• Which inbox or system receives form notifications
• How often to check during the outage
• Which inquiries need a same-day response based on your business’s normal practices
• Who can answer service, scheduling, pricing, or availability questions
• How to record the inquiry so it is not handled twice or forgotten

Use a shared sheet, inbox label, or simple list if your usual system depends on unavailable AI features. Record the customer name, contact method, request, time received, owner, and follow-up status.

The aim is not perfect automation. It is a visible queue and clear accountability.

Save short reply templates before you need them

A human response does not need to be elaborate. Save a few plain-language templates in a document your team can access without the AI service.

Initial acknowledgment

Thanks for contacting [Business Name]. We received your message and a member of our team will review it. If your request is time-sensitive, please call us at [phone number].

When a fuller reply may take longer

Thanks for reaching out. We are reviewing inquiries manually at the moment, so a detailed response may take a little longer than usual. We will follow up as soon as we can.

When you need more information

Thanks for your inquiry about [service]. To help us point you in the right direction, could you share [specific detail, such as location, preferred date, or the service you need]?

Do not promise an exact response time unless your business can reasonably meet it. Honest expectations are better than a confident automated message that no one follows through on.

Test forms and notifications without the AI tool

Do not assume a form works because it looks correct on the page. Test the full path from submission to human review.

Run this five-minute test

1. Visit the form from a phone and a desktop browser.
2. Submit a test message with a unique subject line, such as “AI outage test.”
3. Confirm the thank-you message appears.
4. Confirm the notification reaches the designated inbox or recipient.
5. Confirm the backup owner can see it too, if needed.
6. Reply to the test inquiry and make sure your reply address is correct.
7. Delete or label the test record so it does not get treated as a real customer request.

If a form’s notification is delayed, unclear, or routed somewhere only one person can access, fix that before the next outage. The same principle applies outside an outage: lead notifications need a dependable review process.

Check the customer’s view, not just the admin view

When a chat tool is unavailable, visitors may see an error, an endless loading indicator, or an empty space where the widget normally appears. Review your site from a visitor’s perspective.

Ask:

• Can the customer still find a phone number without scrolling excessively?
• Does the contact page explain what information to include?
• Is there another contact option near the unavailable chat?
• Does the form work on a mobile device?
• Are your business hours current?
• Is the post-submission confirmation clear?

If the answer to any of these is no, the site may need a more resilient contact path.

Use clear, honest customer communication

You do not need to publish a sitewide notice every time an internal tool has a brief interruption. But if an AI outage is affecting customer-facing chat or delaying replies, a short message can prevent confusion.

Only say what customers need to know:

• The chat assistant or automated reply service may be temporarily unavailable.
• Customers can call, email, or use the contact form instead.
• Your team is reviewing inquiries manually.
• You will respond as soon as you can.

Avoid blaming a vendor, speculating about restoration time, or claiming that messages were lost unless you have verified that they were.

A concise website or chat notice might read:

Our website chat is temporarily unavailable. You can still reach our team by calling [phone number], emailing [email address], or submitting the contact form below. We are reviewing new inquiries manually.

If your business is handling a genuinely urgent operational situation—such as a closure, safety issue, or change in available services—put the operational information first. Tool availability is secondary to what customers need to do.

Lead-response checklist for an AI outage

Use this checklist while the AI service is unavailable.

During the outage

• [ ] Confirm whether your website itself is live.
• [ ] Check that the phone number, email, and contact form are visible.
• [ ] Submit a test form and verify that it reaches a monitored inbox.
• [ ] Identify the person responsible for checking new inquiries.
• [ ] Assign a backup person in case the primary owner is unavailable.
• [ ] Review new submissions manually at an agreed interval.
• [ ] Use saved response templates for acknowledgments and information requests.
• [ ] Add a short notice only if customers are likely to encounter an unavailable chat or delayed automated response.
• [ ] Track each inquiry and its owner in a shared, accessible place.
• [ ] Do not promise a response time your team cannot meet.

After the outage

• [ ] Check the AI tool’s history, queue, or connected workflow for messages that may need review.
• [ ] Compare those messages with your manual inquiry list to avoid duplicate replies.
• [ ] Follow up on any inquiry that did not receive a clear response.
• [ ] Remove temporary customer-facing notices once they are no longer accurate.
• [ ] Note where the process broke down or created uncertainty.
• [ ] Update the fallback plan, templates, or website contact options before the next interruption.

Prepare before the next interruption

An AI outage plan is mostly ordinary website and communication hygiene. The businesses best prepared for an unavailable tool are not necessarily the ones with the most automation. They are the ones that can still show customers a clear way to get in touch and give staff a straightforward process for responding.

Review these items quarterly or whenever you add a new tool:

• Is your contact information current across your website?
• Does every primary service page point to a working contact option?
• Can someone access raw form submissions without relying on an AI summary?
• Are inbox owners and backups still correct?
• Can staff find approved reply templates?
• Is your site easy to contact from a phone?
• Are after-hours inquiries handled with a clear process?

A solid website should make customer contact understandable even when third-party tools are not available. StoopCraft builds done-for-you websites for local businesses and includes on-page SEO as part of its $69/month service. If you need a website with clearer service information and contact paths, visit StoopCraft.

Related reading

• 7 contact page mistakes that cost local businesses leads
• How local businesses should handle website leads that arrive after hours
• Local business website maintenance checklist: what to review each month
• The local business website checklist: everything your site needs to win customers