From connection to a fix that worked
1
Connect an agent and approve its brief
You connect a Retell agent with an API key. Signal drafts a short brief of what the agent is for and what a good call is, and you correct and approve it. Approving starts the first import: the latest 500 calls from the last 30 days.
2
Calls keep arriving
After the first import, new calls show up on their own within about 15 minutes of ending, or as soon as they end if you add Signal’s webhook in Retell. Each call has its own page with the recording, the transcript, the steps it passed through and what each tool did. See Calls and flow.
3
Signal reads every call
Signal works out how each call went for the caller and, when something went wrong, where and why. On a call page you see this under Why this outcome, What went wrong and Signals. Calls where the caller never spoke are counted in the call outcomes and are not treated as conversations.
4
5
Your board lists what to do first
Fix holds confirmed defects and Improve holds changes you control that move your numbers, each ordered by impact. A confirmed pattern whose cause Signal could not establish is listed apart, under Cause not established, and is never presented as something to fix. Overview shows the top of each list, and Issues has the full lists.
6
You ship a change, and Signal checks it
When you publish a new version in Retell, Signal shows what changed in the configuration next to what production did afterwards. It tells you when a difference is real and when there are not enough calls yet. On each issue, By version says whether the live version fixed it. See Versions.
7
Or test the change before callers meet it
A call behind an issue can become a test: a simulated caller with the original caller’s goal, run against a version of your agent, with personal details masked. Tests run as text conversations, so they cover Understanding, Flow and state, and Integrations. See Test a fix.
What you can rely on
Every issue is something you can fix
“Dead air” is something a person noticed. Nobody owns dead air. Somebody owns a lookup that takes nine seconds. So every issue names a place (a step, a tool or a transition), a cause, and a change someone could make. A symptom that could come from several different problems is not reported as one issue.Signal says when it does not know
A wrong issue costs more than the minutes spent reading it. Once a board has been wrong a few times, people stop believing it, including when it is right. A cause is reported only when Signal has confirmed it against the calls. When the calls do not show why something happened, Signal says Cause not established. The pattern stays visible, but it is never offered as a defect to fix and never gets a suggested change. That is a legitimate result, printed on purpose. See Cause not established. A reported cause is still a hypothesis until a change proves it. That is why every issue links to the calls behind it, and why Signal tells you afterwards whether your fix worked.It works with your agent as you built it
Your steps and tools are named differently from anyone else’s, and Signal does not depend on your names. It reads calls in other languages too, but works best on calls in English.Designed behaviour is not a defect
A questionnaire that comes back to the same step for each question, or a flow that asks the same questions for each vehicle, is working as built. Signal is designed not to report behaviour like this as a defect. If Signal still flags something your agent does on purpose, answer No on the issue and pick Meant to work that way. The rejection sticks, and it is a sign that your brief should describe that behaviour.Callers are not defects
Someone who hears “we’re closed” and hangs up without a word counts in the call outcomes, apart from the problems you can fix, because no change to your agent would stop it.Next steps
Calls and flow
What you see on a call page and on the Flow page.
Lanes
The five places a defect can live, and who owns each fix.
Issues
What an issue contains and how to act on it.
Versions
How to read what production did after a change.