Short answer
An AI scheduling assistant for a service business books jobs into the right crew's calendar, accounts for job length and drive time, handles reschedules and cancellations, and warns customers when a crew is running late. It follows your scheduling rules and flags conflicts rather than guessing, so the schedule stays real instead of hopeful.
Scheduling is a puzzle with moving pieces
Booking a one-hour haircut is easy. Booking a service crew is a puzzle. Two techs, one truck each, a 90-minute window at the Johnson house on the east side, a job that always runs long, a customer who is only home after 3, and a part that has to be picked up first. And at 9:40 the first job calls to say it needs another hour.
Calendar apps hold appointments. They do not know that moving the 10 am job shifts the afternoon, that the east-side job and the west-side job should not be back to back, or that a customer has already been rescheduled twice.
What a scheduling assistant actually decides
Give Oraculo the rules you use in your head. It applies them the same way every time, and flags anything that does not fit.
| Rule | Example | Why it matters |
|---|---|---|
| Job length by type | Drain clog 1 hour, water heater swap 3 hours | Prevents double booking |
| Skills and licenses | Only Maria does gas; only the two senior techs do panels | Right person on the job |
| Drive time | Add 30 to 45 minutes across the county, or use a map estimate | Keeps windows honest |
| Service windows | Offer 8 to 11 or 12 to 3, not exact times | Gives your crew room |
| Buffers | Leave 30 minutes after jobs that often run long | Absorbs surprises |
| Priority | Emergencies and repeat customers can bump routine work | Protects revenue and relationships |
It reads availability from Google Calendar, Outlook, Calendly or your field service tool such as Jobber, Housecall Pro or ServiceTitan, using their APIs or a login on its own secure computer. Dispatch decisions across a bigger fleet are covered in AI dispatcher for field service.
Booking from a call, text or form
A customer can ask for a time any way they like: a call at 8 pm, a text with a photo, a web form. Oraculo answers, asks what it needs to size the job, offers two or three real windows and books the one the customer picks. It then sends a confirmation with the address, the technician’s name if you share it, and what the customer should prepare, like clearing access to the water heater or securing pets.
The phone side is handled by the same employee that answers your business line, described in AI that answers your business phone. Because it remembers the customer, a repeat caller gets “same address as last time?” instead of the full intake.
Reschedules, cancellations and the late crew
Reschedules are where a schedule turns fragile. Oraculo handles them with the same rules: it offers the next open window that fits the job and crew, holds the old slot only until the new one is confirmed, and logs the change. If your policy charges for same-day cancellations, it tells the customer politely and adds the note for you.
- Cancellation fills. When a customer cancels, Oraculo offers the slot to a waiting list or a nearby job that could move up.
- Running late. A tech texts “stuck at the Hill Street job, 40 minutes behind.” Oraculo tells the next customer with a new ETA, offers to reschedule if they prefer, and updates the calendar.
- Weather and parts delays. One message from you (“no exterior work tomorrow”) moves the affected jobs and notifies each customer with options.
- No-shows. It checks in and rebooks (see AI no-show follow-up).
A sample delegation
Oraculo checks Dev’s Thursday jobs against Marcus’s calendar and skills, moves what fits, drafts messages offering new dates for the rest, and sends you the list of jobs it did not move with the reasons. When you approve, the customers are notified.
What stays human
- Judgment about a job’s real size. A photo helps, but a tech decides what a job needs.
- Favoritism calls. Which customer gets bumped when two need the same slot is a business decision.
- Crew conditions. Fatigue, safety, a tech who needs a day off.
- Pricing and exceptions. Oraculo applies your rules; it does not invent them.
If you sell by estimate, pair scheduling with AI quote and estimate follow-up.
Cost
Work is billed in hours against a published task-time chart. Starter is $12 per hour with a 6-hour weekly minimum (about $312 a month). Business is $8 per hour with a 43-hour weekly minimum (about $1,500 a month) and a dedicated Slack account manager. Setup is $499 once with four 1-hour Zoom sessions where an engineer connects your calendar, phone line and job software. Phone calls are $0.19 a minute, and there is a 30-day money-back guarantee.
To test it on a messy week of your real schedule, book a 20-minute demo.
Key takeaway
A service schedule is a set of rules plus constant changes. An AI scheduling assistant applies the rules every time and handles the changes quickly, so the day stays realistic.
Frequently asked questions
Can an AI schedule jobs around travel time?
Yes, if you give it your rules or let it use a map estimate. Oraculo adds drive time between jobs, uses service windows instead of exact times, and flags conflicts it cannot resolve rather than booking blindly.
Does it work with Jobber, Housecall Pro or Google Calendar?
If a scheduling or field service tool has an API or a login, Oraculo can usually work with it. Google Calendar, Outlook and Calendly are among its connections, and an engineer confirms yours in setup.
What happens when a job runs long?
A tech sends a quick text. Oraculo tells the next customer the new ETA, offers to reschedule if they prefer, and updates the calendar so the rest of the day stays accurate.
Can customers reschedule themselves?
They can message or call and Oraculo handles it using your rules. The customer gets real available windows, and your calendar updates without anyone in your office touching it.
Will it double-book?
It books against the live calendar and job durations, so it avoids overlaps. If two tools hold conflicting information, it flags the conflict instead of choosing, and it is worth fixing the source of the mismatch.