Describe your delivery workflow. Makeform turns it into a focused survey with order lookup, ratings, conditional follow-ups, photo uploads, and contact permission.
Send delivery feedback to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a prompt, adapt it, or send it into the Makeform builder.
Audience
Customers after a parcel arrives
Format
Short post-delivery survey with issue branching
Prompt size
280 chars
Example form structure
Short post-delivery survey with issue branching
Order number and delivery date
Which carrier delivered the order?
Rate timing, tracking, and package condition
What went wrong with this delivery?
May our support team contact you?
Suggested routing tags
Positive delivery
Late arrival
Damage or missing item
Ask for an order number first, then show issue details only when a customer reports a problem.
Step 1
Identify
match feedback to an order or shipment
Step 2
Rate
score timing, condition, updates, and handoff
Step 3
Explain
collect issue details only when relevant
Step 4
Route
send the response to the right team
Why delivery-specific feedback
Separate milestone ratings distinguish late updates from damaged packaging, unclear instructions, or a poor handoff.
Keep positive responses brief; reveal issue, explanation, and photo fields after a low rating or damage report.
Collect the order reference, carrier, and date so operations can find the shipment behind a response.
Tag delays, damage, missing items, and handoff concerns for the responsible support or operations queue.
Built around the last mile
Choose the closest flow, then change its milestones, vocabulary, and exceptions.
Measure tracking, timing, packaging, item condition, and placement.
Ask about instructions, communication, proof of delivery, and professionalism.
Cover arrival, property care, assembly, packaging removal, and crew conduct.
Record appointments, pallet condition, quantities, paperwork, and unloading.
Survey workflow
Start with shipment context, ask about observable moments, and route each exception.
Name the carrier model, milestones, audience, identifiers, and outcomes your team uses.
Use consistent scales and reveal exception details only for relevant answers.
Send the link after delivery, add it to a receipt, or use a QR code.
Filter by carrier, route, location, issue, or date; route service concerns.
Focused survey vs generic review
Choose based on whether you need broad sentiment or detail about one delivery.
Field guide
Use six sections to connect feedback to a shipment, compare ratings, and support follow-up.
Shipment context
Ask for a searchable reference. An order number, date, and carrier create a useful match without slowing the opening.
Core ratings
Use one labeled scale for timing, tracking, condition, and handoff. Separate scores reveal the weak stage.
Issue branching
Show targeted choices after low ratings or exceptions. Routine deliveries skip them; issue reports gain detail.
Evidence and explanation
A description and upload can clarify damage, placement, or receiving exceptions. Label the evidence requested.
Follow-up permission
Ask whether the customer wants a reply before requesting contact details. This separates feedback from a support need.
Internal routing
Map exception choices to tags and destinations. Send damage, delays, and missing items to their responsible queues.
Related tools
Build adjacent forms for feedback, delivery details, returns, and orders.
FAQ
Practical answers for e-commerce, courier, logistics, and receiving teams building a post-delivery survey.
It is a post-delivery survey tied to an order or shipment. Recipients rate timing, tracking, condition, instructions, and handoff; comments and uploads explain exceptions.
Collect the shipment reference and date. Rate the arrival window, updates, condition, and handoff. Show issue type, explanation, upload, and contact permission after a problem.
Keep the default path to shipment identification, three or four ratings, and an optional comment. Conditional questions can cover delays, damage, missing items, placement, or courier concerns.
Yes. Show a file upload after damage or poor condition is selected. Explain which packaging or item photos are useful and provide a comment for context.
Yes. Conditional logic can open an issue category, comment, upload, or contact-permission question after a low score. Apply the same threshold across ratings.
Yes. Makeform offers unlimited free forms and responses, including generating, editing, and publishing your delivery feedback form. The paid tier removes the Makeform badge; it is not required to keep collecting responses.
Match issue choices and tags to team ownership. Route damage, missing items, delays, and courier concerns to their responsible queues. Ask permission before contacting the respondent.
Yes. Add carrier and method dropdowns, then show conditional parcel, courier, in-home, or freight sections. Keep shared rating labels consistent for comparison.
Turn the doorstep moment into useful feedback.
