Sign inSee the 2-minute demo
Menu

Product / Scheduling and capacity

A schedule that refuses to promise what your crew cannot keep.

Requests arrive pending. You approve, propose another window, or decline. Capacity, weekday rules and the service area are checked before you ever see the request.

See the 2-minute demoCompare plans

Engine builtThe scheduling engine, owner-approval states and capacity rules are built and covered by an automated test suite. The owner dashboard is in build.

How it works

  1. Request arrives

    From your website, a call or a missed call. It is saved as pending with the service, the address check and the preferred weekday window.

  2. Rules run first

    Out-of-area addresses, weekends and windows you do not offer are stopped before they reach your inbox.

  3. You decide

    Confirm, propose another window or decline. A request never turns into a confirmed visit without your tap.

  4. Crew day fills in

    Confirmed visits appear in the crew's day with the arrival window, never a fake exact time.

What you get

  • Arrival windows you define, shown to customers as windows, not exact times.
  • Per-crew daily capacity and blackouts for days off.
  • Pending requests are visibly separate from confirmed visits on every screen.

Plan availability: Every plan. Multiple crews start on Team.

See all plan details →

Questions, answered first

Does a customer get a confirmed time when they submit a request?
No. They receive a request receipt that says the visit is not confirmed yet. Your team confirms it.
Can I restrict service days and the service area?
Yes. Weekdays, arrival windows and a list of cities and ZIP codes are configuration, and every channel is checked against the same rules.
What happens when two arrival windows overlap?
Windows may overlap, as they do in the Spiker example (8 to 10, 9 to 11, 10 to 12). Capacity is counted per crew per day. Database-level overlap enforcement is on our build list.