Use creator feedback as an internal product-research record, with a separate decision for any public quote, image, or testimonial. Record what the creator experienced, who may review it, and whether you may follow up. Keep public-use status at "not requested" until you have asked about a specific use and documented the response. A positive reply alone should never move a comment into your advertising library.
That separation lets a creator say the product needs work without turning their answer into a negotiation about posting.
Identify the intended use before sharing the answer
For U.S. advertising, the FTC defines an endorsement by its advertising context and how consumers understand the message. An internal product note and a quote on a sales page have different purposes. Calling the quote "feedback" on the sales page does not settle whether it is an endorsement.
Use these questions when a response arrives:
- Product learning. Does someone need this observation to investigate or improve the product? Share the relevant detail within the internal scope you explained.
- Creator support. Does the creator need an answer or help with a product problem? Assign a named owner and keep the support conversation separate from content requests.
- Public promotion. Does someone want to use the words, identity, photo, or video to persuade buyers? Open a separate permissions and advertising review.
These are recommended workflow categories. They are not regulatory classifications or a substitute for reviewing the proposed use.
Modash's gifting survey article recommends asking about the product experience during follow-up. It also describes brands expecting usage rights despite informal gifting arrangements. Make your own request explicit before collecting responses. For wording that leaves posting optional, use the guide to following up after delivery without demanding a post.
A feedback intake form you can adapt
Start with a short explanation of who will see the answers. Do not bury a public testimonial release in the submit button.
The following is suggested form copy for a voluntary, private feedback request. Use it only if your team's practices match it:
We would like to understand your experience with the product. Feedback is optional, and criticism is welcome. Our creator partnerships and product teams will review your answers for product improvement and support. This form does not authorize public quotes, use of your name, or reuse of your photos. Any request for public use will be separate.
Link the form to your actual privacy information. Under UK GDPR purpose-limitation guidance, organizations must explain their purposes for collecting personal information. A new purpose requires a lawful basis and consideration of the rules on compatible reuse. The preference fields below do not, by themselves, resolve those duties.
| Field | What to ask or record |
|---|---|
| Product | Which product and variant did you try? |
| Experience | What were you trying to do, and what happened? |
| What worked | Which parts suited your needs? |
| What needs attention | What was confusing, inconvenient, or disappointing? |
| Context | Was the observation occasional, repeated, or something you have not tested again? |
| Attachments | Optional photo or video that helps explain the observation; internal review only |
| Internal sharing preference | May the named product team review the response with your name, or would you prefer a summary without your name? |
| Follow-up | May the partnerships contact ask you to clarify this feedback? |
| Public-use status | Staff-controlled field, initially "not requested" |
| Record details | Response date, product record, owner, original message reference |
Avoid collecting a mailing address again in this form. Link to the fulfillment record if an authorized support colleague needs it. Keep unrelated personal details out of the product-team copy as an operational default. Removing a name alone does not guarantee anonymity, especially when a photo or distinctive situation identifies the creator.
Preserve the original message and write the team's interpretation in a separate field. That makes it possible to check whether a summary changes the creator's meaning.
Product-team handoff matrix
The examples below are illustrative. They are invented to show routing decisions, not real creator comments or evidence about a product.
| Illustrative feedback | Owner | Handoff | Public-use decision |
|---|---|---|---|
| A bag's inside pocket is hard to reach | Product design | Product variant, task attempted, original observation | Keep internal; no quote request needed |
| A zipper repeatedly catches | Quality team | Occurrence context, product identifier, optional attachment | Keep separate from promotional review |
| The opening instructions are unclear | Documentation owner | Step that confused the creator and proposed clarification | Do not turn confusion into an endorsement |
| The creator likes the fabric but dislikes the pocket layout | Product manager | Preserve both observations in the same record | Any proposed quote must preserve the relevant context |
| The creator would like to discuss a paid demonstration | Partnerships owner | Open a new partnership conversation | No public rights inferred from the offer |
Give every handoff an owner, next action, and review date. Useful statuses include "needs clarification," "under review," "change planned," and "closed with explanation." None of these statuses should update public-use permissions.
A report of one problem is a lead for investigation. It does not establish the cause or how often buyers experience it. Group related observations for review, but preserve product variants and the difference between direct experience and a suggested improvement.
When you reply, say what the team did. If it reviewed the pocket layout but has no planned change, say that. Do not promise a redesign to secure a later post.
Move a private comment into public use only through a new request
If marketing wants to use a response, create a separate record linked to the original feedback. Include:
- The exact proposed excerpt or asset, including any edits.
- The intended placements, such as a product page, organic social post, or paid advertisement.
- Whether the creator's name, handle, photo, or voice will appear.
- The proposed duration and any compensation.
- The creator's response, approval date, and agreed limits.
- The advertising claims and disclosure review for that use.
Treat an unanswered request as unapproved in your workflow. An agreement to discuss a quote also leaves the quote unapproved. For a creator's existing public post, use the separate process for asking permission before reusing gifted content.
Permission and advertising accuracy need separate checks. The FTC's guidance says endorsements must reflect honest opinions and cannot make claims the advertiser could not lawfully make. Approval from the creator does not supply missing evidence for a product claim.
The same guidance explains that a free product can matter to an audience even when the creator had no obligation to post. For advertising that reaches U.S. consumers, assess the material connection and its disclosure. Do not assume that a voluntary testimonial removes that issue. Review other applicable jurisdictions separately.
Keep feedback responses out of your published-endorsement count. The guide to recording gifted mentions without inflating posting rates covers that reporting boundary.
Before your next feedback request, add separate internal-use and public-use fields. Then take one existing response through the handoff matrix and check that a product-team decision cannot accidentally authorize a testimonial.
