Describe what your shop repairs. Makeform creates a repair intake form for customer contact, item identification, reported symptoms, visible condition, accessories, and drop-off details.
Route repair intake submissions to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a workflow, adjust the prompt, or send it to the builder. The preview is an example, not a completed repair ticket.
Audience
Counter staff receiving phones, tablets, and computers
Format
Device intake with identifiers and condition photos
Prompt size
276 chars
Example form structure
Device intake with identifiers and condition photos
Customer name and contact
Device brand, model, and serial number
Describe the problem and when it started
Photos of visible condition
Accessories left with the device
Suggested routing tags
New drop-offs
Needs assessment
Priority service
Keep the customer's description separate from staff condition notes so an intake observation is not mistaken for a diagnosis.
Step 1
Identify
customer, item, model, and serial number
Step 2
Document
reported fault, condition, photos, and accessories
Step 3
Route
priority, technician queue, and contact preference
Step 4
Confirm
submission stored and drop-off details recorded
A cleaner handoff
Keep the customer's report, item identity, and counter observations together before assessment.
Identity fields connect the customer to the exact item, including model and serial number.
Capture what happened, when it began, its frequency, and triggers without implying a diagnosis.
Condition photos, accessories, urgency, and contact preference help staff sort new work.
Built for repair counters
Choose a workflow, then customize its item types, identifiers, checklists, and routing.
Capture identifiers, error behavior, condition, chargers, and cases.
Record component symptoms, incidents, frame identifiers, wear, and removable gear.
Ask about fault patterns, error codes, cords, attachments, and prior attempts.
Preserve owner descriptions, condition, identifying marks, cases, and requested dates.
Intake workflow
Turn your counter checklist into a workflow staff can complete at drop-off.
Name accepted items, identifiers, problem categories, and details needed before assessment.
Require contact and identity fields, then add condition choices and accessory lists.
Show liquid, crash, or error-code questions only for relevant item types.
Use the form at the counter or share it before arrival, then route submissions.
Paper vs generic notes vs structured intake
A useful intake makes identity, symptoms, condition, and contact details easy to scan.
Field guide
These six field groups create a practical handoff from the customer and counter staff to whoever assesses the item.
Customer contact
Collect the customer's name, phone, email, and preferred channel so staff know how to follow up.
Item identity
Use fields for category, maker, model, color, serial number, and identifying marks.
Reported problem
Ask what is wrong, when it began, how often it occurs, and what reproduces it. Keep technician findings separate.
Condition at drop-off
A checklist and photos document cracks, dents, corrosion, missing parts, and other visible details at intake.
Accessories and history
List each charger, case, battery, cable, attachment, or part received. Note prior damage and repair attempts.
Shop routing
Add categories for service type, urgency, location, or technician group. Treat requested dates as unconfirmed until review.
Related tools
Build connected requests, inspections, work orders, and maintenance forms.
Receive maintenance needs for facilities or equipment.
Open toolFAQ
Practical answers for repair shops replacing handwritten counter notes with consistent digital intake.
A repair intake form records a dropped-off item. It connects customer contact, item identifiers, the reported problem, visible condition, included accessories, and routing information in one submission.
Include customer contact; item type, brand, model, and serial number; the reported problem and timing; condition photos; accessories; prior repair attempts; drop-off date; and staff initials. Add identifiers specific to your items.
Use a long-answer field for the customer's description, then ask about timing, frequency, triggers, and error messages. Keep this report distinct from technician assessment fields.
Yes. File uploads let customers share damage, labels, serial numbers, or error screens before arrival. Staff can add current condition photos at the counter.
Yes. Start with an item-type choice, then show relevant paths. Phones can show liquid-exposure questions while bicycles show crash and component questions. Shared contact and drop-off fields stay consistent.
Use checkboxes for common accessories plus fields for names, quantities, colors, and condition. This works for multiple cables, batteries, cases, attachments, or specialty parts.
Yes. Makeform supports unlimited free forms and responses, so you can generate, edit, publish, and use the repair intake form without a response cap. The paid tier removes the Makeform badge.
Submissions appear in the Makeform inbox and can route to Google Sheets, Slack, or Zapier. Use a consistent intake number or item identifier when matching them to internal records.
Replace incomplete counter notes.
