How to Use TellTide: From Feedback Widget to Public Roadmap

Step 1: Create your first app

In TellTide, an app represents the product or site receiving feedback. Open Apps, choose New app, and enter a name, platform, short description, and the public app link where the widget will run.

After creation, copy the private server key only if you need trusted backend API access. The widget obtains its submission-only publishable key automatically and validates the configured website origin.

Step 2: Choose feedback types and design the widget

Open Manage Widget for the app. Enable the categories your team is prepared to handle: Review, General feedback, Bug report, and Feature request. You need at least one.

Then match the launcher to your product. Set the colors, label, panel title, position, fonts, behavior, and mobile or desktop visibility. The live preview is for design only and does not create real inbox feedback. Click Save before you copy the embed code.

Step 3: Install the widget and send a test

Copy the snippet from the Embed section and place it on the website that matches the app link. Standard websites can add it before the closing body tag. Next.js and single-page apps can use the dedicated integration guides.

Open the site, click the launcher, and send a clearly labeled test submission. Then open Feedbacks in TellTide. The new row should appear within seconds. This one test confirms the App ID, registered hostname, saved design, and inbox path are working together.

Step 4: Review and manage the feedback inbox

The inbox can show all submissions or filter by app, type, status, and search. Open a row to see the complete message, submitter, rating, page context, and structured bug or feature fields.

Give the item a useful status such as open, in progress, resolved, closed, or declined. A short, consistent status workflow helps the team see what needs attention without creating another backlog system.

Step 5: Publish selected ideas to the public roadmap

Not every submission belongs in public. Review feature requests privately first, remove sensitive context, and clarify the customer problem. When an item is ready, show it on the roadmap and choose its roadmap stage.

Share the public roadmap URL with customers so they can vote, comment, and follow progress. Keep statuses current. The roadmap is most useful when it reflects real decisions rather than every idea the team has received.

Verify the setup before inviting customers

Run one test for every enabled feedback type on the registered website. Confirm that the launcher is readable on mobile and desktop, each submission reaches the correct app, page context is present, and no private test data appears on the public roadmap. Ask a teammate who did not configure the widget to complete the test; unfamiliar users often reveal unclear labels or missing instructions.

If the launcher does not appear, first confirm that the embed code is present on the rendered page and that the current hostname matches the app link. If a submission does not reach the inbox, verify the App ID, saved widget settings, and browser console before changing several settings at once.

Your first-week operating checklist

• Assign an owner to review new inbox items each working day.
• Agree on the meaning of open, in progress, resolved, closed, and declined.
• Respond to test submissions so the team practices the complete loop.
• Publish only one well-understood feature request to learn the roadmap workflow.
• Add the public roadmap link where customers can find it.
• Review widget completion and message quality before adding more required fields.

Once the loop works end to end, expand gradually. Reliable review and follow-up matter more than enabling every category on the first day.

Put this into practice: Start using TellTide