Changelog

Have something to say?

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

Option to Update Saved Design in social share

Currently, users can save a custom design in social share for repeat use. But if they make a small adjustment, and want to update an existing saved design, there is no such option. The only workaround for them is to save with a new name and deleted the old one. Which they might not be able to figure out or think as a beginner. The other issue this limitation creates is with social template blueprints. We have re-sync option with blueprints, but it doesnโ€™t work here cause we canโ€™t update the original blueprint source of social template.

Arun Saini about 4 hours ago

๐Ÿ’ก Feature Request

Social Images customization controls

The current social image design tool works great & easy to use for begginers but the design possibilities are quite limited with current control options. The idea is to add a few more low effort controls that increases the design posiblities and improve outcome by a great margin. 1. Custom gradient backgrounds Problem: gradients are fixed presets. A business cannot produce a background in its own brand colours, which is the single most common thing an SMB wants from a template. Today the only path to a brand-coloured background is a flat solid fill. Behaviour: two colour stops with hex input, plus an angle control. Keep the existing presets as a starting row. Implementation: two hex fields and eight fixed angles (0, 45, 90, 135, 180, 225, 270, 315) rather than a free dial, which is easier to build and produces better results from non-designers. Add a "generate from brand colour" button that derives a second stop by lightening the brand colour by roughly 25% and shifting hue 15 to 20 degrees. That button is the plug-and-play path, and most users will never touch the hex fields. 2. Automatic text contrast Problem: with the card removed, review text is a fixed colour. Any user who picks a light background gets an unreadable image. Live bug in the two existing no-card templates. Behaviour: compute relative luminance beneath the text and switch the text stack between light and dark. Applies to review text, author name, rating number, and the Google wordmark together. Implementation: WCAG relative luminance. Sample at the text block's centroid for gradients; after the overlay for photos. Ship automatic with no user-facing control. 3. Background overlay, 0 to 70% darken Problem: photo backgrounds only work behind an opaque card, so the photo is wallpaper. With the card off, text on a raw photo is unreadable on most uploads. Behaviour: one slider applying a black overlay to the background layer only. Implementation: one composited layer between background and content. Default 0% for colour and gradient, 40% when a photo is set. Unlocks: photo backgrounds with the card removed, the layout style that reads as native social content rather than a template. 4. Text alignment, left or centred Problem: every template is left-aligned. Behaviour: one toggle covering review text, author row, and star row as a group. Logo and rating stay in the bar. Implementation: trivial. Flag it in the template preset. Unlocks: a visibly distinct variant of every existing template. 5. Bar treatment, height and style Problem: the bar is a fixed-height strip whose only variable is colour, and it only exists when the card background is on. Behaviour: a height option (compact / standard / tall) and a style option (solid / hairline / none). Allow a bar when the card is off. Implementation: the bar becomes an independent layer rather than a child of the card. Hairline renders a 2px rule in the brand colour with the logo and rating on the background. None floats them directly. Unlocks: the split-block layout via tall, the editorial look via hairline, and a light bar on dark templates.

Arun Saini about 8 hours ago

๐Ÿ’ก Feature Request

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 22 days 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 about 1 month ago

๐Ÿ’ก Feature Request

๐Ÿ‡ซ๐Ÿ‡ท 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 about 1 month 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 2 months 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 2 months ago

๐Ÿ› Bug Reports