The Usersnap widget is configurable from the header down to the disclaimer. You can add or remove any field, rewrite every label in your own words, set the primary color along with the field text, header and background colors, pick one of five positions and three sizes, and put your own logo in the header. Custom CSS is the one route it does not take.
The fields you pick decide what context arrives attached to every submission. Weeks later, when someone asks why a decision was made, that context is the answer.
Most of it. The Form tab controls the layout and the fields, the Style tab controls the design, and both update in a live preview before anything reaches your users.
Field configuration, copy and layout are available on every plan. Three things sit higher up:
If you are not sure which applies to your account, the customer success team can confirm it in one reply.
Two boundaries worth knowing before you plan a design around them. Usersnap does not support custom CSS styling on the widget, so the Style tab is the route rather than an override in your own stylesheet. And widget size selection does not apply to the mobile SDK. If your stylesheet is already interfering with how the widget renders, there is a separate guide for that.
A single submission can carry:
A report carrying all of that goes straight to someone reproducing the issue, instead of into a round of clarifying emails.
Each project routes into the tools your team already runs: Jira, Slack, Zendesk, Intercom, Salesforce, Microsoft Teams, Asana, GitHub, GitLab, Linear, Azure DevOps, Trello, Monday, ClickUp and HubSpot, and the rest through Zapier, webhooks, or the REST API.
You can connect several at once inside the same project, so one submission can open a Jira issue and post to a team channel at the same time. Setting a project to forward automatically is covered in the integrations guide.
Every item keeps a link back to the person and the session it came from. When an AI summary reports that customers are asking for something, you can open it and read the original comments sitting underneath, then quote them in the roadmap review.
Sentiment Sensor tags topic and sentiment as each item lands, so patterns surface without anyone sorting a backlog first, and the tag stays attached to the source rather than replacing it. A week of submissions gets reviewed in one pass in the Triage Inbox. Bulk status, label, assignment and reply actions run from the list view. Items promote onto the Opportunities Board carrying value and effort scoring, so prioritization starts from what the evidence supports rather than from who argued hardest.
From there the Hypothesis Generator and Solution Generator draft what to test next from the items actually collected. If a concept needs to be visual, Usersnap turns the evidence into a prototype prompt and hands it to Alloy, which generates the visual concepts. And through the MCP connector, ChatGPT, Claude or Cursor can query a live workspace and open an Opportunity directly.
Two in-app presets are worth switching on early if this is the part you care about: AI User Interview Analysis and AI Ingestion Product Discovery.
One snippet on your site, then the configuration happens in the dashboard rather than in code. Install options cover HTML, NPM, React, AngularJS, Blazor and single page apps, plus WordPress, Shopify and Google Tag Manager. Path targeting decides which URLs the widget appears on, so a single install can serve several projects. Most teams are collecting within minutes.
Content Snare, a content collection tool, walked through how they set theirs up:
Yes, and across most of the form. You can add or remove any field from the header to the disclaimer, including user email, assignee, checkboxes, poll options, rating scales and screenshots, add custom fields for anything else you need to ask, reorder every field, and write each question, label and placeholder in your own words. Design controls cover the primary, field text, header and background colors, the font, five widget positions, three widget sizes, and your own logo in the header.
Yes. The widget’s primary color, the field text color, and the header text and background colors are each set by HTML color code in the Style tab. Fonts are served through Google Fonts and can be switched off if you would rather not load them. Color, font and logo controls on widgets and surveys are gated, so contact the customer success team to have them enabled for your account.
Yes. The “Powered by Usersnap” link can be removed from the Company plan upward. On Premium and Enterprise, email correspondence can also be unbranded. Adding your own logo to the widget header is handled in the Configuration section, at a recommended size of 430x80px or larger.
Yes. Custom fields let you collect anything the standard form does not already ask for, such as a job role, a phone number, or consent to access an account. Adding the question to the widget saves a round of email after the report arrives. You can also pass data you already hold, like plan or account ID, straight from your app so the user never has to type it.
No. Usersnap does not support or recommend custom CSS styling of the widget. Design changes go through the Style tab instead, which covers colors, fonts, position, size, logo, and whether the widget blocks the page or floats. If an existing stylesheet is interfering with how the widget renders, there is a dedicated troubleshooting guide for CSS conflicts.
Yes, from the list view in both the feedback list and the inbox. Bulk actions cover delete, change status, assign, label, and mark read or unread. There are also bulk replies, where you select several items, write one message and send it to all of them at once, plus saved reply templates you can reuse.
Yes. Any team member, regardless of role, can add an item with the ‘+’ button on either the list or the Kanban view. The form matches whatever the project’s widget form is configured to collect, though the screenshot and screen recording buttons are not available on a manual entry. It then behaves like any other, so it can be labeled, prioritized and assigned, and whoever added it is recorded as the reporter.
Native integrations include Jira, Slack, Zendesk, Intercom, Salesforce, Microsoft Teams, Asana, GitHub, GitLab, Linear, Azure DevOps, Trello, Monday, ClickUp and HubSpot, with the rest reachable through Zapier, webhooks, or the REST API. Several can run inside one project at the same time, so a single submission can open an issue in a tracker and post to a team channel together.
Usersnap is GDPR compliant and data is processed and stored on AWS in eu-central-1 and Ireland. Customer data is never used to train AI models, and AI features can be disabled per account. For a security or procurement review, the privacy and security documentation covers data residency, processing and retention.
Every PM is being told to become an AI PM right now. Building got radically…
Imagine this: you're a Product Manager who has just shipped a feature you spent a…
Eighty percent of businesses believe they deliver a great customer experience. Eight percent of their…
Customer feedback analysis software turns scattered customer feedback (surveys, in-app messages, support tickets, reviews, and…
A voice of customer survey is the most direct way to hear what your customers…
If you are a product manager or SaaS founder, your hardest question isn't whether to…