LARA

Configure after-hours rules and on-call rotation

Decide what LARA does when the office is closed: triage, schedule, transfer to on-call, or take a message. Set it once and stop second-guessing the night shift.

Colin LawlessColin LawlessCo-founder, CTO7 min readUpdated Apr 26, 2026
On this page

Most home-service shops lose more revenue to nights and weekends than to busy signals. After-hours rules let LARA triage urgency, schedule low-priority jobs for morning, and only wake your on-call tech for the calls that warrant it.

What counts as after-hours

By default, after-hours is everything outside the business hours you set. You can also flag certain weekday hours (lunch, training) as after-hours without redefining your full schedule.

Set your business hours

  1. Open Settings → LARA → Business hours.
  2. Pick your time zone first — every rule is evaluated against this.
  3. Set open and close times per weekday. Use the copy-day shortcut for typical 8-to-5 schedules.
  4. Mark Saturdays/Sundays as open if you cover weekends. Otherwise leave them closed.

Multiple service regions

If you operate across time zones, set hours per region under Settings → LARA → Regions. LARA evaluates the caller's number against the region map and uses the matching schedule.

Pick the after-hours rule

There are four rule shapes. You can compose them — for example, triage urgent + schedule the rest.

  1. Triage urgent — LARA asks 2–3 qualifying questions. If urgency keywords hit, transfer to on-call. Otherwise, schedule.
  2. Schedule for morning — LARA offers the next-day morning window and books it. No transfer.
  3. Transfer to on-call — every after-hours call rings the on-call tech directly.
  4. Take a message — LARA captures name, number, and reason, then sends a notification.

On-call rotation

If a rule transfers, LARA uses the rotation to decide who to ring.

  1. Open Settings → LARA → On-call rotation.
  2. Add team members with their personal cell numbers.
  3. Set the rotation cadence — daily handoff at 6pm is the most common.
  4. Add a fallback (usually the owner) for the case where the on-call tech doesn't pick up after 3 rings.
json
// Rotation example — weekly Mon → Fri
{
  "cadence": "weekly",
  "handoffAt": "06:00",
  "members": [
    { "id": "u_01", "phone": "+17165550101" },
    { "id": "u_02", "phone": "+17165550102" }
  ],
  "fallback": { "id": "u_owner", "phone": "+17165550100" }
}

Holidays and exceptions

Add date-range exceptions for holidays, training days, or full-shop closures. LARA falls back to the after-hours rule for the entire range, regardless of weekday.

Watch the time zone

Holiday ranges are evaluated in the region's time zone, not the caller's. If you cover Eastern + Central, set the holiday once per region or accept that the boundary shifts by an hour.

Test it

Use Settings → LARA → Simulate to send a test call as if the clock were 10pm. Verify the rule fires, the transfer reaches the right cell, and the call shows up tagged as after-hours in /lara/calls.

Done

Your after-hours rule is live. Revisit it after the first 30 days — most shops adjust the urgency threshold once they see what LARA actually transfers.

Was this article helpful?

Keep going