Back
Retently
Retently
#retently
Measure customer satisfaction, collect valuable client feedback that you can act on, prevent customer churn, and turn detractors into promoters.
Load previous page…
Recording who connects, reconnects, disconnects or changes settings on every integration and mailbox 
#retently
Customer and internal email subjects standardised. Customer subjects all contain "Retently"; campaign-alert prefixes are unchanged so customer inbox rules keep matching. Every rewrite that states a consequence was checked against its email body. #retently
Star, thumbs and emoji scales: the question box is full width so its alignment shows, and the left label's accept/dismiss icons sit on its left instead of over the images. Button settings: the text and icon colour picker opens rightwards from its swatch instead of under the fixed nav. #retently
Added protection against automated bulk copying of our Help Center, so it stays fast and reliable for customers while normal reading, search and links work exactly as before. #retently
The wp scraper block list now resolves flagged visitors on its own, using Claude with unban-by-default, and it is live on wp #retently
The topic chips in the geo table now link to their topic page, and the clicks are tracked in PostHog. #retently
Rewrote the public notes in both SDK manifests (public/components/embed/sdk-manifest.json and public/widget/manifest.json) as customer-safe summaries, removing Linear ticket IDs, security-audit and open-weakness detail, billing
internals, commit SHAs, and stack/infra details #retently
Tracking who scrapes help.retently.com and have decided to build our own KB with a public version and a fuller logged-in version #retently
Question: are competitors regularly pulling our Intercom help center (help.retently.com) to copy features, and should the KB be gated to logged-in / paid customers? #retently
Blocking the proxy pool behind the /blog scraper without hurting real users or AI crawlers #retently