Use cases

How different teams use Hearl, from solo founders to teams with support, community and product roles, plus AI agents.

Hearl is for teams whose users talk about the product in public on X, Reddit or Hacker News, and who want every post worth answering to have someone on it until it’s resolved. Here are the common setups, with what to configure for each.

Solo founders: don’t leave users’ questions hanging on X

The situation. You build the product alone, and users ask your official account directly: how fees work, how long review takes, why a payment failed. You don’t have time to keep refreshing notifications, and a late answer leaves a public complaint nobody responded to.

How to set it up.

1. Under Products & sources, enter your website. Hearl reads your official X account; tick “Track posts that mention these accounts”.
2. Open Notifications and connect email or your team chat. You hear about it when someone asks a question, and again when a user writes back after you replied.
3. Check the inbox’s Needs action view once a day. Only the posts that need a reply are left; praise, chatter and unrelated posts are sorted elsewhere.

What you get. Pricing and how-to questions are marked high priority and sorted to the top. Once you reply it becomes Team replied on its own, and if the user asks again it comes back to the inbox.

Products with a common name: only see posts that are really about you

The situation. Your product name is a common word, or shares a name with something else, so a plain keyword search is mostly noise.

How to set it up.

1. In What it is, say in a sentence or two what it does and who it’s for.
2. In Not to be confused with, list what shares the name, such as an unrelated product, a common word or a person.
3. Keep the search terms broad and let Hearl’s AI do the filtering. Posts it isn’t sure about go to the To review view as Needs a human check for a person to decide; nothing is dropped silently.

What you get. Posts that only share a word with your product name, or that match a similar spelling, are marked Not about the product and never reach Needs action. If one slips through, mark it irrelevant to close it. If the same kind of post keeps coming in, add it to Not to be confused with and later judgments will leave it out.

After a launch: pull bug reports out of the conversation

The situation. You just shipped a release. Your subreddit and X fill up with posts: praise, suggestions, and some people saying something broke.

How to set it up.

1. Add your subreddits under Reddit, plus site-wide search terms.
2. In the inbox, filter by Bug and Criticism, or show only High priority.
3. Assign each bug to an owner with a due date. When it’s fixed, write a one-line outcome and mark it done.

What you get. Among dozens of launch-day posts, bug reports are tagged as bugs with high priority and sorted to the top. Each problem has one owner, and the outcome stays on the timeline for later.

Teams with roles: support, community and product together

The situation. Community answers posts, technical questions go to engineers, pricing and partnership questions go to sales. Forwarding screenshots meant people often assumed someone else had replied.

How to set it up.

1. Invite teammates under Members. Each conversation has one owner; add collaborators when they need help.
2. Use the Unassigned view for daily triage and Overdue to follow up.
3. Write internal notes on a conversation (never posted publicly) and @mention teammates.

What you get. Every conversation shows who owns it, when it’s due and how it ended. When the team replies on the platform, Hearl sets the status to Team replied by itself; nobody has to sync it by hand.

Let an AI agent help: daily summaries and draft replies

The situation. You already use Claude, Cursor or your own scripts, and want them to read the inbox directly instead of you copying and pasting.

How to set it up.

1. Create a key under Agents & API: read-only to look, read-write to assign and write notes.
2. Connect over MCP, the hearl CLI or the REST API. All three expose the same operations.
3. Ask it in one sentence for this week’s summary, the posts to answer first and a draft reply saved as an internal note.

What you get. The agent reads the summary and inbox, picks the posts that need replies and saves the draft as a note for you to check and post yourself. Hearl never posts publicly, and every change an agent makes is recorded on the timeline as “you via agent”.

Your own community channels: bring in forums and Discord

The situation. Besides X, Reddit and Hacker News, your users also talk in your own forum, Discord or ticketing system.

How to set it up.

1. With a read-write key, push threads in batches with POST /api/v1/products/{slug}/threads.
2. Then call POST /api/v1/products/{slug}/judge so Hearl judges whether they’re relevant and need a reply.
3. Or run the ego collector on your own computer: it reads X and Reddit in a signed-in browser and pushes to the same inbox.

What you get. Conversations from every channel wait in one inbox and are handled with the same judgments, owners and statuses.

Next