Canonical page: https://tellenze.com/help/signals

Turn Signals into reviewed work

Collect reports, connect evidence, review Looper suggestions, and follow resolution and recurrences.

Turn reports into reviewed work

Open Work → Signals to collect unstructured reports and turn related evidence into suggested work. A signal can combine customer messages, service telemetry, and application errors without losing the original reports. This release accepts text, links, and metadata through the web, MCP, Member App API, and Looper. Connect external services through your own App; native Discord and telemetry connectors are not included. The manual Add signal flow does not upload files. Open Forms from Signals to manage Custom Forms for this destination and collect configurable questions and scanned file attachments through public or workspace-only forms.

The Signals section on Home shows workspace stage counts and up to three signals to review. Select a stage to open its board view, a preview to open that signal, or Open Signals for the full board. The section is hidden when there are no active, recently completed or filtered signals. Use the chevron beside Open Signals to collapse or expand the section; your choice is remembered for your account in this browser. Open Signals remains available while collapsed. The completed count follows the same configured window as the board. Project labels and suggestion counts respect your access, and processing notices do not trigger a new pass.

Use Add signal, provide the report and source, and save it. Append evidence to an existing signal when it concerns the same issue. The landing board follows Raw → Grouped → In progress → In review → Completed. The search toolbar and Filters button work like a project's board: expand the compact state, source, and project dropdowns, see the active filter count, or clear the filters. Organized cards use a concise issue title and show project labels for proposed or linked work you can access; original report text stays in Evidence. Each column loads independently, so a large raw backlog does not hide work further along. Open a card to inspect evidence, suggestions, linked work, shared discussion, history, and related signals and take the next reviewed action.

The Completed column shows signals completed in the last 30 days by default. An administrator can change Show completed for (days) under Admin → Settings → Signals to any whole number from 1 to 365. The window uses the completion time. Older signals remain stored and accessible through History, their permanent links, and related-signal history. Filtered and discarded signals are available in the state filter and can be restored.

Understand the workflow

Received → Ready → Accepted → In review → Shipped describes operator progress. Processing health is separate: a provider failure does not discard evidence or complete work.

On the board, Raw means Received, Grouped means Ready, In progress means Accepted, and Completed means Shipped. Grouped can contain one organized report or several related reports; it does not require a merge. Work acceptance and completion still follow the review rules below.

• Received: reports awaiting organization.
• Ready: organized evidence, with zero or more suggestions.
• Accepted: at least one resolution work item is linked. Other suggestions can still need a decision.
• In review: resolution work is complete, every suggestion has a decision, and the current evidence has been reviewed.
• Shipped: a member confirms resolution and records an outcome.

Filtered holds likely noise with an explanation. Discarded records a member's decision. Use Discard signal in the detail page’s header actions (the archive-box icon) and record a reason. Both can be restored. Administrators manage source and fingerprint filters through Noise rules on Signals. Neither filtering nor discarding deletes the original evidence.

Associate projects before creating work

Use Starting projects in Add signal or Add evidence to identify up to 20 active projects you can access. These associations appear on Raw cards, Home previews and project-filtered views before Looper groups reports or suggests work. They provide context; they do not create work or restrict the signal to one project.

For ongoing feedback, open a project's Forms tab, choose New form, select Signals as the destination, and keep that project under Starting projects. In the builder, Collect as Signals lets you change or add starting projects before publishing. For example, a Phratek player-feedback form can start with Phratek. If a response also describes trouble with Emergent Accounts, Looper can associate that project using the report as evidence while keeping Phratek's context. Work still requires a member's approval. See Custom Forms.

On a signal's Overview, use Associated projects → Edit projects to adjust its current context. Original intake projects remain beside each report in Evidence, even after correction. Associations follow their reports through merges and splits; shipped signals retain their recorded context. Changing associations does not move existing suggestions or work. A member's removed association is not silently restored by Looper.

