New AutoCatch user · onboarding
How an operator tunes filters safely with Simulate mode
An example workflow: using Simulate and Dry-run to get the rules right before booking anything real.
Illustrative example scenario — not a specific customer, and without invented metrics.
In short
An illustrative example of how a cautious operator uses Simulate and Dry-run modes to confirm exactly what AutoCatch would accept before switching on real bookings.
The concern
A new user is (rightly) cautious about letting a bot book real rides. They want to see exactly what it would take first.
The approach
- Set up filters and turn the bot on in Simulate mode — it evaluates and logs what it would accept, but books nothing.
- Review the activity feed: every catch, miss, and skip, with the exact reason each ride was passed over.
- Adjust the filters where the decisions don't match expectations.
- Switch to Dry-run to also confirm which vehicle it would assign.
- Only then switch to Live.
Why this matters
The three modes turn automation from a leap of faith into a tuned, predictable system. Read more in the Filters docs.