GmailEmail
Invoice export keeps crashing, and honestly the VAT return took three tries this quarter.
SignalScoop turns support conversations, reviews and calls into the bugs, requests and trends your product team should act on.
Every message has a story.
GmailEmail
Invoice export keeps crashing, and honestly the VAT return took three tries this quarter.
This is what you're here for.
Click on it.
app.signalscoop.app / overview
Signals this week
↑ 12%
Bugs
↑ 38%
Critical open
↑ 3
Positive
↓ 4 pts
Invoicing / Export: 3× more bugs since release 4.2
38 reports · 6 mention switching
VAT: cancellation mentions doubled this month
Mostly right after the return deadline
Bank feeds: compliments up 45%
Since auto-matching shipped
GmailEmail
Export to PDF crashes on invoices with more than 40 lines.
Invoicing / ExportBugnegativecritical
IntercomChat
Can I connect a second bank account to the same company?
Bank feedsQuestionneutrallow
AircallCall
Considering switching, the VAT return took three tries this quarter.
VATCancellationnegativehigh
GmailEmail
New dashboard is genuinely a joy, thank you.
DashboardComplimentpositivelow
Illustrative data · Messages become signals. Charts count signals.
Pick an example or paste your own, and see every signal SignalScoop finds.
Your signals land here.
Pick an example to start.
WHY NOT CHATGPT OR CLAUDE?
A chat model is a great engine. It is not a process. Here is what you end up building around it.
Also: pasting customer emails with names and addresses into a chat is often against company policy.
Try it yourselfSupport reads every message. Nobody counts them. The third report of the same bug looks exactly like the first.
By the time a complaint becomes a churn number, the release that caused it shipped six weeks ago.
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
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.
0 so far
Module
Your product's own structure
Type
Bug, question, wish, praise…
BugQuestionComplaintFeature request+3
Sentiment
Negative to positive
Source
Anything that arrives as text
CHANNELS
Email, chat, calls and reviews all become the same kind of signal, so one bug reported four ways shows up as one spike.
USE CASES
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.
Illustrative data
MODULES
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
We keep finding new ones as messages come in. Confirm one and it counts like any other module.
Types
Sentiment
Urgency
TAXONOMY
Seven types come with the account. Rename, drop or add your own, and do the same with the sentiment and urgency scales.
Edits apply to new signals only, so last quarter's charts stay put.
ONE INBOX FOR SIGNALS
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
4w8w12w
Signals
+12%
Bugs
+38%
Platforms
all live
Realtime alerts
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
Bug · urgency Critical
→ #incidents
Invoicing · type Complaint
→ POST /hooks/product-alerts
3
Delivered
Example Slack delivery
Destinations: Slack Webhook (any tool)
CLOSE THE LOOP · PLANNED
SignalScoop remembers who asked for what, in every channel. Mark a request as shipped and each of them gets a personal note. No spreadsheet, no digging through old tickets.
Same wish, different words, different tools. Counted as one request.
Export to Excel
Invoicing · feature request
✓ Marked as shipped
One click when it’s done. The list of people is already there.
3
To sam@customer.com
You asked for Excel export. It's live.
Invoices → Export → Excel. Thanks for asking.
✓ Sent to 37 customers
A short note to everyone who asked. They’re the ones most likely to use it.
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.app/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" }]
No native connectors to install. Route alerts to Slack, or to a webhook that reaches the rest of your tools.
Helpdesks, inboxes, call tools and review sites
Chat, automation and issue trackers
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.
Up to 1,000 messages / month
/ month
Free while in beta · no card needed
Up to 10,000 messages / month
/ month
Free while in beta · no card needed
Up to 50,000 messages / month
/ month
Free while in beta · no card needed
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.
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.
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.
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.
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.
Send your first messages today. Free while we're in beta, no card needed.