Salesforce Outage Contingency Plan for Service Business Lead Follow-Up

Salesforce Outage Contingency Plan: How Service Businesses Can Keep New Leads From Going Unanswered

A CRM outage does not necessarily mean your lead sources are down—but it can make it harder to see, assign, and follow up on the inquiries still arriving.

Salesforce experienced a global service disruption during Dreamforce, according to reports from The Register and Mirage News. Those reports do not establish that any individual service business lost leads or revenue. They are, however, a useful reminder to prepare for the possibility that CRM-based notifications, routing, tasks, or lead records may be temporarily unavailable.

If Salesforce is central to your workflow, your immediate goal is simple:

Keep a clear, human-owned record of every new inquiry until normal systems are restored.

This guide provides a practical contingency process for quote requests, web forms, missed calls, callback requests, and other new service leads.

#Table of contents

• First, confirm what is actually unavailable
• The Salesforce outage lead-follow-up playbook
• Temporary lead queue template
• Acknowledgment messages to use during a CRM outage
• How to reconcile leads after Salesforce is restored
• Build a permanent CRM-outage continuity plan
• Where SMS follow-up fits
• Key takeaways
• FAQ

#First, confirm what is actually unavailable

Do not assume every connected tool stopped working because Salesforce is unavailable. A lead may still arrive through your website form, phone system, inbox, ad platform, scheduling tool, or messaging platform—even if the CRM record or assignment notification does not appear.

Before switching to manual mode, check these four things:

1. Confirm the Salesforce issue. Check your organization’s normal incident communications and the Salesforce status information available to your team. Identify whether the issue affects login, records, automations, reports, integrations, or only certain users.
2. Test the lead path. Submit a test website form if appropriate, call your main number from a team phone, or inspect the inbox that normally receives inquiry notifications. Do not rely solely on the CRM to tell you whether leads are arriving.
3. Identify what still works. Your public-facing website, phone number, email inbox, ad lead forms, and calendar may continue operating. The key question is whether you can access the original lead information without Salesforce.
4. Name an outage owner. One person should own the temporary process. For a small business, this may be the owner, office manager, dispatcher, or senior salesperson. Without a named owner, teams can assume someone else is handling the queue.

A short team message can prevent confusion:

“Salesforce is currently unavailable. Until further notice, send all new lead details to [name/channel], log them in the outage lead queue, and mark who owns the next response.”

#The Salesforce outage lead-follow-up playbook

1. List every source that can still produce an inquiry

Start with the places prospects can contact you directly. For many service businesses, that includes:

• Website quote or contact forms
• Google Ads or Facebook lead forms
• Email inquiries
• Main business phone calls and voicemail
• Missed-call notifications
• Online booking requests
• Live chat
• Referral emails or texts
• Third-party lead marketplaces
• Social media direct messages

For each source, answer three operational questions:

Do this before an outage if possible. During an active disruption, focus first on the sources that create the highest-intent work: urgent calls, quote requests, scheduled consultations, and paid-lead forms.

2. Create one temporary lead queue

A temporary queue can be a shared spreadsheet, a shared document, a controlled inbox label, or another simple system your team can access. It does not need to replace Salesforce. It only needs to preserve the facts and next action until records can be reconciled.

Avoid scattered notes in personal phones, multiple text threads, or verbal handoffs. Those make it difficult to confirm who responded and what still needs attention.

Use one row or entry per inquiry, even if the person contacts you through more than one channel.

3. Capture the minimum useful information

Your outage record should include enough information for another person to continue the conversation without starting over.

At minimum, capture:

• Date and time received
• Lead name
• Phone number and email, if available
• Source of the inquiry
• Service requested
• Location or service area
• Any timing or urgency details the customer shared
• Assigned owner
• First-response time
• Current status
• Next action and due time
• Conversation notes

For example, “Needs plumbing help” is not enough for a clean handoff. A better note might be:

“Website form, 2:18 p.m. Customer requests an estimate for a leaking water heater. Provided phone number. Jamie acknowledged at 2:23 p.m.; callback assigned to Alex by 2:45 p.m.”

4. Assign one person to each lead

During an outage, do not use “the team” as the owner. Each lead needs a named person responsible for the next action.

Use simple statuses such as:

• New — not yet acknowledged
• Acknowledged — customer received a reply
• Assigned — a named team member owns it
• Contacted — call, text, or email attempted
• Awaiting customer
• Scheduled
• Closed or not a fit
• Needs CRM entry after restoration

If you have several staff members, the outage owner should periodically scan for records that have no assignee, no response timestamp, or no next action.

5. Acknowledge the inquiry without overpromising

When you can verify the lead’s contact information and you have appropriate permission to message them, send a concise acknowledgment. The purpose is not to solve the entire request automatically. It is to let the person know their inquiry was received and establish what happens next.

