Shop isolation
Customers, tickets, payments, inventory, and documents belong to one tenant.
Operating CRM for phone repair shops
Every repair leaves a trail. Keep it.
ServiceKit connects intake, diagnosis, approval, parts, payment, and pickup in one repair record. The team sees what happened. The customer sees what they need to decide.
A separate workspace for every shop. Repair-scoped links for customers.
A phone should not lose its story between the counter and the workbench.
This is not another inbox or a prettier spreadsheet. It is the operational record of the repair: who received the device, what condition it was in, what was found, what the customer approved, which part was ordered, what was paid, and who collected it.
01
RECEIVE
Record the real condition before work begins.
The front desk opens the ticket once and captures the context that normally disappears into photos, notes, and conversations.
- Customer, device, and IMEI/TAC
- Visible condition, photos, and access notes
- Consent, initial estimate, deposit, and promised date
SK-4912iPhone 13 Pro09:14
- IMEI / TAC
- 35732910•••••••
- Condition
- Cracked display
- Accessories
- None
- Due
- 24.07 · 18:00
010203
3 photos attached · consent recorded
02
SHOW
Turn the diagnosis into a clear decision.
The customer receives a link for their repair. They see the findings, images, costs, and warranty before approving or refusing.
- No separate customer account
- Options and total cost on one screen
- The decision returns directly to the ticket
Customer link · ticket #SK-4912
A complete decision on the customer’s screen.
The public link is limited to their repair. It does not expose the shop dashboard or ask the customer to learn another app.
- Findings and photo evidence
- Estimate and optional additions
- Recorded approval or refusal
- Deposit and documents in the same route
Customer link · ticket #SK-4912iPhone 13 Pro
Review Technician finding
Cracked display, unstable touch response
OLED display replacement and post-install calibration.
Estimate total800 RON
03
TRACK
Let the record grow with the repair.
Every important change enters the timeline. Front desk and technician work from the same version of the truth.
- Statuses and technician notes
- Parts, costs, and stock movements
- Messages, payments, and signatures
One record. Five working moments.
Choose a stage to see what remains recorded.
Ticket #SK-4912iPhone 13 Pro03 / 05
Current event
Approval
The customer received the estimate and images for approval.
- Customer
- Mihai Popescu
- Estimate
- 650 RON
- Deposit
- 150 RON
- Status
- Approval
04
CLOSE
Hand the phone back with a verifiable ending.
Pickup is more than another status. The PIN or QR code, payment, and documents close the route in the same record where it started.
- Confirmation of the person collecting
- Invoice and warranty document
- History retained for later returns
742 918
PICKUP CODE
Device ready for handoff.
- Payment confirmed
- Warranty issued
- Identity verified
Product boundaries, not decorative promises
Access stops where it should.
Public and internal flows have different responsibilities. ServiceKit keeps that separation in the product model.
Repair-scoped link
The customer sees only the ticket attached to their token, not the internal app.
Cookie auth and CSRF
Internal sessions use HttpOnly cookies, while mutations require the matching CSRF protection.
Audit trail
Statuses, payments, signatures, messages, and pickup remain recorded.
Before you open the first ticket.
Three answers about the route you can test.
What does the trial cover?01
You can run intake, diagnosis, customer approval, deposit, parts, pickup, and warranty in the same workspace.
Does the customer need an account?02
No. They receive a repair-scoped link and can decide directly in the browser.
Can one shop see another shop’s data?03
The flow is designed around tenant isolation: every operational resource belongs to the shop that created it.
Start with the phone that walks in tomorrow.
Open the workspace, configure the counter route, and follow the first repair without scattering its context.
Open first ticket