Overview
The Safari AI integration allows RideOps to receive automatic dispatch and queue time data from Safari AI sensors installed at your attraction.
This means operators no longer need to:
Tap Dispatch after every cycle (if dispatch automation is enabled)
Manually update Queue Time throughout the day (if queue time automation is enabled)
Instead, RideOps widgets can display Safari AI–reported values alongside—or instead of—operator-entered values.
You can choose to use Safari AI for dispatches, queue time, both, or neither. The integration is flexible and does not change your operator workflow unless you want it to.
Enable the Safari AI integration
Open the RideOps configuration page
Go to Configuration.
Select the Integrations tab.
Enter Safari AI credentials
Locate the Safari AI panel.
Check Enable integration to Safari AI.
Enter the Client ID and Client Secret provided by Safari AI.
Click Save.
This authorizes Mobaro to receive data feeds from Safari AI.
Map Safari AI to each attraction location
Go to Configuration → Locations.
Select the location to configure.
Click Edit.
Expand the RideOps section and ensure Enable RideOps is turned on.
Enter:
Safari AI Location ID
Safari AI Ride ID
Click Test Safari AI connection
This confirms your IDs are correct and data is being received.Click Save.
Note: If the test connection fails, verify the IDs with your Safari AI representative.
Choose whether to display Safari AI data in RideOps
Safari AI data is shown through dedicated Safari AI widgets, not by replacing your existing RideOps widgets.
You can display:
Widget Type | Source | Operator Action Needed | Notes |
RideOps Dispatch Widget | Operator updates manually | Manual dispatch logging | Traditional workflow |
Safari AI Dispatch Widget | Automatically updated | No operator interaction | Shows last dispatch + utilization |
RideOps Queue Time Widget | Operator updates manually | Manual queue estimation | Traditional workflow |
Safari AI Queue Time Widget | Automatically updated | No operator interaction | Shows real-time estimated queue time |
You choose what the operator sees
You may:
Show only Safari AI widgets (fully automated)
Show only RideOps widgets (fully manual)
Show both (operator can compare or override)
This provides complete operational flexibility.
How this affects operator workflow
Without Safari AI | With Safari AI |
Operator taps Dispatch each cycle | Dispatches reported automatically |
Operator adjusts queue time slider | Queue time updates automatically |
Data depends on operator consistency | Data reflects real observed movement from Safari AI |
Note: Operators may still manually override queue time or recorded dispatches at any time.
Best practices
Start by automating queue time only, then evaluate dispatch automation later.
If showing both versions of data, label Safari AI widgets clearly to avoid confusion.
Use the Test Safari AI connection button any time IDs or data feed behavior is in question.
Frequently asked questions
Q: Do we need new hardware to use Safari AI?
Yes. Safari AI sensors must be installed and configured by Safari AI.
Q: Can operators still enter values manually?
Yes. Manual updates override Safari AI data temporarily when needed.
Q: Can we use Safari AI for only some attractions?
Yes — integrate per-location as desired.
Need help?
Contact your Mobaro Customer Success Manager or email [email protected].