Do not promise a technician, estimate, appointment, or callback time your team cannot realistically meet.

A good acknowledgment usually does three things:

1. Identifies your business.
2. Confirms receipt of the inquiry.
3. States the next reasonable step.

For more first-response examples, see best lead-response templates for service businesses and auto-reply messages for leads.

6. Run scheduled check-ins while the CRM is unavailable

A manual queue only works if someone reviews it. Choose a review rhythm that fits your volume:

• Every 15–30 minutes for a high-volume or urgent service line
• At least a few times across the business day for lower-volume inquiries
• At opening and closing if after-hours requests may arrive
• Immediately after a staff shift change or handoff

At each review, look for:

• New leads without an acknowledgment
• Acknowledged leads without an owner
• Promised callbacks that are due
• Replies from leads waiting for an answer
• Duplicate submissions
• Leads that need to be entered into Salesforce later

This is also a useful time to identify whether the disruption is affecting a particular source. If web forms arrive by email but no longer create Salesforce records, the form is still working—but your normal handoff is not.

7. Keep customer-facing operations separate from the internal outage

Customers generally do not need a detailed explanation of your CRM issue. They need confirmation that a real person received their request.

If an operational issue does affect your ability to provide service promptly, be honest about the response window without blaming a platform or making a commitment you cannot keep.

For example:

“Thanks for contacting Northside Heating. We received your request and a team member will review it shortly. If you have an immediate safety concern, contact the appropriate emergency service.”

Use safety language only when it matches your actual business and the customer’s stated situation. A CRM outage is not a reason to give technical emergency instructions outside your expertise.

#Temporary lead queue template

Copy this into a shared spreadsheet or document.

Keep the queue as simple as your team needs, but do not omit the owner, status, and next action. Those three fields turn a list of names into a working follow-up process.

#Acknowledgment messages to use during a CRM outage

These examples are for leads who have provided appropriate consent or otherwise can be contacted through the channel used. Adapt them to your normal communication policies.

General service inquiry

Hi [First Name], this is [Name] from [Business]. Thanks for reaching out about [service]. We received your request and will review the details shortly. What is the best time to reach you today?

Quote or estimate request

Hi [First Name], thanks for requesting an estimate from [Business]. We have your request for [service]. A team member will follow up with the next steps. Is [phone number] the best number to reach you?

Missed call

Hi [First Name], this is [Business]. Sorry we missed your call. How can we help with [service need]?

For a more complete missed-call workflow, read after-hours lead response: how to win jobs while you sleep.

After-hours inquiry

Hi [First Name], thanks for contacting [Business]. We received your message outside normal business hours and will follow up when our team is available. Please reply with a brief description of the service you need and your preferred callback time.

When you need more information before assigning

Thanks for contacting [Business], [First Name]. We received your request. To connect you with the right person, can you share your service address and a short description of the work you need?

Keep your message factual. Do not say “a technician is on the way,” “we can fit you in today,” or “your appointment is confirmed” unless those statements are actually true.

#How to reconcile leads after Salesforce is restored

Restoration is not the end of the process. The most common cleanup risk is assuming the CRM contains every lead and every conversation that occurred during the outage.

1. Freeze the temporary queue for review

Set a clear cutoff time, such as:

“Salesforce access is restored as of 4:10 p.m. All inquiries received before that time remain in the outage queue until reconciled.”

Continue using the temporary queue until you confirm that normal lead capture, routing, and notifications are functioning again.

2. Compare every outage record with Salesforce

For each temporary record, determine whether it:

• Exists in Salesforce already
• Was created but lacks an owner, task, or current status
• Needs to be created manually
• Is a duplicate of another record
• Contains conversation notes that need to be added
• Needs a follow-up task scheduled

Use a “CRM reconciled” column in the temporary queue and do not mark the incident complete until every entry is accounted for.

3. Preserve the conversation history

If a customer replied by text, email, phone, or another channel while Salesforce was unavailable, capture the meaningful details in the restored record:

• Questions asked
• Service requested
• Appointment or callback commitments
• Preferred contact method
• Estimate details
• Any promised next step
• The person now responsible

The goal is continuity. A customer should not have to repeat their situation simply because an internal system was temporarily unavailable.

4. Test normal routing before standing down

Submit a test lead or complete another controlled check appropriate for your process. Confirm that:

• The lead appears where expected
• The right person receives the notification
• Any required task or assignment is created
• The lead can be followed up without relying on the outage queue

Do not discard your temporary process until this test succeeds.

5. Review what broke in the workflow

The incident review should focus on workflow dependencies, not blame.

Ask:

