Products & sources
What Hearl collects for each product, the fields that guide filtering, and how often collection runs.
A product is one thing your team supports. Each product has its own sources, search terms and description. Your plan sets how many products a workspace can have.
Read from the website
Enter the product’s official website and choose Fill from website. Hearl reads the page and fills in:
- the product name and a short description
- official X accounts and Reddit communities linked from the site’s header and footer
- suggested search terms
Everything it fills in can be edited. If it can’t read the site, fill in the fields by hand.
Product fields
| Field | What it does |
|---|---|
| Product name | Shown in the inbox and in notifications. |
| ID | Used in links and the API. It can’t be changed later. |
| What it is | One or two sentences. Hearl’s AI uses it to tell real mentions from noise. |
| Not to be confused with | Things with the same name, such as a game engine function or a stock ticker, so Hearl’s AI can filter them out. |
| Search terms | One per line. Used for Reddit site-wide search and Hacker News search. |
Sources
X
- Official accounts. Posts from your accounts and the replies under them.
- Mentions. Turn on Track posts that mention these accounts to collect posts that mention your official accounts.
Ads and promotions are dropped. When a post is a reply, Hearl fetches the post it replied to, so a short reply like “Yes, it’s customizable” keeps its context.
- Subreddits. New posts in the communities you name.
- Search terms. Your search terms are run across Reddit. Posts from your own subreddits are skipped there, so nothing shows up twice.
- Team accounts on Reddit. The Reddit usernames your team posts from. Hearl reads the full comment tree and uses these accounts to tell when your team has replied.
Hacker News
Turn on Search Hacker News stories with the search terms above. Show HN, Ask HN and link posts all come in, and no API key is needed. Add your team’s HN usernames under Team accounts on Hacker News so their replies are marked.
Collection schedule
Collection runs in the cloud. How often it runs depends on your plan:
| Plan | Frequency |
|---|---|
| Free | Once a day |
| Team | Every hour |
| Scale | Every 15 minutes |
Each run looks for new posts and rechecks the threads it already has for new replies. A thread is followed for 7 days after it was posted. After that its status becomes No longer tracked.
Collect now
The Collection panel on the product page shows each source, the last run and what it found. Collect now starts a run right away. It can be used once every 10 minutes per product.
Monthly limit
Each plan includes a number of conversations a month. When a workspace reaches it, cloud collection pauses until the next month. Nothing is deleted, and you can still work on every conversation you have. See Billing & plans.