BooDoo
What to build · 2026-11-04

Repair shop app to organize customer information and repair history

Keep every customer, every device and every repair in one place, so you can pull up the whole history before you touch a screwdriver.

Manage customers · Repair shop · the United States

Keep every customer, every device and every repair in one place, so you can pull up the whole history before you touch a screwdriver.

Who it's for

You run a repair shop in a strip mall. Phones, tablets, laptops, the occasional game console. It is you, a tech at the bench in the back, and somebody up front on Saturdays. The problem bites when a woman walks in with a cracked screen and says you fixed her son's laptop last spring, and she wants to know if the warranty still covers it. You know her face. You cannot find the ticket.

The problem today

Right now it is a paper ticket book by the register and a spreadsheet I update when I remember. The customer's number is on the ticket, the ticket goes in a shoebox once the job closes, and nobody can read my tech's handwriting anyway. People call all day asking if their part came in, and I have to walk back to the bench and look. I lose repeat work too, because I never circle back to the folks I quoted a battery for who said they would think about it. And when a warranty question comes up months later, I am guessing.

What the app does, screen by screen

  1. Check-in — The person at the front counter uses this to take in a device, pull up the customer or add a new one, and write down the complaint, the passcode and what came in the bag.
  2. Customer list — Staff and the owner search by name, phone number or device here to find anyone who has ever walked through the door.
  3. Customer page — Staff and the owner see one person's whole story on this screen: every device, every past repair, what was charged, what is still under warranty and what was turned down.
  4. Repair ticket — The tech works from this screen, moving the job from looked at to waiting on a part to ready, logging parts, labor and the notes that stay inside the shop.
  5. Customer status page — The customer opens this to see where their device stands, approve the estimate, pay, and pull up their receipt and warranty without calling the shop.
  6. Follow-ups — The owner starts the day here, with the turned-down quotes to call back, the warranties about to run out and the devices sitting on the shelf unclaimed.

Who uses it and what it keeps track of

  • Customers — Name, phone, email, how they found you and shop notes. Staff and owner see everyone. A customer only ever sees their own.
  • Devices — Make and model, serial or IMEI, passcode or pattern, condition it came in, what was left with it. Staff and owner only, and the passcode never shows on the customer's page.
  • Repair tickets — Complaint, what the tech found, stage, parts used, labor, price, warranty end date, inside notes for staff and one short status line the customer sees.
  • Documents — Estimate, the customer's approval, receipt and warranty slip. Staff and owner see all of them, each customer sees their own.
  • Follow-ups — Who to call, why, when it is due and whether it got done. Owner and staff.

What it changes for the business

The front counter stops guessing. Anyone working the register can pull up a repeat customer's history while they are still at the counter, so warranty questions get a straight answer instead of a shrug. Status calls dry up because the customer can look for themselves. Turned-down quotes get called back instead of forgotten, and devices stop aging on the shelf because somebody sees them on the follow-up list. When the tech who wrote the notes is off, the job keeps moving.

The one decision that matters

The one to settle early is whether the customer sees the tech's actual notes or a short status you control. Showing everything is less work and feels honest. The trouble is that techs write plainly, and a line like the board is probably toast reads very differently to the person who owns it. Go with two layers. Inside notes stay inside, and each stage has one plain sentence the customer sees, plus the estimate and receipt. You get a customer who is informed and a tech who still writes down what he really thinks, which is the whole point of the notes.

What to build first, and what can wait

Build check-in, the customer history, the ticket stages and the customer status page with estimate, payment and receipt. That alone kills the status calls and the shoebox. Parts inventory with counts and reorder points can wait, and so can sending offers out to your whole list. Get a clean record of who came in and what you did for them first. Inventory is a second job, and it is much easier once every part is already being logged against a ticket.

How BooDoo builds it

You describe the shop and the way a ticket moves, in your own words, and BooDoo builds it. It sets up the database and the sign-in, so the counter, the bench and the customer each land on their own screens. The same request gives you a website on its own live address and an Android app you can put on Google Play under your own account, with your shop's domain connected. Card payments on the estimate and texts when a device is ready come in through ready integrations. Later you describe the change instead of asking anyone.

How you'll know it works

The shop phone stops ringing with is it ready yet. And when somebody walks back in months later, you have their last repair on screen before they finish describing it.

Build it

Paste this in and it gets built.

I run a phone and laptop repair shop and I want an app for my front counter and my bench, with a website behind it. When someone walks in I want to search by name or phone number and see every device I have ever fixed for them, and if they are new, add them and start a ticket with the device, serial number, passcode, what is wrong and what they left with it. My tech needs to move that ticket from received to diagnosed to waiting on a part to ready to picked up, log the parts and labor, and keep notes only the shop can see. The customer should get a link where they can check the stage, approve the estimate, pay by card and pull up their receipt and warranty. Give me a follow-up list for quotes people turned down, warranties running out and devices sitting unclaimed, and text the customer when the device is ready.

Paste that request and it gets built, with a real database, sign-in and a phone app. You can change anything afterwards.

Ready-made apps like this

Try one live, then copy it into your workspace and make it yours.

Field service app →