Starting
The first twenty minutes.
- How do I log in? I never set a password.
- There is no password. Your dashboard link is the way in — bookmark it. That is deliberate: nothing to forget, nothing to phish, and nothing of yours to leak in somebody else's breach. If you lose the link, the page at /access sends a one-time login link to the address on the account, and to no other address; it works once, for fifteen minutes, and opens every dashboard that address can reach.
- Is Hazelsong the same thing as Kudobox?
- Yes. Kudobox was renamed Hazelsong on October 5, 2026, and nothing else changed: the same product, the same plans and prices, the same projects and testimonials. The site is at hazelsong.com now, and getkudobox.com still answers, so a link you were sent, an embed code already on your site, an API key and a webhook all keep working with nothing for you to do. A webhook now carries its signature under both names, X-Hazelsong-Signature and X-Kudobox-Signature, and an embed finds its element under either id, hazelsong-wall or kudobox-wall. Support is at support@hazelsong.com, and a message written to support@getkudobox.com still arrives.
- What is the very first thing to do?
- Send your form link to three customers who already like you. Not a list of two hundred — three. You will learn more from the first three answers about which of your questions are working than from any amount of planning.
- How long does it take my customer?
- About a minute in writing. A video takes as long as they talk. They do not make an account, install anything, or download anything.
- Can I change the questions?
- Yes, and you should. The defaults are a starting point; the questions worth asking in your trade are on the page for your trade.
- Can I save a review straight from the page it is on?
- Yes. In your dashboard, under Ask, import and set up, press Remember this browser and drag Save to Hazelsong to your bookmarks bar. Then select what they wrote on any page and press it: a small window opens with their words as selected and the page they came from. It works in every browser, on every plan, and the words cannot be changed on the way.
The testimonials themselves
What can and cannot be done to them.
- Can I fix a typo in a testimonial?
- No. There is no route in this product — no dashboard control, no API field, no administrator, no support request — that can change a testimonial's text. That is the rule the whole product is built around, and it is checked in code rather than promised in a policy.
- Then what do I do about a phone number somebody left in it?
- Remove that span. The span becomes [removed], every other character stays exactly as written, and the reader is told something was taken out. If the proposal differs from the original by a single word anywhere else, the whole proposal is discarded rather than applied.
- Can I shorten a long testimonial for a widget?
- Not by storing a shorter version: nothing here can keep a cut-down copy as though it were what somebody wrote. What a layout may do is show less of it — the compact, marquee, toast and sidebar layouts stop a long testimonial at six lines, and there is no control that opens the rest. Every other layout shows the whole of it, so the choice to make here is the layout.
- A customer asked me to take theirs down. What happens?
- Delete it, and it is out of every widget, wall, image and API answer at once — a real delete, the record and the files both. There is no archive here: a testimonial is pending, approved or rejected, and once it is approved the dashboard's own way to take it off your pages is Delete. Reject is the button while it is still pending.
Permission
Who checked off what, and what that stops.
- Where is the consent kept?
- Beside the testimonial: the exact sentence your customer agreed to, the scopes they checked off, and the date. All of it comes out in your CSV export, which is the form you would want it in if anybody ever asked you to show it.
- Which of the three permissions does Hazelsong actually enforce?
- Two of the three, and the difference is worth knowing before you rely on it. Your website and your social media are places Hazelsong itself publishes, so those answers are enforced on every request: a testimonial that did not allow your website is not served by a widget, a wall or the API, on any plan, however many times it is approved, and the same goes for a social image or a clip. Advertising is not a channel Hazelsong has — ads and printed material are made by you — so that answer is recorded and handed to you rather than enforced. The collection form tells your customer exactly that, in those words, before they check anything.
- They checked off website but not ads. What happens if I use it in an ad?
- Nothing here stops you, because nothing here places ads. What the product does is keep the answer where you can find it: the consent sentence on the card names only the places that person allowed, and your CSV export lists what they checked off — which is the form you would want it in if they, or anybody else, ever asked what they had agreed to. The decision, and the responsibility for it, are yours. If you want a permission that holds on its own without you having to remember it, that is the website and social media permissions.
- Does the API respect the website permission too?
- Yes, and that is on purpose: an integration reading your testimonials is a publishing pipe. /api/v1/testimonials filters on website permission and says in its own answer that it did.
- What about a review I imported from Google?
- It carries a note saying the owner copied it from a public review and confirmed they may republish it — and that no permission was collected here, because none was. It never pretends the person was asked.
Putting them on your site
Widgets, walls and addresses.
- How much code is it?
- Two lines: a script tag and a div. The layout is a query string on the script tag, or a data attribute on the div — both of which live in your page, so turning a wall into a marquee later means editing those two lines where you pasted them. There is nothing to rebuild at this end.
- It shows nothing on my page.
- Three usual causes, in order of likelihood: nothing is published yet (Pending is not published); the builder you are using strips script tags from block content, in which case the tag goes in the theme footer; or you are looking at the editor preview rather than the live page, which is normal on Webflow, Framer, Elementor and Squarespace.
- Can I embed it in Notion or a newsletter?
- No, and not because of us: neither runs a third-party script. Link the hosted wall in Notion, and use a testimonial image in the newsletter. Email has not run JavaScript for twenty years.
- Does the widget slow my page down?
- It is one small script with no framework behind it and no font to fetch. It draws after your page has drawn.
- Is there a Hazelsong app in Zapier?
- Yes, and Zapier still lists it as Kudobox, the name Hazelsong had before: two triggers — a testimonial arrives, a testimonial is approved — and four actions: import one, ask somebody for one, find one, and get one as a picture. Until Zapier lists it in its public directory it is added by invitation, from the link on your dashboard's API page under Zapier, Make and the rest. It connects with an API key, which is part of Starter and Pro. Each trigger asks which permission the Zap needs and passes on nothing the writer did not allow.
Video
Recording, storing, cutting.
- What quality is the video stored at?
- The one it was recorded at. One copy is stored — the original — and it comes back at that quality on every plan, including the free one. There is no better version being withheld.
- Can I cut a clip for social?
- Yes, and it happens in your own browser: their footage, their voice, their name over it, cropped to the shape the platform wants. No queue, no server cost, no watermark.
- Can it generate a presenter or a voice?
- No, and it never will. A clip is a cut of footage a real person recorded, or it is not made. That is a deliberate refusal, not a missing feature.
- Can I cut a testimonial that is on YouTube?
- No. A video that lives on somebody else's platform is linked rather than cut — taking the footage off their player is not ours to do.
Plans and billing
What is free, what is paid, and how to leave.
- What does the free plan actually carry?
- Fifteen testimonials held at once — not fifteen a month. Deleting one frees a slot, because a plan that punishes you for tidying up is a trap. With them: all twenty-three layouts, unlimited widgets and walls, all forty import sources, the risk reading, the permission record, the removals, the reels, the thank-yous, and your files back at full quality.
- What am I paying for, then?
- Unlimited testimonials, your own mark with no credit of ours, your own address, more forms, more seats, the API and signed webhooks, and automatic collection from feeds.
- Is there a lifetime plan?
- No. Recurring or usage pricing only — a lifetime price for a product with a running cost per customer is a promise somebody eventually has to break.
- How do I leave?
- Export everything first: the CSV and the original media, free on every plan. Then destroy the project — every record and every file, with the confirmation being the project's name typed out, because none of it is recoverable. Canceling the subscription is separate and lives with the payment provider; the answer says so rather than letting you find out from a bank statement.
Privacy and access
Who can see what.
- Can you read my testimonials?
- An operator can open a dashboard, and the privacy page says so in plain words: we can, we do it to answer a request you made or a fault you reported, and not otherwise.
- Is my customer's email address ever public?
- No. An author's email address is in no public answer, from any endpoint, on any plan.
- Can I give somebody access without giving them my link?
- Yes — a seat has its own link and its own permissions, and revoking it revokes only that one. A seat cannot delete the project or add a paid extra to your subscription.
- Does the widget track my visitors?
- It counts views, plays and clicks per widget so you can tell whether anybody is reading them. There is no visitor profile and no cross-site identifier. Your page's visitors are not our product.
Not here?
Write to a person. There is no ticket number and no chatbot in front of it.
Each capability also has a page of its own, which ends with what it will not do: everything it does.
Still the fastest way to understand it
Open a project, send yourself the form link, and answer it as though you were your own customer.