Welcome to UserGist
Learn what UserGist does, choose your first tool, and start with one useful customer interaction.
Last updated 9 September 2026
On this page
UserGist helps you hear from customers and keep them informed. Collect feedback inside your product, ask follow-up questions, share updates, and give customers a place to suggest what comes next.
Choose what you want to do first
Feedback: Ask one quick question, such as how easy it was to complete a task.
Surveys: Ask a series of questions when you need more context.
In-app messages: Introduce a feature or offer a useful next step while someone is using your product.
Push notifications: Bring customers back to a useful place in your iOS or Android app.
Customer Portal: Bring feature requests, your roadmap, release notes, and help articles together.
Start with one useful moment
You do not need to use every tool at once. Pick one thing you want to learn or improve. For example, after a customer downloads a route, ask: “How easy was it to save your route offline?”
In Feedback, choose New feedback, then Add question. Write your question, pick a response type, and check the live preview beside it. The example above uses a five-star rating.
Choose the right app. Keep the content and customer context connected to the product you are working on.
Prepare your first question or message. Use a clear title and explain what you want the customer to do.
Review the experience. Check the wording, appearance, audience, and timing before making it active.
Learn from the response. Read the answers or review the available results before deciding what to change next.
A few things to know
Your website or mobile app needs a UserGist SDK connection to collect events and responses and show in-product experiences. A developer can follow the setup guide for your platform.
Customers can respond anonymously or as identified users. What UserGist knows about a person depends on the information your app sends and the consent settings it uses.
A draft is work in progress. Publishing content or activating an experience is a separate step. Native push also requires notification permission and configured iOS or Android credentials.
Keep customers in the loop
When you act on a request, update its progress on your roadmap. When the work ships, explain what changed in your changelog and add a help article if customers need guidance.
Start small: one useful question, one clear update, and one next step based on what you learn.
Choose your next step
Connect your app and verify the first activity