Fixxr QA review, Nov 2, 2026

The Nov 2 QA session found 31 issues. Most are small fixes, but one stops techs from accepting jobs, and the estimate engine is guessing repairs without enough information.

On Nov 2, 2026 the team ran a QA session. On Nov 3, six review agents traced each issue back to the code. Left out on purpose: environment and bad deploy issues, chat per customer, and shared tech and driver accounts.

The short version

  • Techs (15 issues): a tech can't accept a job offer. The Accept button stays locked until every tool question is answered Yes, so a tech who can't tick one is stuck. Sign-up also needs work: photo steps that don't move on, a car photo instead of vehicle details, and an interview that sends no invite.
  • Drivers (9 issues): the website asks for a login code on every chat message, the text opt-in is asked again at login and again at estimate approval, pushes arrive after logging out, and every Desk message comes as both a text and a push.
  • Desk and estimates (7 issues): the estimate engine only sees one complaint field, so a 64% guess became a repair estimate. A part Desk removed came back on its own, and there is no switch to turn auto-send off.
  • Most of it is quick: 22 of the 31 issues are small fixes.

What we recommend next

  1. Unblock tech offers first. Make Accept always tappable, ask about tools in a simple popup, and show the real reason when an offer is refused. Until then, a tech who can't tick every tool can't take the job.
  2. Fix the estimate rules next. Send every complaint field to the estimate engine, force a diagnostic for serious warning lights or low confidence, remember parts Desk removed, and add an on/off switch for auto-send.
  3. Then fix driver notifications and sign-in. Stop the repeated login code and text opt-in, stop pushes after logout, and stop sending each Desk message twice.
  4. Finally, polish tech onboarding. One interview time with a calendar invite and meeting link, a vehicle form instead of a car photo, a certifications pick list, and photo steps that move on by themselves.

Where one repair runs into trouble

Each box shows how many issues hit that step. Sign-up and sign-in sit before the job starts. Red marks the steps that block the job.

  • Blocker: the tech cannot take the job
Show the journey as a list

    Issues by area

    UI issues are screen changes only. UI plus backend needs both the screen and the server. Not UI is server, rules, data or settings work.

    • UI
    • UI plus backend
    • Not UI
    Show as a table

    How the estimate went wrong

    Two estimate problems from the session, step by step.

    A 64% guess became a repair estimate

    A part Desk removed came back

    Plans and decisions

    All on GitHub, on the branch Parts-Routing-Booking-Estimates-Test.

    • Build planWhat the field ops build set out to do: booking, parts routing, estimates, visits and pay.
    • Product decisionsEvery product and build decision, numbered, with the founder's words.
    • Staging split planHow staging goes back to Sanjit's latest and our work moves to its own test environment.
    • Remaining workWhat is still open from the build.

    Code for this work, same branch in every repo

    Details for engineers

    Every issue with its cause, where it lives in code, and a one-line fix prompt you can hand to a coding agent.

    Type
    Size
    Area

    Repos: tech app is ~/development/Fixxr-Technician; everything else is under Fixxr-Agent-Workspace (backend, marketplace-web for Desk, website, mobile for the driver app, parts-routing-src, booking). Line numbers are from the branch Parts-Routing-Booking-Estimates-Test (the Nov 3 staging code; routing lines are from the deployed main). "Likely" means read in code but not reproduced.