GmailEmail
Invoice export keeps crashing, and honestly the VAT return took three tries this quarter.
Turn customer messagesinto product insights.
SignalScoop turns support conversations, reviews and calls into the bugs, requests and trends your product team should act on.
Every message has a story.
This is what you're here for.
Click on it.
app.signalscoop.dev / overview
Signals this week
1,284↑ 12%
Bugs
312↑ 38%
Critical open
7↑ 3
Positive
62%↓ 4 pts
Which part of your product they talk about
Signals per week, per module · click a line to open its sub-modulesNeeds attention
Ranked by how fast it's growing- Send to Linear
Invoicing / Export: 3× more bugs since release 4.2
38 reports · 6 mention switching
Landing right now
Latest signals, live- GmailEmail
- IntercomChat
- AircallCall
- GmailEmail
Illustrative data · Messages become signals. Charts count signals.
Try it yourself. Throw any customer message at it.
Pick an example or paste your own, and see every signal SignalScoop finds.
Your signals land here.
Pick an example to start.
Your inbox knows what's wrong with your product. You don't.
It's buried
Support reads every message. Nobody counts them. The third report of the same bug looks exactly like the first.
It's late
By the time a complaint becomes a churn number, the release that caused it shipped six weeks ago.
It's flat
A ticket tool tells you volume. It doesn't tell you which module, whether it's a bug or a wish, or how people feel.
TRY IT
See what’s hiding in one message.
Four real-looking messages from four sources. Click one, watch it run through SignalScoop, and see every signal it pulls out. Each phrase gets the colour of its type.
Processing…
Signals per module
0 so far- Invoicing0
- Bank feeds0
- VAT0
- Reports0
- Dashboard0
Every signal gets five labels.
Module
Your product's own structure
Invoicing→ExportType
Bug, question, wish, praise…
BugQuestionComplaintFeature request+3Sentiment
Negative to positive
Urgency
Low to critical
Source
Anything that arrives as text
EmailChatCallReview
CHANNELS
Wherever customers talk, it counts.
Email, chat, calls and reviews all become the same kind of signal, so one bug reported four ways shows up as one spike.
Email
Forward support mail, or post each message from your helpdesk as it lands.
Gmail
Zendesk
Help Scout
HubSpot
Mailgun
Chat
Send every chat message; a thread id keeps a conversation together.
Intercom
Google Chat
Calls
Send the transcript when the call ends. Every statement in it counts.
Aircall
Reviews
Post public reviews as they appear, from Trustpilot in Europe to G2 in the US.
Trustpilot
G2
Google Reviews
App Store
Google Play
USE CASES
Four things product teams do with it.
See a bad release the day it ships, not six weeks later.
One line per module. When a release goes wrong, that line spikes across chat, email and calls at once, and an alert lands in Slack before the churn report does.
- Bug signals per module, per week
- Alert on: module = Invoicing, type = Bug, urgency ≥ High
- Every complaint keeps its original message
Illustrative data
MODULES
You don't set up modules. We find them.
We read your messages and name the parts of your product ourselves. Invoicing, Bank feeds, Invoicing / Export, whatever your customers keep bringing up. Nothing to set up first.
New ones show up as suggestions. Confirm them, rename them, or fold them into another. Anything that fits nowhere gets suggested as its own module, never dropped in an “other” pile.
Modules, found in your messages
- Invoicing218 signals
- Bank feeds154 signals
- VAT99 signals
- Reports74 signals
- Dashboard39 signals
- Onboardingsuggested11 signals
We keep finding new ones as messages come in. Confirm one and it counts like any other module.
Types
- Bug
- Question
- Complaint
- Wishrenamed
- Compliment
- Cancellation
- Other
- Regressionyours
Sentiment
- negative
- neutral
- positive
Urgency
- low
- medium
- high
- critical
TAXONOMY
Our labels are a start. Yours win.
Seven types come with the account: bug, question, complaint, feature request, compliment, cancellation, other. Rename the ones that don't match how your team talks. Drop the ones you never use. Add your own.
The sentiment and urgency scales work the same way. Add a step, rename one, reorder them.
An edit applies to what comes next. Signals we already classified keep the label they got, so last quarter's charts stay where you left them.
ONE INBOX FOR SIGNALS
Six tools report the bug. You see one spike.
Chat, email, calls and reviews live in separate tools, each with its own dashboard. SignalScoop counts them together, so the same bug reported in six places reads as one spike instead of six half-signals.
Every signal keeps its origin. Intercom chat, Gmail email, Aircall call.
One bug, one line. The export bug is 275 signals from six sources, drawn as one trend instead of six unrelated tickets.
Releases show up everywhere at once. When a release goes wrong, every platform spikes in the same week.
SOURCES
Cross-platform overview
4w8w12w
Signals
1,098
+12%
Bugs
275
+38%
Platforms
6
all live
Realtime alerts
Critical bugs go straight to Slack.
Write rules on any combination of module, type, sentiment and urgency. The planned alert flow sends matching signals straight to Slack or your webhook, with the original message and its context.
1
A signal lands
09:12:04 · email
“Export to PDF crashes on invoices with more than 40 lines. We can't send anything today.”
BugInvoicing / Exportcritical
2
Your rules run
every signal, instantly
Type is Cancellation
→ #customer-success
- match
Bug · urgency Critical
→ #incidents
Invoicing · type Complaint
→ POST /hooks/product-alerts
3
Delivered
Example Slack delivery
#incidents
I
SignalScoop APP · 09:12
🔴 Critical bug · Invoicing / Export
“Export to PDF crashes on invoices with more than 40 lines…”
3rd report this hour · sentiment negative · from sam@customer.com
Open messageAcknowledge
Destinations: Slack Webhook (any tool)
You send text to one endpoint.
Forward text from your helpdesk, chat widget, or call transcription through one API. Replies carry the same thread id, so a whole conversation is read as one and never double-counted.
POST https://api.signalscoop.dev/v1/messagesAuthorization: Bearer sk_live_… { "source": "email", "external_id": "msg_8812", "thread_id": "ticket_4410", "received_at": "2026-09-18T09:12:00Z", "from": "sam@customer.com", "body": "Export to PDF crashes on long invoices, but the new dashboard is a joy."}
202 Accepted { "message_id": "m_01J8…", "thread_id": "t_01J8…"} // seconds later, in your dashboard:[ { "module": "Invoicing", "sub_module": "Export", "type": "bug", "sentiment": "negative", "urgency": "critical" }, { "module": "Dashboard", "type": "compliment", "sentiment": "positive", "urgency": "low" }]
Anything that can send text works.
No native connectors to install. Route alerts to Slack, or to a webhook that reaches the rest of your tools.
Messages come from
Helpdesks, inboxes, call tools and review sites
- + anything with an API
Alerts go to
Chat, automation and issue trackers
- Slack
Zapier
Make
n8n
PagerDuty
Linear
Jira
Notion
Asana
ClickUp
Trello
Discord
GitHub
- + anything with an API
You pay for messages, not for features.
Choose by monthly message volume. Every planned tier includes all signal types, your own module structure, trend views, and alerts.
Pricing preview · SignalScoop is in development. Subscriptions are not open yet.
Starter
Up to 1,000 messages / month
€29/ month
- ✓ Every signal, classified automatically
- ✓ Module, type, sentiment & urgency
- ✓ Trend views and signal alerts
Free while in beta · no card needed
Growth
Up to 10,000 messages / month
€89/ month
- ✓ Every signal, classified automatically
- ✓ Module, type, sentiment & urgency
- ✓ Trend views and signal alerts
Free while in beta · no card needed
Scale
Up to 50,000 messages / month
€239/ month
- ✓ Every signal, classified automatically
- ✓ Module, type, sentiment & urgency
- ✓ Trend views and signal alerts
Free while in beta · no card needed
QUESTIONS
Things people ask before signing up.
Is this another shared inbox?
No. SignalScoop is an analytics layer for the customer messages you already receive. Keep replying in your existing tools; use SignalScoop to understand patterns across those messages.
What’s the difference between a message and a signal?
A message is one incoming text. A signal is one distinct statement inside it. ‘Export is broken, but the dashboard is great’ contains two signals: a bug in Invoicing and a compliment about Dashboard. Charts count signals; planned pricing is based on messages.
Do I need to use your product modules?
Your modules reflect your product. SignalScoop is designed to suggest a structure from your messages that you can refine, including sub-modules such as Invoicing / Export.
How do messages get into SignalScoop?
The API accepts text from your existing tools: emails, chat messages, call transcripts and public reviews (Google, App Store, Trustpilot, G2…). You’ll need to forward messages through the API; the tool logos don’t imply native, one-click connectors.
Can I use SignalScoop today?
Yes, in beta. Sign up, create an API key and send your first message. The interactive demos on this page use illustrative data; your dashboard shows your own. Alerts and paid plans are not available yet.
They already told you what to fix.
Send your first messages today. Free while we're in beta, no card needed.