Describe your damage-report process. Makeform creates a customer-ready form with move identifiers, itemized damage, photo uploads, requested resolution, and a follow-up path.
Send claim submissions to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a starting point, adapt it, or send it into the builder. These are example structures, not submitted claims.
Audience
Residential customers reporting damaged belongings
Format
Itemized claim with photos and values
Prompt size
327 chars
Example form structure
Itemized claim with photos and values
Customer and move details
Order or bill-of-lading number
Describe each damaged item
Upload damage photos and receipts
Requested resolution
Suggested routing tags
New claim
Needs documents
Ready for review
Request one entry per item so reviewers can match photos and estimates correctly.
Step 1
Identify
customer, move, order, and delivery
Step 2
Itemize
one record for each damaged item
Step 3
Document
photos, receipts, and estimates
Step 4
Route
complete claim sent to the right reviewer
A cleaner claim intake
A purpose-built form gives customers a clear sequence and reviewers consistent move, item, and attachment details.
Repeatable groups keep each item's inventory number, damage, value, and files together.
Order number, route, dates, and contact fields help staff locate the job record.
Send responses to the claims workflow with useful review-status tags.
Built around the move
Use one core record, then show details relevant to each moving service.
Inventory tags, rooms, purchase dates, values, and condition photos for household belongings.
Asset tags, serial numbers, authorized contacts, work impact, and repair estimates for office equipment.
Unit references, seal condition, packaging details, and notes made when stored goods were delivered.
Show furniture, electronics, or missing-item questions only when the selected item category calls for them.
Build the workflow
Describe what reviewers need, refine the structure, and connect submissions to the next step.
List the move references, item facts, attachments, and acknowledgment reviewers need.
Use your terminology, explain useful photos, and require essential questions.
Repeat item sections and route submissions by branch or status.
Link the form from delivery emails, instructions, and your help center.
Choose the intake method
Required fields and grouped uploads reduce follow-up for missing move and item details.
Field guide
These sections connect the customer, shipment, belongings, and supporting documents.
Customer
Identify the submitter, their relationship to the move, and the best way to follow up.
Move record
Collect identifiers from customer paperwork using labels that match your documents.
Item record
Use mover inventory tags and enough detail to distinguish similar belongings.
Damage details
Combine a plain-language description with structured discovery and usability details.
Supporting files
Keep uploads with each item and request full views, close-ups, packaging, and labels.
Resolution and acknowledgment
Record the requested outcome, then show your accuracy statement and follow-up instructions.
Related tools
Build related loss, incident, inventory, inspection, and repair forms.
Capture an early report of loss before a complete itemized claim is available.
Open toolDocument what happened during a move, including people, locations, and follow-up details.
Open toolGive service complaints that are not damage claims their own organized intake path.
Open toolRecord item identifiers and condition details before assets are transported.
Open toolBuild structured inspection checklists with observations and supporting images.
Open toolRoute approved repair needs with item details, photos, and requested scheduling information.
Open toolFAQ
Practical answers for moving companies replacing email-based claim intake.
It lets a customer report belongings damaged or missing during a move or storage delivery. It connects the move record with item descriptions, values, photos, documents, and requested outcome for review.
Collect contact and job details, move dates, and discovery date. Per item, request its inventory number, prior condition, damage, age, value, photos, and available receipts or estimates. Finish with requested resolution and an accuracy acknowledgment.
Yes. A repeatable section lets customers add items while keeping each item's identifiers, damage, value, and uploads together. This is easier to review than one combined narrative.
Yes. Add item-level upload fields for wide photos, close-ups, packaging, inventory tags, delivery paperwork, receipts, and estimates. Explain which files are useful and provide an extra notes field.
It can offer repair, replacement, reimbursement, or contact to discuss. Present this as a request, not a promised outcome. Your team can evaluate it using its own process.
Yes. Collect the branch, service type, or job number needed for routing, then send the response to the appropriate inbox or sheet. Status tags can identify missing documents or review readiness.
Yes. Makeform is unlimited free for generating, editing, publishing, and collecting responses. The paid tier only removes the Makeform badge.
Yes. Add your current instructions, contacts, document list, and reporting deadlines. Maintain the wording internally and do not imply that submission confirms responsibility or a specific outcome.
Replace scattered claim emails with one clear intake.
