Acknowledgements can show where useful feedback and expertise came from. They should also distinguish a contributor, a customer and a commercial partner. This page defines an acknowledgement framework; it is not a directory of verified Gavek customers.
Describe the contribution accurately
Record the specific assistance, such as reporting a broken explanation, checking a technical example or reviewing a translation. Thanking someone for feedback does not imply they use every product or endorse the business. Ask how they want their name and contribution described.
Seek permission before publishing identity
Obtain approval for the name, logo, quote and link you intend to use. State whether a commercial relationship or incentive exists when relevant. Avoid displaying a familiar brand merely because an employee submitted a support question or attended a public event.
Keep recognition maintainable
Assign someone to review acknowledgements and process corrections or removal requests. Use dated context where a contribution relates to an old version. Prefer a precise description of the contribution over a broad testimonial that the contributor never approved.
Put the method to work
Illustrative acknowledgement: a Danish editor spots an ambiguous instruction in a guide. With permission, the website thanks the editor for reviewing that paragraph. It does not add their employer’s logo to a customer wall or claim that their organisation recommends the platform.
Your next steps
- Identify the actual contribution.
- Approve wording and identity separately.
- Disclose relevant incentives.
- Provide a correction and removal route.
Questions & answers
Can a contributor also be a customer?
Yes, but each relationship should be verified and described separately. One role does not establish the other.
Does this list Gavek’s existing community?
No. No named customer, partner or endorsement is asserted on this framework page.
Documentation & further reading
- developers.google.com · › search › docs › fundamentals › creating-helpful-content
- developers.google.com · › search › blog › 2023 › 02 › google-search-and-ai-content
- developers.google.com · › search › docs › fundamentals › using-gen-ai-content
Explore the related in-depth guide ↗ · Build an action plan ↗