What Happy Morse does
Most product teams lose customer feedback in spreadsheets, support inboxes, and call notes. Happy Morse keeps every report, works out which reports describe the same problem, ranks those problems by how much business they affect, and brings you a short list of decisions instead of a long list of tickets.
- Step 1Feedback arrivesTyped in, imported from a CSV, pasted as a call transcript, or pulled from Intercom, Slack, and Notion.
- Step 2Each report is readHappy Morse works out the underlying problem, what the customer wants, how severe it is, and which product area it touches.
- Step 3Reports are groupedSimilar reports become one customer problem. Reports about work your team already tracks are filed against that work instead.
- Step 4You decideThe Decision Inbox shows what needs you, ranked by impact. You commit, choose Not now, or decline.
- Step 5Work goes outCommitted problems become briefs and PRDs, then tickets in Linear or Jira, or pages in Notion.
- Step 6The loop closesTicket status comes back into Happy Morse, and new reports after shipping bring the problem back to you.
The one idea to hold on to: you never have to sort, tag, or link anything by hand. Happy Morse does the filing and only asks you when it isn’t sure, or when something needs a human judgement call.
Sign up and invite access
Happy Morse is invite only. You can create an account first, but you need a valid invite code before you can create or open a workspace.
If you have an invite code
- Open the invitation link or sign upAn invitation link remembers the code for you. If you sign up normally, Happy Morse asks for the code after you verify your email.
- Check the codeCodes begin with
HM-. The code may already be filled in when you arrive from an invitation link. - Select ContinueA valid code unlocks onboarding. If a code has reached its usage limit, ask the person who invited you for a new one.
- Complete onboardingNew users are never sent straight into the workspace. Happy Morse first asks for the context it needs to make useful recommendations.
If you need an invite
Select Request an invite. Confirm the email address where you want to receive it, then add your name, company name, company website, and team size. Every request is reviewed by a person. Happy Morse aims to reply within 24 hours.
Already used Happy Morse? Choose Log in on the home page. While your session is active, the public-site button changes to Open workspace.
The four onboarding steps
| Step | What you provide | Why it is asked |
|---|---|---|
| Workspace | Workspace name, with optional company website, company size, and product type. | Creates the shared place that holds your team’s feedback, product work, and decisions. |
| Goals | Your role and at least one outcome you want from Happy Morse. | Keeps the product focused on the workflows that matter to you. |
| Feedback | Where feedback lives today, plus an optional first product area. | Helps you choose the right imports and integrations later. |
| First steps | Connect an integration now, or explore the workspace first. | Takes you to the most useful next action without locking you into it. |
Fields marked Required must be completed. If you choose Other or Something else, an extra field appears so you can describe it in your own words. Use Back to change an earlier answer before finishing setup.
Getting started
- Create your workspaceSign up, then name your workspace on the welcome screen. A workspace holds your feedback, problems, decisions, and connected tools. Everyone you invite shares it.
- Bring in what your team already tracksGo to Product Backlog and add your features, known bugs, backlog and roadmap items — by hand, from a CSV, or by connecting Linear or Jira. This stops Happy Morse from raising problems you are already working on.
- Add customer feedbackGo to Customer Feedback → Add feedback. Import a CSV of past feedback to get an immediate picture, or start with one report.
- Wait a momentEach report is analysed as it arrives, and grouping runs shortly after. The status line at the top of a screen reads Organizing new feedback… while this is happening and Up to date when it is finished.
- Open HomeCheck workspace setup, customer-demand trends, product coverage, and decision health. Home explains what data is still needed when an analytic is not ready yet.
- Review the Decision InboxWork through the questions top to bottom; the most important is first. When it is empty, nothing needs your judgement.
- Connect your toolsIn Integrations, connect Slack, Intercom, or Notion so feedback flows in without anyone copying and pasting, and connect Linear or Jira so approved work can leave Happy Morse as tickets.
How much feedback do you need? A problem reaches your Decision Inbox once its impact score clears about 30 out of 100, or it is growing, or a customer reported something critical. In practice that usually means two or more companies, or one large account with a severe problem. Fifteen to twenty reports is enough to see the grouping work properly.
Home and analytics
Home is the first place to look when you open a workspace. It shows what needs attention now and turns your customer evidence into a small set of readable product signals.
Finish the setup checklist first
- Add your product context — requiredConnect Linear or Jira, or add features, bugs, backlog items, and roadmap work manually or from a CSV. Happy Morse needs this before it can tell new demand from work you already know about.
- Connect feedback sources — optionalConnect Intercom, Slack, or Notion if you want new customer evidence to arrive automatically.
- Import your first feedback — requiredAdd one report, paste a conversation, upload a CSV, or import from a connected source.
The checklist disappears automatically after product context and customer feedback both exist. It does not leave behind a “setup complete” card.
The four summary numbers
| Number | What it means | What happens when you select it |
|---|---|---|
| Needs your decision | Questions currently waiting for human judgement. | Opens Decision Inbox. |
| Customer feedback | Reports in the workspace and the companies they came from. | Opens Customer Feedback. |
| Customer problems | Groups of reports describing the same underlying problem. | Opens Customer Problems. |
| Product work | Features, bugs, backlog, roadmap, and delivery work Happy Morse knows about. | Opens Product Backlog. |
What each chart answers
| Chart | The question it answers | How to use it |
|---|---|---|
| Customer-problem trends | Which leading problems are being reported by more or fewer companies over time? | Each point counts distinct companies in that interval. Select a problem in the legend to open it. |
| Problem-impact ranking | Which problems affect the most business? | Compare the impact bars, then select a problem to inspect its evidence and score. |
| Demand-to-plan coverage | Does customer demand have no linked work, sit in the backlog, have a plan, move in progress, or already show as shipped? | Select a segment to open the related problems or product work. |
| Decision flow and ageing | What did we commit to, postpone, or decline, and how long are decisions taking? | Use the counts with median time to decision, oldest undecided problem, and decisions needing review. |
| Post-ship demand | Are customers still reporting a problem after the related work was marked shipped? | Select an item to review the new reports and decide whether the work needs attention. |
Changing the date range
Open Date range above the charts and choose Today, Yesterday, Last 7 days, Last 28 days, Last 90 days, This year, All time, or a custom start and end date. The charts use evidence and decisions from that period. Product-work stages show their current state, so you can read historical demand against today’s plan. Empty charts explain which data is missing and link to the place where you can add it.
Decision Inbox
The Decision Inbox is a list of decisions, not a list of tasks. Each card describes one thing that needs a judgement, explains why it is being raised, shows the customer evidence behind it, and offers the action Happy Morse recommends.
The heading tells you how many decisions are waiting. When there is nothing left, you see You’re done for now — that is the expected state most days, and it means nothing is being hidden from you.
How review works
Every card starts with only the question, a short factual summary, and Review. Opening it reveals:
- Happy Morse’s view: what it makes of those facts. Where it made a judgement call, a note says whether it is Confident, Not certain, or Unsure. Cards built from plain facts — a growing problem, a cancelled ticket — carry no note, because there is nothing to be unsure about.
- Key evidence: companies, ARR, report counts, dates, and the state of any related work.
- A customer quote — the strongest one, chosen by account size, severity, and recency.
- An expandable explanation (for example Why Happy Morse matched these), with More detail inside it when there is more to read.
- A visual source → action → destination flow shows the exact data change without making you parse a paragraph.
- One contextual action whose label names the result, such as Create problem, Add to “Export scheduling”, or Review Linear update. There is no generic Approve button.
Nothing changes when you click Review. It only opens the evidence and consequence. A separate, explicitly named button performs the action.
The three kinds of question
Whatever the badge says, every card is one of three things — and you can filter by them:
| Kind of question | It asks | Examples |
|---|---|---|
| Product decisions | What should we do about this problem? | New problem, growing problem, a Not now decision coming back, work the team cancelled, an urgent report |
| Where evidence belongs | Where does this customer report belong? | Possible match, possible duplicate, a report that may not fit, reports that couldn’t be placed |
| Work needing attention | Does work we already track need attention? | Customer demand on backlog work, demand out of step with the plan, problems still reported after shipping |
The outcome shown after Review
| Situation | Contextual action | Result |
|---|---|---|
| New or growing problem | Review problem | Opens the problem workspace, where you can Commit, Not now, or Decline. |
| Urgent report | Create problem | Creates a problem with the report as its first evidence. |
| Possible match | Add to “problem” or Add demand to ticket ID | Files the report in the named destination. |
| Possible duplicate | Merge into “problem” | Moves the evidence into the named problem after confirmation. |
| Report may not fit | Remove from “problem” | Removes the report from the named problem so it can be re-filed. |
| Customer demand | Review Linear update or Review work item | Shows the exact external comment before confirmation, or opens the internal work item. |
| Decision needs review | Review decision | Opens the existing problem and its recorded decision. |
The other controls
- Keep separate, Not now, Leave ungrouped, or Keep current decision names the relevant alternative without applying the proposed change.
- Supporting information opens the evidence, source ticket, or related work. These controls never make the decision.
- Reversible filing changes offer Undo immediately. Merges and writes to an external tool ask for confirmation first.
Nothing leaves Happy Morse without your say-so. External posts and irreversible combinations show a second confirmation after you choose the contextual action.
Search and filter
Search the inbox by problem, customer, or work item. Kind of question narrows it to product decisions, evidence questions, or work needing attention. The counter on the right shows how many of the total are visible.
Customer Problems
A customer problem is a group of reports that describe the same underlying thing. This section holds all of them — including the smaller ones that never reach the Decision Inbox.
The list
Two tabs: Open (no decision yet) and Decided. Each row shows:
- Problem — the title and a one-line headline, plus a chip such as Linear: In progress once work exists.
- Impact — the score from 0 to 100, with an arrow if the problem is growing.
- Customers — how many companies reported it, and their combined ARR.
- Status — Watching, Needs a decision, Committed, Not now, Declined, or Decision revisit.
Search by problem, customer, or requested outcome, and filter by trend (New, Growing, Steady, Cooling).
The problem page
Opening a problem gives you a one-page brief. From the top:
| Part of the page | What it tells you |
|---|---|
| Commit · Not now · Decline | The decision bar. Always visible at the top, because deciding is the point of the page. After you decide, it becomes Change decision. |
| Headline and problem statement | What customers are struggling with, in one or two sentences. |
| Delivery | Where the work stands in Linear or Jira: Not started, In progress, Done, or Cancelled, with a link to the ticket and how many child tickets are finished. |
| Why now | The reasons this deserves attention today — growing, new, quiet, a critical report, a gap between customer demand and the team’s plan, or a revisit condition you set. “Why is this ranked here?” opens the impact breakdown. |
| What customers said | One quote per company, strongest first: biggest ARR, then most severe, then most recent. “See all N reports” shows every one. |
| Linked Product Backlog items | Work your team already tracks that these customers are asking about, with the option to share the evidence to Linear. |
| Decision | Once decided: what you chose, who decided, when, why, and any revisit condition. |
| Documents | Briefs, PRDs and other documents written for this problem. |
| Send to your team’s tools | Appears after you commit. Creates tickets in Linear or Jira, or a page in Notion. |
Making a decision
| Choice | What happens |
|---|---|
| Commit | The decision is recorded with today’s evidence and a problem brief is drafted for you. A note for the team is optional. You can then send the work to Linear, Jira, or Notion. |
| Not now | A reason is required, and Happy Morse suggests a condition for bringing it back — for example when 5 companies have reported it. Leave the checkbox ticked and the problem returns to your Decision Inbox by itself when that happens. |
| Decline | A reason is required. It is saved to Decision History so the same idea does not quietly come back without new evidence. |
For Not now and Decline there are one-click reasons (“Not a priority this quarter”, “Not our product direction”, and so on) you can use as-is or edit. Every decision can be changed later with Change decision; the earlier decision stays in Decision History.
Fixing a problem that isn’t quite right
- Manage report (next to a quote) moves that single report to another problem, marks it as a separate problem, or takes it out of this one.
- Merge with another problem (top right) combines this problem into another. Reports, linked work, and documents move across; past decisions stay in Decision History. It asks once, because it cannot be undone in a single step.
You rarely need either. Happy Morse raises duplicates and misplaced reports in the Decision Inbox on its own — these menus are there for the cases it misses.
Impact score and trend
The impact score is a single number from 0 to 100 that answers “how much business does this problem affect?”, so problems can be compared with each other. It is built from four things:
| Ingredient | Weight | What it measures |
|---|---|---|
| Reach | 35% | How many different companies reported it. Two companies count for much more than two reports from one company. |
| Revenue | 30% | The combined ARR of those companies, where you have provided ARR. |
| Severity | 20% | The most severe or most urgent report in the group. |
| Recency | 15% | How recently it was last reported. Old, quiet problems fade rather than disappear. |
The result is then adjusted for the trend: growing problems are lifted, new ones slightly lifted, quiet ones reduced. Why is this ranked here? on the problem page spells out the exact numbers used, including the split across customer segments.
| Trend | Meaning |
|---|---|
| New | First reported in the last 14 days. |
| Growing | Clearly more reports in the last 14 days than in the 14 days before. |
| Steady | Coming in at a similar rate. |
| Quiet | No new report for more than 45 days. |
ARR makes a real difference. Include an ARR column when you import feedback, or connect a tool that carries it. Without it, the revenue part of the score is zero for those companies and large accounts look the same as small ones.
Customer Feedback
Every report ever added, exactly as the customer said it, with Happy Morse’s reading beside it. Nothing here is ever rewritten or summarised away.
Adding feedback
＋ Add feedback opens a dialog with three tabs.
Manual entry
One report. Customer, company, source, and date are required; ARR, segment, plan, and internal notes are optional but make the ranking sharper.
CSV upload
A file of past feedback. You map your columns to Happy Morse’s fields before anything is imported.
Conversation or call
Paste a transcript or meeting notes. It is split into one report per problem the customer raised, each linked back to the conversation.
CSV columns
The first row must contain column names. Happy Morse guesses the mapping from your headers; you can change any of them, and Do not import ignores a column.
| Field | Required | Notes |
|---|---|---|
| Feedback text | Yes | The customer’s own words. |
| Customer name | Yes | The person who said it. |
| Company/account | Yes | Used to count how many companies are affected — the biggest part of the impact score. |
| Source | Yes | Call, email, survey, support ticket… anything you like. It becomes a filter. |
| Date | Yes | When the customer said it. Drives recency and trend. |
| ARR (number) | No | Accepts 120000, $120k, or 1.2M. |
| Segment | No | Enterprise, Mid-market, SMB… used in the impact breakdown and in revisit conditions. |
| Plan | No | Their pricing plan. |
| ARR/customer value | No | Free text, for when you have a description rather than a number. |
| Notes | No | Internal context. Kept separate from the customer’s words. |
| External source ID | No | The ID in the system this came from, so re-importing updates instead of duplicating. Every row must have a different value, or the import is refused. |
After importing, the dialog tells you how many rows were accepted and shows the row numbers of any that were rejected, so you can fix those rows and import them again.
The list
Each row shows the customer, company, date, the report itself, the source, and either the product area Happy Morse assigned or the processing status. A ↗ tag shows the problem or work item the report was filed against.
- Filters: search, status (Processed, Processing, Needs attention, Stopped), and source.
- Select all / Select checkboxes allow bulk actions on the reports currently visible.
- Delete selected removes reports from active evidence. Past decisions and saved documents keep what they recorded, and an Undo link appears for a few seconds.
- Stop processing stops analysis for items still being worked on. You can restart it later from the report.
A single report
| Block | What it shows |
|---|---|
| Customer context | Company, ARR, segment, and source. |
| Customer report | The full text, any internal note, the source, the date, and how it was added. |
| Happy Morse analysis | Whether it is product relevant, the type of feedback, sentiment, severity, urgency, product area, the underlying problem, and the outcome the customer wants. |
| Where this report lives | The problem or backlog item it was filed under, any earlier decision that applies to it, and a menu to change the filing. |
Reports that are not product relevant (a scheduling message, a thank-you note) are kept but never grouped or counted. If analysis fails or is stopped, the page says so and offers Retry analysis or Restart analysis.
Product Backlog
Everything your team already knows about: features you ship, bugs you know about, backlog and roadmap items, and work in flight. Its job is to stop Happy Morse from presenting you with problems you are already solving — a report that matches known work is filed against that work instead of becoming a new problem.
| Type | Use it for |
|---|---|
| Product Area | A part of your product (Billing, Reporting). Other items can sit under one. |
| Feature | Something that already exists. |
| Known Bug | A defect your team has already recorded. |
| Backlog Item | Something agreed but not scheduled. |
| Roadmap Item | Something planned for a period ahead. |
| Existing Work | Work currently under way. |
| Product Strategy | Direction and principles, used as background when documents are written. |
Adding work
＋ Add work offers manual entry or CSV import (Type, Title and Description are required; status, product area, source, external ID, URL and dates are optional). Connecting Linearor Jira fills this section automatically and keeps statuses current, which is the easier route if you use either.
The list and a work item
Work customers are actually asking about is sorted to the top. Each row shows its type, status, how many customer reports and companies are behind it, the combined ARR, and when it was last mentioned. The summary above the list counts your work items, how many have customer demand, and how many reports have been filed against them.
Opening an item shows the customer demand behind it, the planning information from Linear or Jira (priority, cycle or sprint, estimate), and a link to the original ticket. From here you can:
- Share evidence to Linear — posts a summary of the customer reports as a comment on the issue, after you confirm. If evidence has changed since last time, the button becomes Update evidence in Linear.
- See a warning when reports arrived after the work was marked done — a possible regression, or a fix that did not cover what customers needed.
“Searchable” on a work item means Happy Morse has finished indexing it and can match new customer reports against it. Until then it shows as Pending indexing — it usually takes seconds.
Documents
Committing to a problem drafts a problem brief automatically. From the Documents block on the problem page you can draft more: a PRD, User Stories, Acceptance Criteria, or a Bug Report. They are written from the actual customer evidence and your product backlog, not from a blank page.
| Control | What it does |
|---|---|
| Edit / Save revision | Edit the text yourself. Each save becomes a new version. |
| Revise with AI | Describe the change you want (“add a rollout plan”, “make the scope smaller”) and the document is rewritten as a new version. |
| Approve | Marks the document as final. Only approved documents can be sent to Linear, Jira, or Notion. |
| Version history | Every version, who made it, when, and whether it was AI-generated, an AI revision, or your own edit. |
| Export PDF / Markdown / DOCX | Downloads the document with its evidence list for sharing outside Happy Morse. |
Citations
Small numbered chips in the text are citations. Click one to see the exact report, work item, or decision it came from, and Open in Customer Feedback to read the whole report. The evidence list at the foot of the document names every source used, so anyone reading the brief can check the claims.
Sending work to your tools
Once a problem is committed (or a document approved), Send to your team’s tools appears. You always see exactly what will be created before anything leaves Happy Morse.
- Choose a toolOnly connected tools are offered. Linear and Jira create tickets; Notion publishes a page.
- Review the planHappy Morse proposes a parent ticket (an epic in Jira) and child tickets, with a suggested priority and the reason for it. Edit any title, and untick any child ticket you do not want.
- Pick the destinationA Linear team and optional project, a Jira project, or the Notion page to publish under.
- CreateThe button names exactly what will happen, for example Create 4 tickets in Linear. The count changes as you tick and untick tickets, and it ignores anything already created.
- Check the resultYou get a link to each ticket. Anything that failed can be retried by sending again — existing tickets are never duplicated.
Every ticket carries the customer evidence and a link back to the problem in Happy Morse, so whoever picks up the work can see who asked for it and why. Open questions from the document are added to the parent ticket.
Status comes back
Once work exists, the problem page shows a Delivery block and the problem list shows a chip:
| State | Meaning |
|---|---|
| Not started | The tickets exist but nobody has picked them up. |
| In progress | At least one ticket is being worked on. |
| Done | The work shipped. New reports about it will come back to you as “Still reported after shipping”. |
| Cancelled | The team stopped the work. Customers who reported the problem are still waiting, so this also appears in your Decision Inbox as a card. |
Linear sends changes to Happy Morse as they happen. Jira does the same when its card says Live updates on, and otherwise syncs every hour. Sync now on the integration card fetches the latest at any time.
Decision History
Every decision, with the problem, what you chose, the date, who decided, the reason, and a snapshot of the evidence at the time — how many reports and how many companies. This is the answer to “why didn’t we build that?” six months later.
- Reconsider if… shows the condition you set when you chose Not now.
- Needs another look marks decisions whose condition has now been met. The banner at the top links straight to your Decision Inbox, where the revisit card is waiting.
- If a problem was later combined into another, the row says which one, and the link takes you there.
- Filter by decision and by review state, or search the problem, reason, or decision maker.
Integrations
Integrations lists every tool. Choose one to see its status, its settings, and the actions available. Connecting goes through the tool’s own permission screen — Happy Morse never asks you for a password.
| Tool | What it brings in | What it sends out |
|---|---|---|
| Intercom | Closed conversations, split into one report per problem the customer raised. | — |
| Slack | Messages from the channels you choose become customer feedback. | A weekly digest of decisions, posted Monday morning to a channel you pick. |
| Notion | Interview notes from a page you choose, imported as feedback. | Approved briefs and PRDs, published as pages. |
| Linear | Issues, their status and planning data, into Product Backlog. | Tickets from approved work, and customer evidence as comments. |
| Jira | Issues from the projects you choose, into Product Backlog. | An epic with child tickets from approved work. |
Zendesk, Gong, and GitHub are shown as Coming later and cannot be connected yet.
What each card shows
- Connected / Not connected / Reconnect required — the connection state. Reconnect required means the tool withdrew permission; click Connect again.
- Workspace and last sync — which account is linked and when data last came in.
- Sync now — pulls immediately instead of waiting for the hourly run.
- Disconnect — stops future syncing and sending. It asks first and tells you exactly what stops. Data already imported stays.
Only a workspace admin can connect or disconnect tools. Everyone else sees the status and can trigger a sync, with a note asking an admin to make the connection.
Per-tool settings
Slack
Tick the feedback channels Happy Morse should read (for example #customer-feedback), and choose a channel for the weekly digest or turn it off. Save, then invite Happy Morse to any channel it is not yet a member of by typing /invite @Happy Morse there — the card tells you which channels need it. Send digest now posts a digest immediately, which is handy for checking the setup. Messages that are not about your product are ignored.
Notion
Happy Morse only sees pages you share with it: in Notion, open a page → ••• → Connections→ add Happy Morse. Then choose which page documents are published under (or Ask each time), and use Import interview notes to bring a notes page in as feedback, naming who was interviewed and their company.
Jira
Tick the projects to sync (leave all unticked to sync everything) and save. The card says Live updates on when changes in Jira reach Happy Morse within about a minute; otherwise it syncs hourly.
Linear
After connecting, use Sync now for the first import. The card reports how many issues were found, created, updated, and made searchable. If the import fails, the connection itself is unaffected — try Sync now again.
Intercom
Closed conversations import continuously; the card shows how many conversations and feedback items have come in.
If a connection fails
| Message | What to do |
|---|---|
| Connection cancelled. Nothing changed. | You (or someone) pressed cancel on the tool’s permission screen. Click Connect again. |
| You weren’t signed in when … sent you back. | Open Happy Morse at the same web address your admin configured, sign in there, and connect again. |
| That connection link expired or was already used. | Connection links are single-use and short-lived. Click Connect again. |
| Only a workspace admin can connect … | Ask an admin to make the connection. |
| … couldn’t be connected. Check the settings. | The tool’s credentials on the server need attention — ask your admin. |
Guided walkthroughs
Walkthroughs teach you inside your real workspace. They open the section you selected, highlight the actual controls on screen, and explain what each control does without changing your data.
- Open WalkthroughChoose Walkthrough in the workspace sidebar.
- Choose a sectionHome, Decision Inbox, Customer Feedback, Customer Problems, Product Backlog, Decision History, and Integrations each have their own tour.
- Follow the spotlightThe selected section opens and the current area is highlighted. Use Next and Back to move through the controls.
- Finish or leaveSelect Finish at the last step, or use × at any time. The tour does not mark itself permanently complete.
You can replay every walkthrough. They work for new and existing users and can be started as many times as you need. A walkthrough only explains the screen; it never creates, edits, sends, or deletes anything.
Everyday routines
Monday morning (10 minutes)
- Open the Decision Inbox and work top to bottom.
- Commit, choose Not now, or decline the problems; merge or keep separate the duplicates and misplaced reports.
- For committed problems, review the drafted brief and send the tickets to Linear or Jira.
- Stop when you reach You’re done for now.
After a customer call
Customer Feedback → Add feedback → Conversation or call, paste the transcript, and add the customer and company. It is split into separate reports and joins the right problems by itself. If it is urgent, it will appear in your Decision Inbox as a critical report.
Planning a cycle
Open Product Backlog, sorted so work with customer demand sits at the top, and look for cards badged Customers rank this higher than the team in your inbox. Use Review Linear update to preview the exact evidence comment before putting it in front of the team.
Answering “why didn’t we build this?”
Search Decision History for the problem. You get the decision, the reason, who made it, and the evidence available at the time.
What the labels mean
| Label | Meaning |
|---|---|
| Watching | A problem Happy Morse is tracking that has not yet earned a decision — usually one company, or low impact. |
| Needs a decision | It has crossed the threshold and is in your Decision Inbox. |
| Decision revisit | A Not now problem whose revisit condition has been met. |
| Committed / Not now / Declined | Your recorded product decision. |
| Merged | Combined into another problem. |
| Product relevant | The report says something about your product. Reports that are not are kept but never counted. |
| Severity / Urgency | How bad it is for the customer, and how soon they need it. Both come from the report itself. |
| Processed / Processing / Needs attention / Stopped | Where a report is in analysis. “Needs attention” retries by itself; “Stopped” is a report you paused. |
| Searchable | Indexed, so new reports can be matched against it. |
| Draft / Approved | A document’s state. Only approved documents can be sent to your tools. |
| Up to date / Organizing new feedback… | Whether grouping has caught up with everything you have added. |
FAQs and troubleshooting
Short answers to the questions users most often have while joining, setting up, and running a workspace.
Why do I see Log in instead of Open workspace?
Open workspace appears on the public site only while you are signed in. Choose Log in with the account you used before. After authentication, Happy Morse opens your existing workspace or asks you to activate it.
My invite code does not work.
Check that the code begins with HM- and contains the complete set of letters and numbers. Invite codes can have a usage limit. If the code is valid but has no uses left, ask the person who sent it for another code. If you do not have one, choose Request an invite.
Can I skip onboarding?
No. A new user completes the four short onboarding steps before entering the workspace. The answers give Happy Morse enough context to guide setup. Optional fields are clearly marked and can be left blank.
Why is the setup checklist still visible?
The checklist remains on Home until the workspace has both product context and customer feedback. Add product context first through Linear, Jira, manual entry, or CSV; then import at least one feedback item. It disappears automatically when both required steps are complete.
Why did an analytics chart change when I changed the date range?
The date filter limits customer evidence and decisions to the selected period. Product-work stages still show their current state. This lets you answer questions such as “What were customers reporting last month, and where does that work sit today?” Choose All time to remove the date limit.
Can a walkthrough change my workspace?
No. A walkthrough only opens a real section, highlights controls, and explains them. You can exit and replay it at any time. Your data changes only if you deliberately use a product control after leaving the walkthrough.
I added feedback but no problems appeared.
Two common reasons. First, grouping runs shortly after analysis finishes — the status line says Organizing new feedback… while it is working.
Second, small problems stay out of the Decision Inbox until they matter: it takes an impact score of roughly 30, a growing trend, or a critical report. Check Customer Problems, where every problem appears including the quiet ones, and open a report to see where it was filed — it may have been matched to something in your Product Backlog instead.
A report was filed under the wrong problem.
Open the report and use Change where this report is filed, or use Manage report next to its quote on the problem page. You can move it to another problem, track it as its own problem, or take it out so Happy Morse re-files it.
Two problems are really the same thing.
Happy Morse usually spots this and offers Combine problems in your Decision Inbox. If it hasn’t, open either problem and use Merge with another problem. Reports, linked work, and documents move across; past decisions stay in Decision History.
My CSV import was rejected.
Check that Feedback text, Customer name, Company, Source, and Date are all mapped, and that the first row of the file contains column names.
If you mapped External source ID, every row needs a different value in that column — set it to Do not import if your file does not have one. The error message names the repeated values and the rows at fault.
“N items couldn’t be processed.”
Happy Morse retries on its own, and Retry now pushes it immediately. If the message mentions setup or a model, your workspace admin needs to finish configuring the AI service; everything queued resumes once they have.
I hid a card by mistake.
An Undo link appears in the message at the top of the Decision Inbox for a few seconds. After that, the problem is still in Customer Problems and the card returns on its own when the evidence changes.
I deleted feedback I needed.
Use Undo in the message that appears after deleting. Deleting only removes a report from active evidence — decisions and documents keep what they recorded at the time.
Sending to Linear or Jira failed.
The dialog shows the tool’s own explanation of what went wrong (for example a team that no longer exists). Fix that, then send again — tickets already created are never duplicated, and only the failed ones are retried.
Slack messages aren’t showing up.
Messages become Customer Feedback, not backlog items. Check that the channel is ticked in the Slack card, that Happy Morse has been invited to it in Slack, and remember that messages unrelated to your product are ignored on purpose.
Nothing is in my Decision Inbox.
That is the normal, healthy state. Nothing is hidden: new problems, growing problems, duplicates, and anything Happy Morse is unsure about all appear here as they arrive. Browse Customer Problems if you want to look ahead.
What can Happy Morse send to another tool?
Happy Morse can create delivery tickets in Linear or Jira, publish approved documents to Notion, post customer-demand evidence to Linear, and post a Slack digest when you configure one. It shows the destination and asks for confirmation before an external write. Importing, analysing, reviewing, or making an internal product decision does not send anything outside Happy Morse.
Where can I get help?
Email radio@happymorse.com. Include the workspace name, the section you were using, what you expected to happen, and the exact message shown on screen. Do not send passwords or private access tokens.