| name | sales-noisely |
| description | Noisely (noise.ly) platform help — AI feedback-tracking & product-intelligence tool that aggregates customer feedback from 23+ sources (reviews, app stores, Reddit/HN/GitHub, Zendesk/Intercom, CSV), auto-categorizes into 12 types, scores sentiment + urgency/impact, clusters similar mentions into ranked 'action items', and spike-detects. Pushes to 10 channels (Slack, Linear, Jira, Notion, Google Sheets, Email, Webhooks…). No public REST API documented — the developer surface is outbound webhooks + native integrations + CSV; AI analyses are a monthly credit limit. Use when wiring action-items or spike alerts to your tools via webhook, choosing which sources to monitor, clustering/deduping feedback, reading sentiment or urgency, exporting to a sheet/ticket, or picking Try vs Pro vs Custom. Do NOT use for survey/VoC program strategy across tools (use /sales-customer-feedback), public review collection (use /sales-customer-reviews), or broad brand/social listening (use /sales-social-listening). |
| argument-hint | [describe what you need help with in Noisely] |
| license | MIT |
| version | 1.0.0 |
| tags | ["sales","customer-feedback","voice-of-customer","platform"] |
Noisely Platform Help
Step 1 — Gather context
If references/learnings.md exists, read it first for accumulated platform knowledge.
-
What are you trying to do?
- A) Push action items / spike alerts to your tools (Slack, Linear, Jira, webhook…)
- B) Pick which of the 23+ sources to monitor (reviews, social/dev communities, support)
- C) Understand the AI output — categories, sentiment, urgency/impact, clustered action items
- D) Export feedback to a sheet/BI, or import your own via CSV
- E) Tune signal — brand-ambiguity filters, dedupe, spike thresholds
- F) Decide Try ($29 one-time) vs Pro ($49/mo) vs Custom, or budget the analysis credits
-
Code or no-code? Custom routing → outbound webhook. Otherwise use the native channels (Linear/Jira/Slack/Sheets) — no endpoint to host.
Skip-ahead rule: if the user's prompt already provides enough context, skip to Step 2.
Step 2 — Route or answer directly
| If the question is about... | Route to... |
|---|
| Survey / VoC program strategy (NPS/CSAT/CES design) across tools | /sales-customer-feedback {question} |
| Collecting public reviews (Trustpilot/G2 generation) strategy | /sales-customer-reviews {question} |
| Broad brand/social listening across tools | /sales-social-listening {question} |
| Wiring Noisely into a CRM/ticketer generically (iPaaS) | /sales-integration {question} |
When routing, give the exact command, e.g. "This is a strategy question — run: /sales-customer-feedback design a closed-loop VoC program".
Step 3 — Noisely platform reference
Read references/platform-guide.md for the full reference — the source/analysis/output model (what's UI-config vs webhook vs CSV), the credit-based pricing, the action-item data model, and quick-start recipes (route action items to Linear/webhook; export to Sheets; tune brand-ambiguity filters).
Read references/noisely-api-reference.md for the integration surface — no public REST API is documented; the surface is (23+, UI-config), the (12 categories → sentiment → urgency/impact → clustered → spike detection), including (payload schema not published — capture a live delivery), and import/export.
