Does your booking link know you’re about to be in a car? If you mix on-site visits with virtual calls, it doesn’t, unless you tell it. Reclaim.ai reads physical addresses in your Google Calendar events, calculates drive time via Google Maps, and auto-blocks those windows so your booking link never offers a slot you can’t keep.
Disclosure: Some links in this article are affiliate links. If you purchase through them, we may earn a small commission at no extra cost to you.
Setup takes about 15 minutes. The real key is standardizing how you type addresses so the detection fires consistently.
The math: Time to set up: ~15 min | Tasks automated: travel buffer creation | Weekly time reclaimed: ~1-2 hours of manual calendar juggling
The 3-Hour Problem: Why Mobile Solopreneurs Need AI Travel Blocks
Here’s the thing: default calendars treat every gap between events as bookable, even when you are physically in a car.
Most how-to articles on Reclaim AI travel time focus on flipping a toggle. That part takes 30 seconds. The real problem is upstream: your calendar has no idea which events happen at physical locations unless you tell it in a format Google Maps can parse.
The consensus view online is simple: turn on Reclaim’s travel time feature, and it cross-references event locations with Google Maps to calculate drive time. That’s true, but incomplete. The actual friction is the gap between “setting enabled” and “setting working reliably.”
If your Google Calendar event says “Meet at the downtown office” instead of “401 S Tryon St, Charlotte, NC 28202,” Reclaim never fires the travel block. Your booking link stays wide open during your commute.
This is where most mobile solopreneurs and small business owners lose time. You end up manually blocking drive windows because the AI keeps missing triggers.
That manual blocking typically eats 20-40 minutes per week for someone running five or more on-site visits. Multiply that across a year and you are looking at 15-30 hours of calendar babysitting that software should handle.
The fix is a three-phase setup: enable detection, standardize your address inputs, and add decompression buffers. Each phase builds on the last.
Phase 1: Enabling Reclaim AI Travel Time Auto-Detection
The upshot: one setting unlocks automatic drive-time blocks, but only the paid Starter plan includes it.
Reclaim.ai is a calendar tool (not a routing or dispatch platform) that helps small business owners and solopreneurs protect their time by auto-blocking focus hours, habits, and travel buffers. The travel time feature specifically watches for Google Calendar events that contain a physical address in the Location field, then calculates drive time from your previous event’s location.
Step 1: Confirm Your Plan Supports Travel Time
Before starting, confirm your Reclaim plan includes travel time features. The free Lite plan does not include travel time auto-detection.
You need at least the Starter plan at $10/month ($8/month if billed annually). For a full breakdown of Reclaim’s tiers and what each includes, see our Reclaim AI settings walkthrough.
Step 2: Turn On Travel Time in Your Scheduling Settings
Open Reclaim and go to your scheduling preferences. Find the travel time or commute settings section.
Turn on auto-detection for travel, then set your default transportation mode. Most field-based solopreneurs will pick driving.
Step 3: Set Your Home Base Address
Reclaim needs a starting point. Enter your home or office address as your default location.
This is the fallback origin when your prior calendar event has no address attached. Use a full street address, not a neighborhood name.
The detection works like this: Reclaim reads the Location field of each Google Calendar event. If it finds a parseable address, it queries Google Maps for drive time from your previous location (or home base).
Then it creates a blocking event on your calendar before the appointment. Your scheduling link reads that block and removes the slot from availability.
One honest limitation: Reclaim’s travel time auto-detection requires Google Calendar. If Outlook is your primary calendar, this specific workflow does not apply.
Reclaim has added limited Outlook support over time, but travel time detection is built around Google Calendar’s Location field. The tool also does not do route optimization, geo-clustering, or anything map-based beyond point-to-point drive time estimates.
Phase 2: Handling Locations Reclaim Can’t Parse
What matters most: vague locations break the detection, but two fixes cover the gaps.
Get Your Free AI Tools Starter Kit
Take the 2-minute quiz to find your AI match — plus get the tools, checklist, and 50 prompts matched to your business type.
Take the Quiz →The real bottleneck is not the toggle. It’s the messy reality of how people type locations into calendar events. “Downtown Starbucks” is not an address. “Client’s warehouse” is not an address. “The usual spot” is not an address.
When Reclaim can’t parse the Location field, it silently skips the travel block. No error, no warning, just an open slot on your booking link during your drive.
Two workarounds handle this:
For events where the location is TBD at creation time: Add a placeholder calendar block after the appointment for expected drive time. Set it as “Busy.” Update the actual appointment’s Location field with a full address as soon as you have it, Reclaim will then generate the real travel block on the next sync. Delete the manual placeholder once the auto-block appears.
For events where you know it’s on-site but the address won’t resolve: Add a note in the event description flagging it for manual follow-up, then block drive time yourself until you can confirm the address. A confirmed full street address is always more reliable than hoping a business name resolves.
How to Standardize Your Address Inputs
For events where you do know the address, formatting matters:
- Full street address works: 401 S Tryon St, Charlotte, NC 28202
- Business name alone often fails: “Pinnacle Solutions office” may not resolve
- Business name plus city sometimes works: “Pinnacle Solutions, Charlotte, NC” resolves if Google Maps has the listing
- Neighborhood or landmark names fail: “Uptown,” “near the highway,” “by the park”
The safest habit: paste the full Google Maps address into the Location field every time. It takes five extra seconds per event and eliminates 90% of travel detection failures.
For solopreneurs who mix virtual and physical meetings, this address discipline is the difference between a travel system that works and one that misses half your drives.
Phase 3: Adding Decompression Buffers So You Don’t Lose The Job
The short version: a 15-minute buffer after arrival is not laziness. It is how you show up prepared instead of flustered.
Reclaim calculates raw drive time. Google Maps says 35 minutes, Reclaim blocks 35 minutes.
But raw drive time ignores parking, walking from the lot, pulling up notes on your phone, and catching your breath before a client meeting. If your first words to a client are “sorry, traffic,” you have already lost ground.
Add a decompression buffer of 10-15 minutes on top of the calculated travel time. In Reclaim’s travel settings, look for the buffer or padding option. Set it to at least 10 minutes before and after travel events.
This also protects you from the reverse problem: a client meeting runs 10 minutes long, and now your drive time block starts late, which cascades into your next appointment. The buffer absorbs that overflow.
For anyone comparing scheduling tools, our Reclaim vs Calendly breakdown covers how each platform handles buffer logic differently.
The honest answer: clients see “Busy.” They never see “Driving to your competitor’s office.”
This is the fear that stops many small business owners from turning on travel blocks. If a client opens your scheduling link and sees something like “Driving” stamped across 2-3 PM, it looks unprofessional. Or worse, it reveals you were just at another job site.
In practice, booking links, whether Reclaim’s own Scheduling Links or a connected tool like Calendly, only read free/busy status from your calendar. They show a slot as unavailable. No label, no destination, no “Travel to 401 S Tryon St.”
On your own calendar view, you see the full travel event with origin, destination, and estimated drive time. That detail is private to you by default.
One caveat: if you share your Google Calendar directly with a team member or VA (virtual assistant, someone who helps manage your schedule remotely), they may see travel event details depending on your sharing permissions. To restrict that, change the event visibility to “Private” on the individual Google Calendar event, or adjust your default calendar sharing settings in Google Calendar. This control lives in Google Calendar, not in Reclaim.
Troubleshooting: When the Travel Predictor Fails
Here’s the pattern: three common failures, three quick fixes.
Contractors have taken this even further, using AI to book jobs automatically without lifting a finger between appointments.
| Problem | Cause | Fix |
|---|---|---|
| No travel block created | Location field empty or unparseable | Paste full street address into Location field. If the address is correct but still not triggering, add #needs_travel to the event title, which flags the event so Reclaim schedules travel time for it even when location auto-detection doesn’t fire on its own. |
| Travel block too short | Google Maps underestimates rush hour | Increase buffer padding to 15-20 min in Reclaim settings |
| Travel block conflicts with fixed meeting | Fixed events override smart blocks | Move the fixed meeting or accept the overlap. Reclaim will not delete a human-created event. |
Address parsing errors are the most common issue. If you created the calendar event on your phone and typed a shorthand address, Reclaim may not resolve it. Open the event on desktop, paste the full address from Google Maps, and the travel block should generate within a few minutes on the next sync cycle.
Overlapping fixed events are the second most common complaint. Reclaim treats human-created calendar events as immovable. If you manually blocked 1-3 PM for “admin work” and Reclaim calculates a 1:15 PM travel block, the travel block loses.
Reclaim will not overwrite your manual block. The fix: convert recurring admin blocks into Reclaim “Habits” instead of fixed calendar events. Habits are flexible and will shift around travel blocks automatically.
Stale home-base address causes wrong drive-time estimates if you moved or work from a different location on certain days. Update your default location in Reclaim when your routine changes. If you split time between two offices, this is a known limitation. Reclaim uses one default origin, not a rotating schedule of home bases.
For broader context on how AI scheduling tools handle these edge cases differently, that comparison covers the field.
Your 15-Minute Setup This Weekend
Here is one concrete action you can finish before your next on-site appointment:
- Open Reclaim.ai and confirm your plan includes travel time (Starter or above at $10/month, or $8/month annual).
- Enable travel time auto-detection and set your transportation mode to driving.
- Enter your home or primary office address as the default location.
- Set buffer padding to 15 minutes before and after travel.
- Open your next three on-site appointments in Google Calendar and paste full street addresses into each Location field.
- Wait 5-10 minutes for Reclaim to sync, then check your calendar for the new travel blocks.
Expected output: You should see gray or colored travel blocks appear before and after each on-site event. Open your booking link in an incognito browser window and confirm those drive-time slots no longer show as available.
If the blocks do not appear, check the Location field formatting first. That is the fix in 80% of cases.
Set your buffer rules in Reclaim.ai today, then run a test appointment with a physical address to see the automatic travel blocks in action.
Before You Go — Grab Your Free AI Tools Starter Kit
Join 250+ small business owners getting smarter about AI. Take the 2-minute quiz and get your personalized toolkit.
Get Your Free Kit →Frequently Asked Questions
How much does Reclaim.ai cost for a small business like mine?
Reclaim.ai’s Starter plan is $10 per month (as of June 2026), or $8 per month billed annually. Check Reclaim’s pricing page for current rates and any plan changes since this was published. The free Lite plan does not include travel time auto-detection, so you’ll need at least Starter to use the features in this guide.
Does Reclaim AI work with Google Calendar?
Yes, Reclaim.ai is a dedicated app that integrates directly with Google Calendar as its primary platform. It reads event details and location data from your calendar to automatically create travel time buffers and adjust scheduling links.
Do I need technical skills to set up Reclaim AI travel time?
No, you don’t need technical skills for the basic setup. The main task is standardizing how you format physical addresses in your Google Calendar events (e.g., using full street addresses, city, and state) so Reclaim can consistently parse them.
What happens if the AI makes a mistake with my travel block?
If Reclaim mis-calculates travel time, the worst-case scenario is that your booking link may show an unavailable slot. You can manually edit or delete any travel buffer block it creates directly in your calendar, and future blocks will adjust based on corrected address data. You will see travel blocks appear after the next sync for events that already have valid, parseable addresses in their Location fields. To get full coverage quickly, go through your next week of on-site appointments and confirm each one has a complete street address. Reclaim doesn’t learn patterns over time for this feature, it reads location data and calculates drive time on each sync cycle.
How we create this content
AIscending articles are researched using public documentation, verified user reviews, and published benchmarks, then written with AI assistance and editorially reviewed for accuracy. Some links on this site are affiliate links — we may earn a commission if you sign up, at no extra cost to you. Affiliate relationships never influence our recommendations. Read our editorial policy for details.
You Might Also Like