• Which lead sources continued to work?
• Which ones required Salesforce to be usable?
• Did we know where original lead data was stored?
• Who owned the temporary queue?
• Were customer acknowledgments sent consistently?
• Did any lead sit without an assigned person?
• Which information was hardest to reconstruct later?
• What should be documented or automated differently next time?

#Build a permanent CRM-outage continuity plan

The best time to decide who checks the web-form inbox is not during an outage.

Create a short continuity plan that your team can access without Salesforce. One page is enough for many small service businesses.

Include these six items

1. Lead-source map

Document every inbound source and where the original lead data can be found:

• Website form notification inbox
• Phone-system dashboard
• Ad-platform lead center
• Booking calendar
• Shared email inbox
• Social channels
• Third-party marketplaces

2. Temporary queue location

Choose a shared, access-controlled location that authorized team members can reach without logging into Salesforce.

3. Named outage roles

At minimum, assign:

• An incident owner
• A person monitoring new lead sources
• A person reconciling records after restoration
• A backup for each role

4. Customer acknowledgment templates

Pre-approve plain-language messages for new inquiries, missed calls, estimates, after-hours messages, and scheduling requests.

5. Routing rules

Write down who receives which lead type. For example:

• Urgent inbound calls → on-call team member
• Estimate requests → estimator
• Existing-customer service questions → office manager
• Out-of-area requests → documented decline or referral process

6. Restoration checklist

Include the comparison and testing steps from the previous section so the team does not overlook records created outside the CRM.

A CRM continuity plan is not a substitute for restoring the CRM or for human follow-through. It is a way to reduce the chance that new inquiries become invisible while a primary workflow is unavailable.

#Where SMS follow-up fits

If your business already has an SMS follow-up layer configured independently from the Salesforce functions affected by an outage, it may help you acknowledge captured leads and maintain follow-up. But you should confirm your actual setup before relying on it.

SecureMyLead automatically texts captured leads and can run SMS follow-up sequences. It is designed to sit as a follow-up layer alongside existing lead sources and CRM workflows—not to replace Salesforce.

During an outage, do not assume any tool automatically bypasses Salesforce, continues operating, or receives every lead. Review:

• Where the lead is captured first
• Whether the capture source still works
• Whether the connection to your messaging workflow depends on Salesforce
• Who monitors replies and owns the next human response
• Whether scheduled messages remain appropriate after a customer replies

For teams building a more resilient general process, how to build a lead follow-up system that runs automatically explains the underlying workflow components.

If you want a separate follow-up layer for captured leads, get started free with SecureMyLead. Review your lead-source connections and messaging workflow before treating any system as an outage contingency plan.

#Key takeaways

• Reports of Salesforce’s global disruption during Dreamforce are a useful prompt to review CRM availability risk, not proof that individual businesses missed leads.
• Your lead sources may still work when Salesforce does not, so test the full inquiry path rather than assuming everything is offline.
• Use one temporary queue with a timestamp, lead details, named owner, status, and next action.
• A prompt acknowledgment can reassure a prospect that their inquiry was received, but do not make promises your team cannot meet.
• After restoration, reconcile every outage lead, preserve conversation details, and test normal routing before ending manual operations.
• Document the process now so staff know exactly where to look and who owns new inquiries during a future disruption.

#FAQ

What should I do first when Salesforce is down?

Confirm the scope of the issue, then check whether your original lead sources still work. Review website-form inboxes, phone systems, ad-platform lead centers, booking tools, and shared email before switching to a temporary lead queue.

Can leads still come in when Salesforce is unavailable?

They may. It depends on how your forms, phone systems, ad platforms, integrations, and routing are configured. A lead source can remain operational even when the CRM record, notification, or automation connected to it is unavailable.

Should we tell prospects that Salesforce is down?

Usually, focus on the customer’s request rather than your internal platform. Confirm that you received the inquiry and explain the next step. Only discuss an operational delay when it materially affects what you can deliver.

Can SecureMyLead replace Salesforce during an outage?

No. SecureMyLead is a lead-follow-up layer, not a full CRM replacement. It can automatically text captured leads and run SMS follow-up sequences, but businesses should verify how their own lead capture and integrations behave during an outage.

How do we avoid duplicate leads after Salesforce comes back?

Keep one temporary queue, record timestamps and source details, then compare each entry against Salesforce after restoration. Mark every lead as reconciled only after confirming its CRM record, ownership, notes, and next action are complete.

#Related reading

• How to build a lead follow-up system that runs automatically
• Best lead response templates for service businesses
• After-hours lead response: how to win jobs while you sleep
• 7 lead follow-up mistakes that quietly kill conversion

#Sources

• The Register: Salesforce suffers global outage amid Dreamforce
• Mirage News: Salesforce hit with service disruption during Dreamforce