Ask Signals, and get an answer instead of a list.
Plain English questions about your own desk, answered from everything that has been said, with the sources attached.
What it is
Ask Signals answers questions about your own data in plain English. Rather than returning a list of records to read, it states the answer and shows the calls, emails and notes it came from. It only draws on what a recruiter is permitted to see, and it says when it does not have enough to answer rather than guessing.
Searching and answering
Searching and answering are different things. A search gives you twelve records and the job of reading them. An answer tells you the thing you asked. The difference is not the box you type into, it is whether the record underneath is complete enough to answer from. A chat box sitting on a database of half filled fields returns half filled answers, which is why most recruiters stop using them after a fortnight.
How it works
You ask in plain English
No boolean, no filters, no field names. The question is asked the way you would ask a colleague who had been on every call.
It reads everything you are allowed to see
Calls, email, messages, notes and records, across your whole desk. The answer is correct for you, bounded by your own scope, so a recruiter in one office never gets an answer built from another office's data they cannot see.
It answers, with the sources attached
The answer states the thing. Underneath it, the calls, emails and notes it was drawn from, each one a click away.
You check anything you want to
Nothing has to be taken on trust. Open the source, read what was actually said, and use the answer in front of a client knowing where it came from.
What it looks like
The answer, and everything it was drawn from.
What it means on the desk
You can use the answer in front of a client, because you can see where it came from.
A question about six months ago takes the same time as a question about yesterday.
Nobody has to remember which record the detail was filed under.
Where it fits
Automatic capture. Why there is enough on the record to answer from.
Notes written for you. What a single conversation looks like once it has been written up.
Many offices, one system. How scope decides what an answer can draw on.
Common questions
Answers come only from your data. Ask Signals does not draw on anything outside your workspace, and every answer carries the calls, emails and notes it used. Each source opens in a click, so an answer is never a claim you have to take on trust. If the record is thin in one area, the answer says so instead of filling the space.
It tells you. Where the record does not hold enough to answer, Ask Signals says what is missing rather than producing something plausible. A quiet week on a desk shows up as a quiet week, not as an invented summary, which is what makes the answers you do get worth acting on.
It answers within your scope. The answer you get is the correct one for you, built from the records, calls and messages you are permitted to see. A recruiter in Singapore and a director with group visibility can ask the same question and each gets the answer that is right for their view.
Both, and mostly the former. Calls, email, messages and notes carry the detail that fields never hold, so they are what most answers are built from. Structured fields are read alongside them, which is why an answer can quote what a client actually said about salary rather than a stage label.
Anything on your desk. Candidates, clients, jobs, your pipeline and your own activity are all answerable, and a question can cross them. Ask which clients have gone quiet, which jobs have stalled at second interview, or what a candidate said about notice period, in the same box.
Yes, across APAC languages. A conversation held in Cantonese, Mandarin, Japanese or Bahasa is read the same way an English one is, and you can ask your question in one language about a conversation held in another. The sources are shown in the language they were recorded in.