Describe your repair counter, and Makeform creates a phone repair form for customer details, device identifiers, symptoms, condition, and service preferences.
Route repair requests to email, Google Sheets, Slack, and Zapier.
Sample prompts for the builder
Choose a workflow, edit it, or send the prompt to the Makeform builder. Each outline previews the requested structure.
Audience
Customers dropping off cracked phones at the counter
Format
Quick intake with condition photos and contact preference
Prompt size
224 chars
Example form structure
Quick intake with condition photos and contact preference
Customer name and contact details
Brand, exact model, color, and device identifier
Which functions still work?
Upload front and back condition photos
Inspection acknowledgment
Suggested routing tags
New intake
Awaiting estimate
Ready for pickup
Ask for the exact model and existing-damage photos so staff can plan intake and record condition.
Step 1
Identify
customer, phone model, and device identifier
Step 2
Document
symptoms, damage, photos, and accessories
Step 3
Triage
priority, estimate contact, and technician routing
Step 4
Return
pickup preference and completed-request record
Why structured intake matters
Record which device arrived, what the customer observed, its condition, and how the shop should follow up.
Model, color, carrier, storage, and serial or IMEI fields distinguish similar-looking phones.
Issue categories reveal focused questions about power, liquid exposure, prior repairs, and fault timing.
Timing, accessories, condition photos, and acknowledgment stay together instead of across notes.
One builder, several service paths
Choose a service path, then edit issue choices, identifiers, and routing.
Customer, model, condition, and pickup details for walk-ins.
Return address, tracking, accessories, condition, and estimate contact.
Conditional questions for battery, charging, display, liquid, audio, and software issues.
Billing details with repeatable asset tags, users, priorities, and faults.
Repair intake workflow
Define your devices and services, generate the structure, then tailor questions and routing.
Name accepted brands, common jobs, intake channels, identifiers, estimate steps, and contact choices.
Require essential device details and reveal relevant battery, liquid-exposure, or shipping questions.
Share before appointments, at the counter, on your site, or with remote customers.
Send submissions to the repair inbox and route by issue, location, or urgency.
Online intake vs improvised notes
Calls capture whatever someone remembers. A generated intake creates a consistent, device-specific record.
Field guide
Use these six sections as the intake backbone. Adjust required fields and helper text for the services, device brands, privacy practices, and estimate process used by your shop.
Customer & communication
Identify the customer and record how to reach them when inspection is complete.
Device identity
Capture the exact model and an identifier so the request stays with the correct device.
Problem & history
Use repair categories to reveal focused questions about events, timing, frequency, and attempted fixes.
Condition & included items
Use a checklist and photos to give customers and staff a shared handoff record.
Service preferences
Capture the desired outcome and inspection contact. Separate requested timing from confirmed completion.
Intake acknowledgment
Place the shop's inspection, estimate, data, storage, and unclaimed-device wording beside the relevant fields.
Related tools
Extend intake into appointments, work orders, warranty claims, and returns.
FAQ
Straightforward answers for repair-shop owners, counter staff, and technicians improving their intake process.
A phone repair form records the customer, exact device, reported fault, condition, accessories, requested timing, and contact preference. It gives inspection staff a consistent starting point.
Include customer contact; exact model and serial or IMEI number; issue and symptom history; function checks; condition photos; accessories; requested timing; estimate contact; and return method. Add follow-ups for accepted repairs.
Yes. Branch from the issue category. Charging can reveal cable and port questions; liquid exposure can ask when it happened; screen damage can ask about touch, display, cracks, and frame bends.
Request access information only when necessary, and explain why, who can access it, and how it is handled. Offer customer-assisted unlocking, a temporary code, or limited testing without access.
Yes. Add uploads for the front, back, frame, cameras, and damage. Give lighting and focus instructions. Photos improve the intake record but do not replace inspection.
Collect organization, requester, billing, order reference, location, and deadline once. Repeat asset tag, user, model, identifier, issue, condition, priority, and accessories for each phone.
Yes. Makeform offers unlimited free forms and responses, so you can generate, edit, publish, and use the intake without a response cap. The paid tier removes the Makeform badge.
For walk-ins, share before arrival or at the counter, then verify identity, condition, and accessories. For mail-ins, add return address, tracking, package contents, and return method.
Replace scattered intake notes with one clear request.
