Salesforce Outage Website Response Checklist for Local Businesses
Use this practical website and lead-response checklist when Salesforce or another CRM outage may affect local business inquiries.
Keep your website reachable when CRM access is limited
Reports described a global Salesforce outage during the Dreamforce conference, followed by customers reporting that service was returning to normal. Quartz and The Register covered the event and restoration reports.
That does not mean every local business lost access, every Salesforce feature failed, or every website form stopped working. But if your business relies on Salesforce—or a website form, inbox, scheduler, phone system, or automation connected to any CRM—it is worth checking the path a new inquiry takes.
The immediate goal is simple: make sure a prospective customer can still reach a real person, and make sure your team has a temporary record of that contact if the usual system is unavailable.
Contents
- First: verify the actual impact
- Website response checklist
- What to publish on your site, if customers are affected
- Use a temporary inquiry log
- Reconcile leads after service returns
- Build a CRM-outage fallback before the next incident
- Key takeaways
First: verify the actual impact
Do not assume that a CRM outage has broken your public website. A contact form can appear normal to a visitor while its submission fails later in the chain—or it may continue working perfectly even when your team cannot log in to the CRM.
Assign one person to check the full inquiry path:
- Submit one clearly labeled test inquiry through each important form: contact, quote request, booking request, and service-page form.
- Confirm that the site displays its usual thank-you message or confirmation page.
- Check the recipient inbox, notification channel, and CRM record, if accessible.
- Test the main business phone number and any website chat or scheduling link.
- Write down exactly what is working, what is delayed, and what cannot be confirmed yet.
Use a test message such as: “TEST — please disregard.” Avoid entering real customer details into an unfamiliar fallback process.
This distinction matters. A form may still collect submissions but fail to create a Salesforce record. Or Salesforce may be inaccessible to one staff member while form notifications still reach a shared inbox. Your response should match what you have verified, not what you fear might be happening.
For a broader review of how forms should work under normal conditions, see 7 contact page mistakes that cost local businesses leads.
Website response checklist
If CRM access is limited, work through this checklist in order.
1. Keep a working contact method prominent
Your website should always give visitors at least one direct way to reach you that does not depend entirely on a single form integration.
Check that your header, contact page, and key service pages show the right:
- Click-to-call phone number
- Monitored email address
- Business hours
- Booking link, if it has been tested and is operating normally
- Physical location or service-area details, where relevant
If calls are your most reliable fallback, make the phone number easy to tap on a mobile device. A visitor who needs urgent plumbing, towing, repair, veterinary, or home service help may not wait for a form workflow to recover.
Read why your local business website has to work on a phone first for a practical mobile-first review.
2. Do not remove forms until you know they are failing
Taking down a form unnecessarily can create a problem where none existed. First test it.
If the form submission reaches a monitored email inbox but does not appear in Salesforce, you may be able to leave the form live while your team records inquiries elsewhere temporarily. If you cannot confirm whether submissions are arriving, place a verified alternate route near the form.
For example:
Having trouble submitting this form? Call us at [phone number] or email [email address], and our team will respond as soon as possible.
Use only contact details your team is actively monitoring. Do not add a personal number or rarely checked inbox simply because it is available.
3. Check automated confirmation messages
A visitor may receive an automatic “we received your request” email even if your team cannot access the CRM record promptly. If you can edit that message and know your response time may change, update the expectation carefully.
A suitable temporary confirmation could say:
We’ve received your message. Our team is reviewing requests manually and will respond as soon as possible.
Avoid promising “a response within one hour” unless your team can realistically deliver it during the disruption.
If you cannot verify that your confirmation automation is functioning, do not claim that every submission was received. Direct visitors to a tested phone number or email address instead.
4. Give staff one fallback owner and one fallback channel
The most common operational mistake during a system interruption is not technical—it is unclear ownership.
Choose:
- One person responsible for checking the temporary inquiry log
- One monitored inbox or phone queue
- A backup person for breaks, after-hours coverage, or high inquiry volume
- A stated internal response target that your team can meet
Keep this temporary process narrow. Adding three inboxes, two spreadsheets, a text-message thread, and a new chat app can make it harder to determine whether someone has already replied.
5. Protect customer information while working manually
A CRM outage is not a reason to handle customer details carelessly. Store only the information needed to return the inquiry, limit access to the temporary record, and avoid copying payment details, medical information, passwords, or other sensitive material into a casual team chat or broadly shared document.
If your team uses shared documents during an interruption, review how to avoid exposing passwords in shared Google Docs.
What to publish on your site, if customers are affected
Most businesses do not need a public outage notice. Publish one only if you have verified that customers may be unable to submit a form, schedule, access an account, or receive a normal response.
Keep the notice short, specific, and action-oriented. A banner, contact-page message, or brief note above the affected form is usually enough.
Website notice template for a verified form or response issue
We are currently experiencing a temporary issue with our usual inquiry system. For the fastest response, please call us at [phone number] or email [email address]. We appreciate your patience.
Website notice template when forms are working but replies may be delayed
We’re currently reviewing new requests manually. Your message is important to us, and our response may take longer than usual. For urgent help, please call [phone number].
Do not name Salesforce in customer-facing copy unless doing so is useful for your customers and accurately explains an effect they can see. Most visitors only need to know how to reach you and what response timing to expect.
When the issue is resolved, remove the notice promptly. Old incident messages can make a business appear unavailable long after normal operations resume.
Use a temporary inquiry log
If new leads may not be reliably entering your CRM, create one secure, temporary place to record them. This is not meant to replace Salesforce or become a permanent second database. It is a short-term handoff tool.
A simple log can include:
| Field | What to record |
|---|---|
| Date and time | When the inquiry arrived |
| Customer name | Name provided by the visitor |
| Phone or email | Best way to reply |
| Inquiry source | Form, call, email, chat, referral, or walk-in |
| Service requested | The customer’s stated need |
| Owner | Team member responsible for follow-up |
| Status | New, contacted, booked, not a fit, or resolved |
| Notes | Only the details needed for a useful response |
Use a unique reference, such as the date, time, and initials, if multiple people are logging inquiries. That can make reconciliation easier later.
For incoming calls, ask staff to add the inquiry to the same log before moving on to the next task. For email and form requests, record the original timestamp and preserve the message in the monitored inbox. This gives your team a way to check whether each inquiry received a response if activity rises during the interruption.
Reconcile leads after service returns
Once Salesforce access returns, do not assume everything has synchronized correctly. Restoration can be a good time to reconcile, not merely resume normal work.
Compare temporary records with the CRM
Review each entry in the temporary log and determine whether it:
- Already exists in Salesforce
- Needs to be added manually
- Needs an updated owner, status, or note
- Was answered but not documented
- Was duplicated because the customer used more than one contact method
Preserve the original inquiry time where possible. A request received during the disruption should not look like a brand-new lead simply because it was entered later.
Look for unassigned or unanswered inquiries
Filter the temporary log for entries marked “new” or without an owner. Then check shared inboxes, voicemail, chat transcripts, and form notifications for conversations that may not have made it into the CRM.
A short review can help prevent the handoff gap that often occurs when everyone assumes someone else handled the request.
Restore normal website messaging
After you have tested the normal workflow again:
- Remove any temporary website notice.
- Restore standard form confirmation language if you changed it.
- Confirm that staff notifications are arriving.
- Stop using the temporary log for new inquiries.
- Keep the log only as long as needed for reconciliation and appropriate recordkeeping.
Build a CRM-outage fallback before the next incident
The useful lesson from an outage is not that every business needs a public alert. It is that a website inquiry path should not be a mystery.
Document a one-page fallback plan before you need it:
- Which forms connect to which systems?
- Which inbox receives form notifications?
- Which phone number is staffed during business hours?
- Who can edit a contact-page message or site banner?
- Who owns the temporary inquiry log?
- Who checks that the usual CRM workflow is working again?
- What is the process for entering and deduplicating inquiries afterward?
Review this plan whenever you change your website, CRM, booking tool, form provider, or email routing. A new integration can quietly change where leads go.
Your contact page should also make it easy for customers to choose a method that works for them. See how local businesses should handle website leads that arrive after hours for ideas on setting clear expectations when immediate replies are not possible.
A short StoopCraft website check
During a CRM disruption, a clear website can help customers find an alternate way to contact your business without guessing. StoopCraft builds websites for local businesses and includes on-page SEO as part of its $69/month service.
If you want a website with clear contact paths, service pages, and information your customers can use, visit StoopCraft.
Key takeaways
- The Salesforce outage reported during Dreamforce does not prove that every local business website or form was affected.
- Test the full inquiry path before changing your site or publishing an outage notice.
- If customers are affected, provide one tested alternate contact method and realistic response expectations.
- Use a secure, temporary inquiry log if CRM records may be delayed or unavailable.
- When service returns, reconcile the log, inboxes, and CRM before treating the incident as closed.
