Practical guide

Close the feedback loop without promising what you cannot deliver

Last materially reviewed 2026-10-01

Quick answerAcknowledge, explain and distinguish a completed change from a proposed one.
What to know

Choose the appropriate response

Some feedback needs an individual support response; some informs a general service update. Use the organization’s authorized channel and avoid publishing a person’s comment or identity merely because they submitted a survey. A survey submission is not permission for every subsequent use. This page is process guidance, not a consent or messaging-law determination.

What to know

Use precise progress language

“We are reviewing the collection instructions” means something different from “The collection instructions have been corrected.” Do not announce a resolved problem when the work is only assigned. A fictional update might say that the entrance map was corrected on a stated date while a separate accessibility issue remains under review. That makes the boundary understandable.

What to know

Do not promise an individual outcome

A general feedback form should not imply a guaranteed personal resolution or a response deadline that nobody can meet. Give an appropriate support route for urgent or account-specific matters. Avoid inviting passwords, order records or other unnecessary private details into a general comment field.

What to know

Keep the record modest

Preserve what was communicated, to which appropriate audience and why. Do not treat an acknowledgment, email delivery or board movement as evidence that the recipient read or accepted the result. The useful endpoint is an honest account of the action, not a manufactured engagement metric.

What to know

A factual update example

An original fictional update could say: “We checked the collection directions and corrected the map link. Feedback about opening hours has been passed to the service manager for review.” It names a completed action and a separate pending one. It does not promise new hours, publish a respondent’s identity or claim everyone is satisfied. Adapt any real communication through your approved process; this example is not sent by the site and is not a substitute for reviewing the actual facts.

Continue when useful

Next: Review access

Review the form, response store, exports and integrations as separate places data can travel.

Open Review access →

Sources used for this page

These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.

  1. Yay! Forms response board — Merchant documentation · yayforms.com · Merchant-controlled · checked 2026-10-01