Canonical page: https://tellenze.com/platform/signals Signals · Observe and respond # Find the work in the noise. A customer report. An outage alert. The same error again. Bring the clues together, let Looper suggest a next step, and keep the evidence with the work your team chooses to do. [Join early access](#waitlist)[Follow a signal](#signal-flow) Available on Starter and above. [Explore plans](https://tellenze.com/pricing) Illustrative example · Accounts login - Customer reports Discord messages: “We can’t log in.” - Service telemetry The Accounts service reports an outage. - Application errors Login requests return connection errors. Related evidence, brought together One signal · Suggested incident ## Investigate the Accounts login outage. Three sources point to a shared problem. Review the scope and evidence before creating work. Your team decides what happens next. Example reports supplied through web, Apps/API, MCP or Looper. This diagram illustrates the workflow. From report to resolution ## A clear next step. With the story still attached. Follow signals across the board, from raw reports to completed work. Grouping helps you understand the issue; a member decides which suggestions become work. - 01 ### Raw Capture a report as it arrives. Keep the original words, source, links and timing. - 02 ### Grouped Looper brings related reports together and suggests work for the projects that fit. Review and edit the suggestions. - 03 ### In progress Accept a suggestion or link existing resolution work. The signal stays connected while the team investigates and delivers. - 04 ### In review Review the outcome once resolution work is complete, every suggestion has a decision and new evidence has been assessed. - 05 ### Completed A member confirms the resolution and records what happened. The evidence and outcome remain available. ### If it happens again, keep the connection. New reports can connect to earlier signals as related issues, recurrences or possible regressions. The original outcome stays intact, so the team can compare what changed. Bring the clues you already have ## Start with a report. Structure can come later. Add text, links and metadata from the web, a permissioned App or API integration, an MCP client, or Looper. Each report keeps its source and original content as the signal develops. WebApps & APIMCPLooper ### See the evidence behind the pattern. Read the original reports and follow their source links. Report volume, distinct sources and source-reported occurrences stay separate, so a delivery retry does not look like another incident. ### Turn down the noise. Keep a way back. Use source rules and Looper’s noise classification to keep triage focused. Filtered signals carry an explanation and can be restored. ### Know when more context would help. When Looper cannot ground a useful suggestion, it explains the gap and asks focused questions. Add evidence, discuss it, or ask it to reconsider. Reason together ## The discussion belongs with the signal. Mention teammates to bring them into the conversation. Mention @looper to ask about the evidence, a possible project match or what still needs investigating. The answer stays in the shared discussion, where everyone can follow the reasoning. Private Looper conversations stay private. Shared chat helps you reason. Work changes still go through the reviewed controls. Illustrative shared discussion · Accounts example Alex @looper Do these reports belong together? @Sam, can you help confirm the impact? Looper The login reports and Accounts errors could describe the same outage. Accounts looks like a plausible destination for an investigation; the root cause still needs checking. Reasoning from the supplied reports Your team keeps the deciding vote ## Useful suggestions. Reviewed work. ### Shape the work before accepting it. Edit the project, work type, title, context and acceptance criteria. One signal can suggest several work items across projects; accept the useful ones individually and dismiss the rest. ### Keep existing work in the picture. Link work that already addresses the issue. Resolution work and contextual links stay distinct in the Linked work tab, so the team knows what still needs to be finished. ### Close the loop deliberately. Completing linked work brings the signal into review when its remaining decisions and evidence are settled. A member confirms the resolution and records a short outcome. A few useful details ## Before the first report. Which plans include Signals? Signals is available on Starter, Team, Business and Enterprise. It is not included in Free. [Compare plans and processing intervals.](https://tellenze.com/pricing) When does Looper organize reports? Administrators choose the cadence in workspace settings, starting with an hourly default, or use manual mode. Processing requests share the plan’s minimum interval. Discussion and manual triage remain available immediately. Does Signals connect directly to Discord or telemetry tools? Bring those reports through a permissioned App or API integration, an MCP client, the web or Looper. Signals accepts text, links and metadata; dedicated Discord and telemetry connectors are outside this release. Can I correct how reports were grouped? Yes. Review the evidence and correct a grouping or split a signal. Once work has been accepted, regrouping also requires an explicit review of the evidence and work links. The original reports and accepted work are preserved. What happens to older completed signals? Workspace settings control how long completed signals appear on the board. Older signals remain in History and can help the team understand a later recurrence. COME TAKE A LOOK ## A little less busy. A lot more together. Curious? Leave your email. We’ll keep you posted on early access and what’s new.