Have something to say?

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

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 22 days 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 22 days ago

πŸ› Bug Reports

Multiple message fields in testimonial forms overwrite/misroute input

Description We wanted to use a testimonial form for an employee survey. For this, we added multiple β€œMessage” fields, where each message field represented a separate question. Example questions: β€œHow satisfied are you with your current work environment?” β€œHow do you rate the opportunities for professional development within the company?” β€œWhat could be improved in internal communication?” Steps to reproduce Create a testimonial form. Add multiple β€œMessage” fields. Use each message field as a separate question. Open the public form link. Try to answer the first message field. Actual result Input entered into one message field appears in another message field instead. The individual questions cannot be answered separately. Expected result Each message field should work independently and save the answer for its own question. Impact Customers cannot use testimonial forms for structured employee surveys or feedback forms with multiple open questions.

J.D 22 days ago

πŸ› Bug Reports

Organization invite links sometimes redirect to 404

Description Invitation links for newly created organizations do not reliably open the correct join page. Invited users are often redirected to a 404 page after clicking the link in the invitation email. Steps to reproduce Create a new organization. Invite an employee. Send the invite from either the organization/customer view or the agency view. Open the invitation link from the email. Actual result The invitation link redirects to a 404 page. This happened with customer invites, agency-view invites, and a self-invite test. In one case, incognito mode worked once, but for other users incognito mode still led to a 404 page. Expected result The invite link should always open the correct join/setup page for the invited organization, regardless of login status or browser mode. Impact Employees cannot reliably join new organizations, which blocks customer onboarding.

J.D 22 days ago

πŸ’‘ Feature Request