Services
Add each service, its duration and price, plus any skills or equipment it needs.
Location-aware scheduling for ElevenLabs voice agents
For businesses that travel to customers: the agent collects the service and address, then uses service areas, staff coverage, schedules and travel time to find suitable appointments.
This describes the intended workflow. The playground below is a simulation, not a live connection or an integration test.
ElevenLabs + GeoWise
1Customer call
2Service + address
3Zone + staff
4Schedule + travel
5Suitable times
Understand the location in conversation
An address is more than coordinates. The agent gathers the city, area, street and building number, then asks for missing details. Entrance, unit and landmark instructions stay as notes for the team, not a substitute for a resolved destination.
CALLER
I’m in Al Malqa, behind the mosque. The entrance is on the side.
AGENT
Which city, street and building number? I’ll read back the address before checking times.
1. Clarify
Ask for missing details or a location link. Do not guess an address from an ambiguous landmark.
2. Confirm
Read the resolved address back to the caller. Keep access instructions separately.
3. Check
Resolve the destination to a location, then compare it with service areas and coverage.
Set up the business before taking calls
Service zones
Define the geographic areas you serve and what to do with addresses outside them.
Staff and coverage
Assign staff to services and zones, with working days, hours and exceptions.
Scheduling rules
Set buffers, lead time and the scheduling mode appropriate to each service.
Voice agent
Tell it when to ask for service and address, then when to call coverage, availability and booking tools. Test missing and out-of-area addresses before launch.
COVERAGE EXAMPLE
North: Sam on Tuesdays and Thursdays. South: Leila on Mondays and Wednesdays. Sam is not offered a South job just because his calendar is free.
How a time is checked
Check hard constraints first, then rank the remaining options. Proximity alone does not make a slot feasible.
1
Service and address
Is the service offered in this area? Is the destination clear?
2
Eligibility
Which staff can perform the service and cover this zone on the requested day?
3
Working time
Does the service duration fit staff hours and existing appointments?
4
Travel and buffer
Can the person reach the customer from the prior job and still reach the next job on time?
5
Preference
Once infeasible options are removed, nearby work can be preferred. Ranking does not override the constraints.
Travel occupies time in the schedule
A calendar gap is not enough. Check travel to the new customer and onward to the next job, plus the required buffers. These numbers are illustrative, not live route estimates.
15 / 20 min
Previous job ends 11:00 + 10-minute buffer + 15-minute drive = arrival 11:25. A 60-minute service ends 12:25; 10-minute buffer + 20-minute drive = arrival 12:55 for a 13:00 job.
40 / 35 min
For a farther customer: 11:00 + 10 + 40 = 11:50; then 60 + 10 + 35 = 13:35. The 13:00 next job cannot be reached, even though the calendar initially looked open.
Try a scheduling check
Illustrative model with fixed travel inputs. It does not call GeoWise or ElevenLabs or create a booking.
Sam’s example schedule
Previous job ends 11:00
Buffer before visit: 10 min + Drive to customer: 15 min
Earliest start: 11:25
Service duration: 60 min
Buffer after visit: 10 min + Drive to next job: 20 min
Next job starts 13:00
Result
Feasible starts in this example
11:30
Back-to-back shows the first feasible start after the previous job; open shows all calculated starts at 15-minute intervals.
Choose how to offer times
Back-to-back
Offer times near the beginning or end of a job chain to reduce gaps, after checking both travel legs.
Open
Offer every start that satisfies the constraints, not just the closest to the route.
Arrival windows
Offer a broader window rather than a precise start; the exact visit time is determined later under the operating rules.
What GeoWise adds to ElevenLabs
ElevenLabs
ElevenLabs handles the conversation and can collect booking details. Reception.ai also supports configured fixed time blocks before or after appointments for travel.
ElevenLabs travel settingsGeoWise
Location-based scheduling uses the customer’s address, service areas, staff coverage, existing jobs and travel between locations in the booking decision. That is different from applying one fixed buffer to every visit.
Connect the agent to the booking workflow
1
Configure the business in GeoWise
Services, zones, staff, coverage hours and scheduling rules.
2
Connect the agent’s tools
Connect authorized tools for resolving the address and checking coverage and availability. Use the authentication method supplied for your setup.
3
Write the conversation instructions
Collect service, address and preferred time. Confirm the address and check again if it changes; never invent coverage or availability if a tool does not return it.
4
Test before accepting bookings
Test an ambiguous address, an out-of-area request, no eligible staff, travel time and availability changing before confirmation.
Confirm connection details and feature availability with the GeoWise team before production use.