Reports are shared within the workspace. Project names, associations and related history follow current project access. Shared Looper analysis sees only eligible workspace-visible projects, never private routing context through an administrator's access. Intake from forms uses the last published starting projects; changing a draft does not change earlier reports or current public intake.

Quiet noisy signals

Use Noise rules on the Signals board for reports you already know are routine, such as successful health checks. An administrator can create rules; members can inspect filtered signals and restore them. Start with a source rule. You do not need a fingerprint for this.

1. Choose Add rule.
2. Enter the exact Source, for example heartbeat. This is the source key entered in Add signal, or the source_key sent by an App or MCP client. A display label can be different: a source shown as “Health checks” might have the key heartbeat.
3. Add a reason, such as “Routine successful health checks; no action needed.” The reason appears on signals filtered by the rule. It is an explanation, not a condition or an instruction to Looper. For example, source manual with reason “Lacks minimum context” filters all-manual signals even when their reports contain detailed evidence of a real failure.
4. Leave the advanced fingerprint empty, keep Enabled checked, and choose Save noise rules.

Rules are checked during processing, before the model analyzes the remaining signals. They do not filter reports immediately on receipt. Processing cadence still applies. Saving a rule does not rescan signals already processed; open an unaccepted Raw or Grouped signal and choose Process now, or Reconsider suggestions in Suggested work, to check it again.

The matching rules are deliberately precise:

• Source keys are exact and case-sensitive: heartbeat does not match Heartbeat or heartbeat-errors. Keywords, wildcards, and regular expressions are not supported.
• Every report in a signal must match the same enabled rule. A group containing both heartbeat and discord reports will not match a source-only heartbeat rule. Separate rules for those two sources do not combine to filter that mixed group.
• If a rule includes both a source and a fingerprint, both must match each report. If several rules match, the first matching rule supplies the explanation.
• Rules filter Raw or Grouped signals. They do not automatically filter accepted resolution work, In review signals, or Completed signals. Reporting windows and occurrence counts are not rule conditions.

Bring a signal back: disable, remove, or narrow the matching rule and save it. Open Filtered, select the signal, and choose Restore signal. The evidence is preserved. Disabling a rule does not restore signals automatically; restoring a signal without changing its matching rule can filter it again on a later processing pass.

Looper may also classify likely noise during analysis, even when there are no custom rules. Its explanation is shown on the signal, and you can restore it in the same way.

Advanced: fingerprints

Use Advanced: match a report fingerprint only when an integration maintainer has a verified stored hash. The field accepts a 64-character hash that matches either the report's source_fingerprint or its content_hash. These stored hashes are not currently displayed in Evidence or returned in the normal signal detail response. Do not paste the report text, source event ID, URL, or raw metadata.fingerprint value into this field.

For integrations that supply metadata.fingerprint, the source hash is SHA-256 of the exact source key, one NUL byte, and the trimmed metadata fingerprint: SHA-256(source_key + NUL + trim(metadata.fingerprint)). The separate content hash covers the submitted report and metadata, including any supplied occurrence times, counts, and reporting windows; a changed report can have a different content hash. Use a source-only rule unless you specifically need this narrower technical match.

Review evidence and suggested work

Reports retain their source, external event ID, URL, occurrence and receipt times, submitting member or App, and supplied metadata. Form reports also retain their form origin and accepted evidence attachments; public form submissions remain anonymous. Report volume and distinct sources are separate counts. Source-reported totals retain their reporting windows: overlapping telemetry windows are not added together into an invented total.

Review each suggested project, optional Focus group, work type, title, context, acceptance criteria, and severity. Accept it to create a native work item, or link an existing work item. Dismiss suggestions you do not want. Accepting again safely returns the existing work item. Changes to evidence or Required Context require a fresh review before acceptance.

Looper compares new reports with existing signals using exact fingerprints first, then shared terms in titles, summaries and report text, with source-only matches as a fallback. Different sources or wording do not prevent a supported merge. Similarity is a candidate for analysis, not proof that two failures share a cause. Accepted work and completed outcomes are never merged automatically. Search remains bounded and may be incomplete.

