FIELD NOTES FOR SALES & SERVICESEPTEMBER 2026 · ISSUE 01
The Agent Dispatch.

Practical guide

After-hours texting: acknowledge the message without inventing a promise

Set clear expectations for customers while keeping the next shift’s work visible.

Browse practical guides →
A useful after-hours response explains when a person can help and preserves the original request for them.

Write the service window first

Publish the hours your team actually covers, including its time zone. Identify who changes those hours for holidays and exceptional closures. An automated message should use that maintained schedule rather than an employee’s guess about when somebody will be back.

For example, a draft could say: “Thanks for your message. Our team is back at 9 a.m. Eastern on Monday. We will pick this up then.” Use a response commitment only if the team can support it.

Keep acknowledgment separate from action

Decide which requests automation may answer and which it should leave for staff. A receipt acknowledgment should not silently confirm a booking change, refund or exception. Give the customer a clear route when a matter needs a different service channel.

Check how a late reply enters the queue and whether another automated message will repeat unnecessarily. Repeated acknowledgments can crowd out the customer’s actual question.

Rehearse the first hour back

Send consenting test messages before closing, during the closed period and just before reopening. Ask a different agent to locate each one and identify what has already been promised.

Confirm that the opening team sees waiting cases together, including any failures to send the acknowledgment. Review the wording after a real schedule change; an accurate message in September may become misleading over a holiday weekend.

Source notes

  1. Plans and sandbox
  2. Integrations
  3. Current plan comparison
  4. HighLevel integration
  5. Detailed pricing and options
  6. Channels and capabilities
  7. Photon pricing and number types
  8. Photon platform
  9. Linq platform
  10. Developer documentation