Automated Rental Double-Booking Conflict Detection
Every morning, WebRun opens Booqable and scans the next 14 days for assets booked on overlapping dates, logs each conflict to a Google Sheet with asset and booking details, and fires an immediate Slack alert to your team so conflicts are resolved before any delivery is affected.
How do I automatically detect double-booking conflicts in my rental calendar?
WebRun scans Booqable every morning for the next 14 days, identifies any asset booked on overlapping dates across two or more orders, logs each conflict to Google Sheets, and fires a Slack alert to your team. Conflicts within 3 days of delivery are flagged urgent, so no double-booked asset makes it to a delivery truck.
- Double-booking conflicts caught 14 days out, not the morning of delivery
- Urgent conflicts within 3 days flagged first for immediate action
- All conflicts tracked in a sheet so nothing falls through
Built for equipment rental businesses · party and event rental companies · AV rental operations · furniture and prop rental
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.booqable.comin a real browser with your saved login - no setup, no API keys. -
1
Booqable - scan for overlapping bookings
booqable.com
WebRun opens Booqable to scan for overlapping bookings. - Open Booqable and review the booking calendar for the next 14 days
- Identify any asset appearing in two or more confirmed orders with overlapping rental periods
- Capture the asset name, both order numbers, customer names, and the overlapping dates
Done when All booking conflicts in the next 14 days are identified with full order details.
-
2
Google Sheets - log conflicts
google.com
WebRun opens Google Sheets to log conflicts. - Open the conflicts tracking sheet and append a row for each new conflict found
- Include asset, conflicting orders, customer names, dates, and resolution status
- Mark previously logged conflicts that have since been resolved
Done when The conflicts sheet is updated with all current and newly found conflicts.
-
3
Slack - alert team immediately
slack.com
WebRun opens Slack to alert team immediately. - Post an alert for each unresolved conflict to the ops channel
- Include the asset name, both order numbers, customers affected, and the conflict dates
- Escalate conflicts within 3 days of delivery as urgent
Done when Team has an alert in Slack for every unresolved booking conflict, with urgent ones flagged.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it automatically reassign or cancel a conflicting booking?
No. WebRun only identifies and alerts on conflicts. Your team decides how to resolve each one: reassign an asset, substitute equipment, or contact a customer. Nothing is changed automatically.
How far ahead does it check for conflicts?
By default it scans the next 14 days of bookings each morning. Conflicts within 3 days of delivery are flagged as urgent in the Slack alert.
What if a conflict was already resolved yesterday?
WebRun reads live booking data from Booqable each run. Resolved conflicts are marked in the tracking sheet and not re-alerted, so your team only sees active issues.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.