It starts with your website
Paste your address on the home page. LiquidUser reads up to eight public pages of your site to work out what the product does, who it is for and which problems it solves. It follows your robots.txt.
Every claim it makes points back to the page it came from. If a line is wrong, correct it before the search starts, and the search uses your version.
- Product
- A shared inbox that collects customer feedback from Slack, email and support tools./
- Who it's for
- Product teams at software companies with 5 to 50 people./pricing
- Problems you solve
- Feedback is spread across tools and nobody reads all of it./features
- It is hard to tell which requests come from paying customers./features/tagging
Then it searches public conversations
LiquidUser looks through public conversations for people describing the problems you solve, even when they use different words from your website.
A result needs enough evidence to be shown. When there isn't enough, it stays out, and if nothing qualifies the scan tells you that instead of filling the page. Sometimes the useful answer is that we haven't found the right people yet.
You check the evidence
Each result shows the post it came from, a quote, how recent it is and a link to the original. Read the context and decide whether the match makes sense. A result is a starting point for your own judgment.
Looking for one place to keep feature requests
“We have feature requests in three places and I only find them when a customer leaves. Is there a tool that pulls them together?”
jmartin on Hacker News, in “Ask HN: How do you track feature requests?”
- Fit
- Strong fit
- Intent
- Active intent
- Evidence
- Some evidence
- Timing
- Now
Four signals instead of one score
Every result is described on four separate lines, in words, so you can see why it was ranked where it is.
- Fit
Whether the person matches your product and audience.
Strong fit · Some fit · Weak fit
- Intent
Whether they are dealing with the problem now, or actively trying to solve it.
Active intent · Evaluating · Has the problem · No current need
- Evidence
The source behind the result, and how directly it supports the conclusion.
Strong evidence · Some evidence · Limited evidence
- Timing
When it was said. An old need may not be a current one.
Now · Recent · Aging · Stale
You write the reply
Save a result, set it aside, or start a reply. The draft is based on what the person actually wrote. You review it and post it yourself. LiquidUser never sends anything for you.
The point is a useful conversation with someone who could benefit from what you make.
We had the same problem at 12 people. What helped was one inbox that every channel forwards into, then tagging each request with the account it came from. I'm building a tool for this and happy to share what we learned either way.
LiquidUser never sends anything for you. You decide what to say, and you post it yourself from your own account.
The scan is free and needs no account. See pricing