Trail Hits:Bicycle Maintenance

Add an internal, staff-only note to a shop work order's message thread. Not shown to the customer and not synced to the POS. Use for tech-to-tech context on a ticket.

add_work_order_note

Component-level health for one of the rider's bikes, using Trail Hits' parity-checked scoring (safety-weighted 0-100 bike score; per-component usage percent, status, urgency, and Replace-vs-Service action). Facts here come from the rider's real tracked wear; do not estimate.

get_bike_health

Search the shop's customer directory by name (and phone). Returns bikes count and engagement per customer. Contact details (email, POS id) are omitted unless you set include_contact, so ask for them only when the task genuinely needs to reach the customer.

search_customers

Permanently remove one of the rider's OWN rides that is a duplicate. It deletes the ride and cannot be undone. The first call changes nothing: Trail Hits asks the rider to confirm, or returns a preview and a confirmation_token to pass back once the rider has said yes. Trail Hits then recomputes the bike's mileage and component wear from the remaining rides. It does NOT retroactively change service-reminder counters (chain wax, drivetrain, or shock service intervals).

dismiss_duplicate_ride

Everything an assistant needs to coach the rider through a specific service: the exact bike (make/model/year), the component and its measured wear, what the shop's most recent inspection noted for that bike, plus Trail Hits' own maintenance tip. The facts about the rider's bike come from this tool; YOU should combine them with your own mechanical knowledge and current web resources (torque specs, part-specific procedures, videos) to walk the rider through the job.

get_service_context

Booked-vs-finished labor minutes per active work order at the shop: how much estimated labor is on each ticket and how much is marked done.

labor_progress

Trail Hits' learning library: maintenance and setup modules with their lessons. Call without arguments for the catalog (module titles, levels, lesson titles); pass a module_slug to get the full lesson content for one module.

list_learning_content

Record that the rider serviced (or replaced) ONE component on their own bike, resetting its maintenance counter as of the service date. Use the component_id from get_bike_health, get_service_due, or get_service_context. Only call this when the rider actually performed the service: it writes a service record and moves the component's last-serviced date, and cannot be undone from here. Use service_type 'service' (the default) for cleaning, waxing, bleeding, or any maintenance that keeps the same part; use 'replace' ONLY when the part was physically replaced (it also resets the wear/install baseline). It affects only THIS component, not related parts.

mark_component_serviced

List the authenticated rider's bikes (their quiver) with identity and true lifetime mileage. Mileage is already in the rider's preferred unit (see the units field); present it in that unit. total_mileage already includes odometer, ride, and manual miles; never add ride sums on top of it.

list_my_bikes

The rider's shop estimates and inspection reports for their own bikes: estimate id, status, decision, and totals, plus the shop's inspection findings. Resolved through the rider's authenticated account, never through share links; only estimates the shop has actually sent are shown. An estimate with no customer_decision and no superseded_at is waiting for the rider; its id is what respond_to_estimate takes. superseded_at means a newer version replaced it.

get_my_estimates_and_reports