Your holiday closure checklist
Before the last person leaves, check that:
- Your closure and reopening dates include a named timezone.
- Every booking link blocks unavailable dates and offers a staffed return date.
- Your website, business listings, voicemail, and replies show the same hours.
- Each inquiry channel has one intended acknowledgement and a clear next step.
- New requests reach an owner, a backup, and a dated follow-up task.
- Urgent requests have a real staffed route or an honest statement that you cannot respond.
- Someone has tested the closure and is responsible for checking it when you reopen.
After hours lead capture works when a request survives the closure with enough detail for someone to act. A reply that says “we’ll get back to you” is only part of that job. The following procedure connects the reply to availability, ownership, and the first working day back.
Write one closure record
Use a short internal record as the source for every change. Here is an illustrative closure, not a preconfigured SMBcrm setting:
| Item | Example |
|---|---|
| Normal hours | Monday–Friday, 8 AM–5 PM, America/Phoenix |
| Last staffed moment | Wednesday, November 25, 2026, at 5 PM |
| Closed dates | November 26–29, 2026 |
| Reopens | Monday, November 30, 2026, at 8 AM |
| Follow-up target | First human attempt by noon on November 30 |
| Ownership | Office coordinator; service manager as backup |
| Urgent coverage | None during this example closure |
For this example, activate the closure workflow from November 25 at 5 PM until November 30 at 8 AM, America/Phoenix. That interval includes the evening before the first closed date.
Replace these details with commitments your team can meet. A business with an on-call service should record the staffed number, coverage hours, and backup separately. Do not advertise emergency coverage because someone occasionally checks their phone.
Use America/Phoenix in this example rather than a vague “local time.” Businesses in other regions should choose their own named timezone and check daylight-saving changes.
Set booking availability, then public hours
Review each calendar customers can actually book, including staff links, website embeds, and links in existing emails. In SMBcrm, use Date-Specific Hours for the closure. These override recurring Weekly Working Hours; the documented way to mark a selected date unavailable is to remove its time slots. Keep the ordinary weekly schedule for the following week. Calendar availability reference.
For the example, block November 26–29 wherever slots would otherwise be available. Check staff availability and already-booked appointments separately. An unavailable slot does not tell an existing customer what happens to their appointment; contact affected customers through your approved process.
Confirm the timezone shown on the public booking page. Changing your personal appointment viewing timezone only changes the display; it does not alter availability or booking behavior. Appointment timezone reference.
Then update the website notice, contact page, voicemail, and business listings. For Google Business Profile, open Edit profile → Hours → Special hours, select each date, mark it closed or enter its hours, and save. Google’s guidance covers closures of up to six consecutive days with special hours; closures of seven days or longer use “Temporarily closed.” Check the public result after saving. Google’s special-hours instructions.
Review other listings individually. A change to one calendar or profile is not proof that every customer-facing surface agrees.
Coordinate replies by channel
Write the closure message once, then adapt it to the channel. Include the business name, reopening time, expected human follow-up, and urgent-request boundary. These are sample templates; replace bracketed text and approve them before use.
Website form and email
Put the closure notice above the form, then use a confirmation like this:
Thanks for contacting [Business]. Our office is closed November 26–29. We reopen Monday, November 30, at 8 AM Arizona time. We received your request and plan to make our first response by noon that day. We have no on-call service during this closure. For immediate danger, contact local emergency services.
Show “received” only after a successful submission. A notice visible before submission should explain the hours without claiming a request has arrived. On a booking page, explain whether the person is confirming an appointment or requesting a callback.
For email, choose whether the mailbox responder or a CRM workflow sends the acknowledgement. Test for overlap if both are enabled. Gmail’s vacation responder uses start and end dates, starting at midnight and ending at 11:59 PM; it does not match the example’s Wednesday 5 PM cutoff by itself. Plan that boundary explicitly. Gmail vacation responder instructions.
SMS and missed calls
Keep the text compact and check its segment count in your sending tool:
[Business]: We’re closed Nov 26–29; back Nov 30 at 8 AM Arizona time. No on-call service. Request help: [short form link]. Reply STOP to opt out.
Use this only for contacts eligible to receive that message. A phone number or missed call is not a blanket marketing opt-in. Keep promotional enrollment separate from the service request and retain the permission record used for texting. The platform’s messaging policy requires valid consent, sender identification, and opt-out instructions; honor STOP before any further automated texting. Messaging consent and opt-out reference.
Missed-call texting is one entry point in this workflow. Check repeat calls and any existing missed-call automation before adding a holiday reply. Use the missed-call automation recipes for the detailed routing and suppression steps.
Web chat and social messages
State whether a person is available before inviting a visitor to wait. During the closure, ask for a short description and a permitted reply channel. If a connected social inbox has its own away message, check it alongside your CRM reply. Avoid having both promise a different response time. SMBcrm’s communication tools help organize conversations, but each channel still needs an explicit response policy.
Capture the request and give someone responsibility
Keep holiday intake brief: name, service needed, service area or ZIP code, a short description, and the person’s preferred contact method. Request only the details needed to decide the next step. Avoid collecting payment details or sensitive records in an ordinary inquiry form.
With SMBcrm’s forms and lead capture tools, plan the record that staff should see on return. Include the source channel, received time, closure label, assigned owner, and follow-up deadline. Preserve conversation history when an existing contact submits again.
Use this sequence as a workflow design to configure and test:
- Identify a new inquiry received during the closure interval.
- Check contact preferences, opt-out status, and whether an acknowledgement has already been sent for this request.
- Save the request, assign the responsible person, and create the follow-up task.
- Send the eligible channel acknowledgement, with a manual exception task if delivery fails.
- Notify the backup when a request has no owner or misses the agreed follow-up target.
In Automation → workflow → Settings, check the timezone and communication Time Window. Account Timezone follows the location; Contact Timezone follows the contact and falls back to the account when missing. A Time Window holds communications outside selected weekdays and hours, while internal actions such as tags and field updates can still run. Workflow settings reference.
That weekly window does not establish a holiday-date exception. Configure and test the closure interval separately. Keep immediate intake acknowledgement and reopening follow-up separate where their timing differs; otherwise an “instant” confirmation could wait until Monday. Review queued messages before changing an existing workflow’s timing. SMBcrm’s automation workflows provide the place to coordinate this logic, with SMBcrm support available for account-specific setup.
Test before closing
Use a controlled test contact and destinations your team owns. Preview messages first, then send tests only to approved numbers and inboxes your team controls. Do not run a holiday workflow against the customer database to see what happens.
Test immediately before and after the closing and reopening times, plus a closed weekday and the weekend. Include an existing contact, a repeat inquiry, a contact without a timezone, an SMS opt-out, and an unassigned request. Check these outcomes:
- Closed dates offer no appointments, and the first staffed date has the intended slots.
- The visitor sees one correct acknowledgement, with no competing promise from email or social settings.
- The request contains its source, owner, backup process, and follow-up due time.
- A delivery failure enters a manual queue; an opt-out does not receive another automated text.
- The urgent-request wording matches actual coverage, including the absence of coverage.
Check the rendered pages and received test messages on a phone. Record the expected result, actual result, and person who will fix any failure before closing.
Reopen with a queue check
At reopening, the designated owner should verify public hours and booking slots, remove expired website notices, and turn off or replace holiday replies. Submit a fresh controlled inquiry to catch overlapping responders or a stale closure message.
Review every request received since the cutoff, including failed deliveries and unassigned leads. Assign missing owners first. Then work through the queue by urgency and age, checking for existing appointments or conversations before contacting anyone again.
Record the first human attempt and outcome separately from the automated acknowledgement. If the backlog puts the promised response time at risk, have the backup take requests or send an approved, accurate update through an eligible channel. Close each task with a next step, appointment, or documented resolution. Save the tested closure procedure for the next holiday, but replace its dates and staffing commitments each time.
Platform references checked November 16, 2026. Settings, templates, and test cases above are illustrative; verify the behavior in your own account before enabling them.
Keep holiday inquiries ready for your return
Use SMBcrm to connect lead intake, customer conversations, and assigned follow-up before your next closure.
Explore this in SMBcrm
Keep holiday inquiries ready for your return.
Connect closure replies, booking availability, and lead ownership in a workflow your team has tested.
Explore workflow automation