Get ready for feedback.
Add the widget where you want feedback. Send one test comment and check it arrives in your project.
You need a project and access to your site’s code, script settings or tag manager. Whoever manages the site can help.
Create an account now. Finish setup later.
Create free account1. Copy your project’s snippet
Create a project for your site. Copy its generated installation code; each project needs its own snippet.
Copy the actual code from your project.
<script src="…" data-project="…"></script>The example shows the shape of a snippet. It is not working installation code.
2. Add it to your website
Place the complete snippet before the closing </body> tag, or add it through the custom-script or tag-manager setup your website uses. Publish the change on the pages where you want the widget to appear.
Keep your existing website. You need permission to add the script and settings that let it load.
Working with a developer? Send them the project’s snippet and this instruction:
Please add this Voicedot snippet to the website we are reviewing.
Website: [review URL]
Pages to include: [pages or the whole website]
Snippet: [paste the complete code from the Voicedot project]
After publishing, please check that the widget appears on those pages.
Do not change the rest of the website.3. Send one test comment
Open the site, pick a spot and type a comment. Send it, then find it with its page context in your project.
Start with text: it works on Free and does not require microphone access. Voice is included in the full 7-day trial and paid plans.
Once the test arrives, invite a client, user or teammate. Your test checks the setup. Their feedback starts the review.
Create an account now. Set up your site when ready. Your seven free days start when the first real feedback is successfully sent and saved in your project.
When the widget does not appear
When the widget does not appear
The published page
- What to do
- Make sure the deployed page contains the complete snippet.
The project and domain
- What to do
- Check that the project is active and the website address matches its configuration.
Script restrictions
- What to do
- Check whether your consent setup, content security policy or tag-manager conditions prevent the script from loading.
The browser
- What to do
- Check the console for errors and try a test without an aggressive content blocker.
| What to check | What to do |
|---|---|
| The published page | Make sure the deployed page contains the complete snippet. |
| The project and domain | Check that the project is active and the website address matches its configuration. |
| Script restrictions | Check whether your consent setup, content security policy or tag-manager conditions prevent the script from loading. |
| The browser | Check the console for errors and try a test without an aggressive content blocker. |
Microphone permission is only needed for voice. A reviewer can write instead.
Need help? Contact support with the website address, your browser and the step where you got stuck. Do not send passwords, access tokens or visitors’ private messages.