Asklet

Asklet's core idea is simple and genuinely useful: a survey is a fixed script, and the most valuable feedback is usually the sentence you didn't plan for. Asklet's widget reads each answer and asks the next question that follows from it, so "the checkout feels slow" becomes a thread about which step, which device, and compared to what. Respondents can type or speak, and the voice path is worth calling out — spoken answers tend to run longer and cover details people skip when typing. Placement is flexible: in-product, on a page, in an email, or after a support ticket closes. The real value shows up once the conversation lands in Sunbeam. Answers feed the same themes, impact scores, and system model as every other source, so a conversational reply is simply better raw material for analysis rather than a separate silo. Sunbeam names themes automatically, auto-discovers the actors and components in your product, and scores which themes drive NPS, ratings, and churn. The change analysis shipped 15 May 2026 adds step-change detection, emerging themes, concentration shifts, and distribution shifts with a significance score, so you see flagged events instead of eyeballing chart after chart. That pass was later backfilled across historical dashboards, and change-point annotations now sit on the actual date of the change. Trial dashboards refresh weekly for a month as of 6 June 2026, so an evaluation doesn't freeze on day one. Where it doesn't fit: teams that only want numeric ratings or multiple-choice results, buyers who want a standalone conversational widget with no analytics platform attached, and organisations with no pipeline to route free-text into. Asklet is not a replacement for your survey tool's panel or logic branching. The honest framing is that Asklet makes most sense as the qualitative capture layer on top of Sunbeam — if you're not using Sunbeam, you're paying for half a product.