Changelog

Have something to say?

Tell us how we could make the product more useful to you.

Rewrite the subject line of AI Insights

Currently, it sounds like something urgent that they have to deal with instantly, instead I think it would be better if the subject line is much softer and aligns with its purpose their regular ai insights report is ready. Current version: “Action Required: Critical insights for organization name“ Even better, if the agencies get the option to set their own subject lines/content, for such report and insight emails.

Arun Saini about 23 hours ago

💡 Feature Request

Private mode only for regulated professions

For regulated professions that are not permitted to collect customer reviews for public display, would it be possible to offer them a secure, private collection method that prevents publication, so as not to be considered an illegal solution? This would allow them to collect reviews to improve their service. And responding to unsolicited reviews is not prohibited by law. Responding to reviews helps show Google that the GBP is active, and the keywords used contribute to local SEO.

Romaric 15 days ago

💡 Feature Request

You are currently impersonating another WORD user - bad translation 🇵🇱

Hi, I'd like to suggest changing the wording of the impersonation banner. The current message: „Obecnie podszywasz się pod innego użytkownika.” has a rather negative connotation. The phrase „podszywasz się” is commonly associated with fraud or unauthorized access, even though that's not what this feature does. I would suggest replacing it with: „Przeglądasz konto klienta: WORD Nauka Jazdy.” In my opinion, this wording is more natural, more user-friendly, and better describes the purpose of this feature. Thank you for considering this suggestion.

Paweł Maćkowiak 20 days ago

🐛 Bug Reports

🇫🇷 Request for French agencies

I noticed a translation trouble in the customer sidebar. "récolte" is an agricultural word. So it is really weird to read this. It sounds bad translation. So would you mind to say yes in order to replace "récolte" by "collecte". It is more accurate. Moreover, the initial name of the section in the English version is 'Review tools', so a more accurate translation would be 'Collecte d’avis'.

Romaric 23 days ago

💡 Feature Request

UX Issue: “Content & Flow” shows unrelated sections

Description The “Content & Flow” area shows sections that do not belong to the selected form/funnel type. Example When creating a testimonial form, sections such as “Private Feedback” or other review-flow settings are still visible, even though they do not clearly belong to testimonials. Actual result Different form/funnel types appear to overlap in the UI. Users may not understand whether they are creating a testimonial form, private feedback form, public review request flow, or a mixed flow. Expected result Only settings relevant to the selected form/funnel type should be shown. For example: Testimonial form → only testimonial settings Private feedback → only private feedback settings Public review request → only review-platform settings Impact The current UI is confusing for customers and agencies and makes it difficult to understand which settings affect the published form. Suggested improvement Hide irrelevant sections dynamically or separate the form/funnel types more clearly.

J.D about 1 month ago

💡 Feature Request

Form preview shows wrong flow or content

Description The form preview does not always match the selected form type or the current configuration. In some cases, the preview shows content from a different flow or displays fields/pages that do not belong to the form being edited. Steps to reproduce Open the form editor. Go to the “Content & Flow” tab. Open the relevant configuration sections in the left-hand sidebar. Create or edit a testimonial form. Configure testimonial-specific fields/content. Check the preview on the right side while editing and switching between sections. Actual result The preview sometimes displays unrelated review-flow content, wrong thank-you pages, platform options, or fields that are not part of the current form. Examples observed: A testimonial form preview shows a review/thank-you page with Kununu as a platform option. The preview shows fields that were not created in the testimonial form. The editor and preview appear to show different form states. Expected result The preview should always reflect the currently selected form type and its active configuration. Impact Users cannot reliably see what the published form will look like, which creates confusion and increases the risk of publishing the wrong flow.

J.D about 1 month ago

🐛 Bug Reports