How to Request Customer Feedback Automatically

Choose a moment when feedback makes sense

Ask after the customer has had time to use the result. For a repair, that may be after the equipment is returned. For a design project, it may be after the approved files are delivered. Choose the event that means the customer actually received the service.

Do not use an invoice being created as proof that the job is complete. Agree which record holds the completion date and who can change it. A reopened job should leave the normal feedback queue until its status is clear.

Start with one service and one request. A business with several bookings for the same customer also needs a sensible contact-frequency limit so each booking does not trigger another message.

Ask a question you can use

Keep the first version short. Two useful questions are “How well did the service meet your needs?” and “What should we improve next time?” Add an optional way to request a reply.

Explain who will read the answer. If you need to connect feedback to a job, do not describe it as anonymous. If you offer an anonymous form, avoid reminders that depend on knowing exactly who responded.

Keep the wording neutral and offer the same opportunity to customers with positive and negative experiences. This workflow collects useful service feedback; it should not filter unhappy customers out of a separate public-review process.

Work through one finished job

Example: a small repair business marks job J208 as Collected on Monday. Its rule queues one feedback email for Wednesday. Before sending, it checks that J208 is still complete, the address is usable and the customer has not asked to stop these requests.

The message could say: “How did the repair go? We would welcome a short reply about what worked and what we could improve. You can reply to this email or use the feedback form. Please tell us if you would rather not receive future feedback requests.”

The customer replies that the repair works but collection instructions were unclear. The workflow marks feedback Received and assigns the comment to the service coordinator. It does not send a second request or claim that the issue has been resolved.

Use a form customers can actually open

If you use Microsoft Forms, review the Collect responses settings. A form restricted to your organisation will not work for ordinary external customers. Microsoft documents an Anyone can respond option as well as organisation-restricted choices.

Test the link outside your staff account. Confirm that the customer sees only the questions and any information you intend to show. Do not put a customer name, email address or private job description in a public form link.

Check the chosen tool’s current plan limits and the business’s normal contact rules before enabling sending. Use an approved sender that accepts replies, and make it clear how a customer can stop future requests.

Keep a small send record

Record the job reference, feedback-request version, planned send time, actual result and response state. The same job and request version should not produce two sends when a workflow restarts.

Check the latest status immediately before sending. A cancelled job, stopped contact or already received reply should remove the queued request. A changed address needs the same checks as any other customer contact update.

If the email service returns an unclear result, inspect its delivery record before retrying. If the form cannot reliably identify responses, use a single invitation with no automatic chase. That is safer than repeatedly asking people who already answered.

Give feedback a clear owner

A response is useful only if someone reads it. Route comments to the service owner and keep a simple status such as New, Reviewing and Closed. Include the related job link for people who already have access.

An optional automated acknowledgement can confirm receipt, but it should not promise a refund, deadline or fix that nobody has approved. Let the responsible person decide the next step and reply through the normal business channel.

Review recurring themes, such as unclear collection instructions or a missing handover guide. Keep customer identities out of broad team summaries when the theme can be explained without them.

Check the whole experience

Test a completed job, a reopened job, a repeated event, an invalid address, a stopped contact and a reply received before the planned send. Read the message and complete the form on a phone.

After the trial, review requests sent, delivery failures, responses and issues actually followed up. A high send count alone does not mean customers are happier. Use the comments to choose a concrete service improvement.

The worksheet below covers the timing, wording and stop rules. Contact Automations For Business on WhatsApp with your job system and a blank feedback form if you want help connecting the steps.

Your ready-to-use checklist

Make the next step clear.

Sources and notes

Sources checked on October 22, 2026.

• Microsoft: form response access

  External versus organisation-restricted form access.

• Microsoft: automated Forms workflow

  A form response can start a follow-up workflow.