Riggs by HoneyRuns
Riggs
Riggs is HoneyRuns' fleet maintenance agent. He works out what each vehicle needs, gets it on a shop's calendar with the people involved, and follows up until the work is done, inside the approval rules your company sets.
- Made by
- HoneyRuns, Austin, Texas
- Last updated
- October 2, 2026
What Riggs does
- Knows what's due. He reads fault codes and mileage from your telematics, plus each vehicle's service intervals. Intervals run on mileage or on time (for example every 5,000 miles, or every 12 months).
- Texts the people involved. The driver, the shop or mobile mechanic, and whoever on your side has to say yes.
- Books the visit. He gets a time on the shop's calendar that the vehicle can actually be spared for.
- Follows up until the vehicle is in and the work is finished, then logs the completed service.
- Stops at your limits. Estimates over your approval limit come to you, and so does anything your settings say needs your OK (see Rules he works under).
Each job Riggs handles, from the moment service is due to the moment it's logged, is called a run.
How to hand him work
In HoneyRuns
The Runs page lists what's due. The Next step column says what Riggs will do on each run (for example, "Riggs will schedule a time with Collin"). Press Approve and he takes it from there. "Approve all" hands him every run on the list.
By text
Text Riggs the way you'd text a coordinator: what's wrong, which vehicle, and when it can come off the road. Drivers and shops reply to him the same way.
From Claude
Ask Claude to hand something to Riggs, or to check what he's working on. See Connect Riggs to Claude.
What he reads
Telematics
Samsara, Geotab, Verizon Connect, Motive, Azuga, Ford Pro, Bouncie, DIMO, GPS Insight (including WEX Telematics), One Step GPS, and FleetSharp. Fault codes come through where the provider sends them; mileage comes through from all of them.
Maintenance and shop systems
Fleetio, Shopmonkey, and AutoLeap.
Other connections
A Google Drive folder you share with him, and Slack or Microsoft Teams for updates.
No telematics? Riggs still works from each vehicle's VIN, its service intervals, and its service history.
Rules he works under
- Your vendors. Riggs works with the shops and mobile mechanics you already use.
- Your limits. You set the approval limit. An estimate over it waits for you.
- Your settings. Each kind of action (scheduling, changes to a run, service intervals, messages, and logging completed service) is set per company to one of three levels: draft only, ask first, or go ahead on low-risk work. Every kind starts at ask first.
Connect Riggs to Claude
Coming soon. The Riggs connector for Claude isn't in Claude's connector directory yet. This section will say so when it's listed.
The connector gives Claude two tools:
ask_riggs: hand Riggs work, or answer a question he asked you, in plain words.check_riggs: see what's open and what needs you.
How it works
- Sign in with your HoneyRuns account. Riggs acts for your default company.
- Approvals. When Riggs needs a yes or no, Claude relays your answer. It's logged as you, through your connected agent.
- Same rules. Riggs follows your company's approval settings no matter where the work came from.
Connector URL
https://mcp.honeyruns.com/mcp
Things to ask Claude
- "Samsara shows unit 14 has P0300. Have Riggs get it in this week."
- "What does Riggs need from me today?"
- "Tell Riggs yes on the brake job for Transit 214."
- "Tell Riggs the Sprinter can't come off the road until Friday."
- "Which runs is Riggs still waiting on a shop for?"
Who it works for
- Fleets whose shop runs on HoneyRuns.
- Shops on HoneyRuns.
- Self-managed fleets: coming.
Privacy and support
- Privacy policy: honeyruns.com/privacy
- Security: honeyruns.com/security
- Sub-processors: honeyruns.com/sub-processors
- Terms: honeyruns.com/terms
- Support: honeyruns.com/support