Call Signals
Capture intent, urgency, follow up reasons and similar signals as structured fields you define with the agent, and use them to decide who to call back first.
Showing instructions for Xebit VoiceCloud.Showing instructions for Xebit VoiceKit, on your own infrastructure. Switch with the selector at the top. Updated 22 October 2026.
Call signals are the details that tell your team how a conversation went and what to do about it: what the caller wanted, how urgent it was, why they need a callback. In Xebit you decide which signals matter, define them as structured fields with the agent, and the agent captures them during the call. Together with the disposition and the summary, they give a clear picture of each conversation.
Xebit does not score sentiment automatically. Signals are fields you define and the agent fills in from what the caller actually said, so each one means exactly what you decided it means.
Signals you can capture
An example set that works for many teams:
| Signal | Example values | What it shows |
|---|---|---|
| Intent | Book, enquire, complain, pay, cancel | What the caller was trying to do |
| Urgency | High, medium, low | How soon the caller needs something to happen |
| Follow up reason | Wants a quote, asked for a manager, needs documents | Why someone should call back |
| Asked for a person | Yes or no | Whether the caller wanted to speak to someone |
| Complaint raised | Yes or no, with the topic | Whether the call needs a service recovery step |
| Lead status | Your own pipeline stages | Where the contact now sits. See Lead Quality Metrics. |
Every call also carries two signals you do not need to define:
- The disposition: how the call ended, such as completed, failed to connect or caller hung up.
- The summary: what was wanted, what was agreed and what happens next.
Define your signals
- Sign in to the Xebit VoiceCloud dashboard at
voice.xebit.ai. - Sign in to the Xebit VoiceKit admin console on your own host.
- Open the agent's settings and go to the fields it captures.
- Add each signal with a clear name and, where you can, a fixed set of allowed values. "High, medium, low" is easier to act on than free text.
- In the agent's instructions, say what each value means. For example: urgency is high if the caller has a deadline within two days.
- Start a test call and check the fields come out the way you expect.
See Configure an Agent and Agent Testing.
Where to find them
Open any call's details from the calls list. The captured fields sit with the transcript, summary and recording. The same fields go to your systems through webhooks, the REST API or the Zoho and Salesforce connector.
How to use them
Turn signals into simple rules your team follows. For example:
- High urgency and a qualified lead: call back the same day.
- Medium urgency and still deciding: schedule a follow up within a few days.
- Asked for a person but was not transferred: check why, and whether transfer rules need changing.
- Caller hung up early: read the transcript to see what happened in the first few turns.
- A lead marked lost: consider a reactivation campaign later. See database reactivation.
Put those rules in your CRM or ticketing system, so the follow up happens without anyone reading every call.
When signals trend badly
If you see more early hang ups, more complaints or more requests for a person than usual, review:
- the agent's tone and wording: is it too formal, too long or too scripted?
- the campaign message: does it match what the person expects to hear?
- the calling window: are calls going out at a bad time of day?
- Observability: a sudden change across many calls may be an incident, such as a slow provider, rather than the agent's instructions.
Next steps
- Call Recordings: listen to calls with poor signals.
- Transcripts: read what was said.
- Lead Quality Metrics: lead status across all calls.