When new evidence changes a generated suggestion, Looper can revise that suggestion without creating another simply because its title changed. Duplicate untouched generated suggestions can be consolidated; expand Earlier suggestions to inspect their retained context. Member edits, dismissed suggestions and accepted work are preserved. Distinct work in the same project remains separate.

Looper generates suggestions in the same pass that organizes reports. It considers active, workspace-visible project names, keys, and descriptions. A plausible match can support an investigation even when the root cause is unknown; the suggestion states the assumption for your review. When it cannot propose useful work, Suggested work explains the limitation and asks focused questions. Add the missing details as evidence, discuss them with Looper, or reconsider an already processed Raw or Grouped signal from its detail page. Reconsideration is recorded in History, preserves the original reports, and respects the same processing cadence. Ordinary idle scans do not repeatedly analyze unchanged evidence.

Overview starts with a resolution progress bar and completed count for work you can access. View linked work opens the supporting work. Context links do not contribute to the percentage, and 100% work completion still requires the signal’s review and shipping checks.

The Linked work tab separates Resolution work, which determines whether a signal is ready for review, from Context links, which provide background. Track resolution progress here, open the native work item, or link existing work. Reclassifying a link requires a reason. Archived incomplete work still blocks resolution. Project permissions apply to suggestions, work links, and their history; shared reports do not grant private-project access. Shipping requires access to every resolution link.

New evidence during review returns the signal to Accepted. Review it before shipping. It does not silently change an existing task's scope.

Correct grouping and follow recurrences

Looper can merge unaccepted signals about the same issue. Members can merge or split groups while preserving original report identities. Accepted groups require an explicit review of evidence and work allocation; existing task receipts remain intact.

Reports arriving after a signal ships create a recurrence or join an open recurrence. The shipped outcome remains historical. Related signals can be marked related, recurrent, a possible regression, or a confirmed regression. Similarity alone does not prove a regression; record why you make that connection.

Use Looper and shared discussion

Use Process now or the configured schedule to have Looper organize changed evidence, propose grouping, classify noise, and suggest work. Processing uses existing workspace AI allowances. Idle checks make no provider request. Search and processing are bounded; limited coverage is shown when the available context cannot include everything.

After a processing request is accepted, the button stays loading and unavailable while the request is queued or running. The page refreshes its status automatically. A queued request can wait until the plan's next eligible start.

Use Discussion for a shared conversation about the signal. Mention a teammate to bring them into the discussion, or mention @looper to ask about the evidence, possible project, or next step. Looper replies in the same conversation, visible to workspace members. Queued, running, and failed replies have their own status. Discussion does not automatically create work or change the signal workflow; review suggested work before accepting it.

The separate Looper assistant remains private. Its conversation history is never copied into signal Discussion automatically. Shared Looper replies use shared signal context and eligible workspace-visible projects, without reading members' private assistant conversations or private projects.

Manual triage and discussion remain available when Looper is unavailable. Provider failures, exhausted allowances, or a suspended processing owner appear as processing problems for an administrator to resolve.

Choose availability and cadence

Signals is available on paid subscriptions starting at Starter.

The default is hourly. Under Admin → Settings → Signals, an administrator can choose manual mode or an allowed interval from 1, 5, 15, 30, and 60 minutes. Every processing request, including Process now, MCP, and Looper, respects the subscription minimum. Requests share one workspace run and coalesce until the next eligible start. The interval governs when work can start; it does not promise completion within that interval.

Paid downgrades clamp the effective interval. Moving to Free or losing paid entitlement locks Signals access and processing while retaining the data. Previously created work items remain usable. Previously published Custom Forms can still collect raw signal evidence, and their managers can read the original responses and files in Forms. This does not unlock the Signals board or processing. Restoring a paid subscription restores Signals and reconciles linked-work progress.