Call summaries
The sentence where somebody promised something becomes a job with a name and a date on it.
The follow-up is drafted with the file on it. Missed calls come back ranked.
100%
of calls come back as a summary, filed under the customer who was on it rather than mailed to whoever dialed.
2fields
on every task a call leaves behind: the person who owns it, and the date it is due.
0%
of the follow-ups send themselves — each one is drafted, the file already on it, and a person presses send.
What happens when the call ends
Against what happens after a call today
| How it normally works |  With qallin | |
|---|---|---|
| When it ends | A recording, often an AI summary by email | A summary in the customer’s thread |
| A promise inside it | A line in the summary | A task with an owner and a due date |
| The follow-up | Written later, from notes | Written already, one tap to send |
| The file that was promised | Found and attached by hand | On the message |
| Where the reply goes out from | A personal inbox or phone | The number she called |
| Missed calls | A list in the order they called | Ordered by what is at stake |
| A week later | A recording nobody replays | Call, task and reply in one thread |
What the call leaves behind
Tasks with owners
A commitment becomes a task on a person, dated by what was actually said.
The file goes with it
The follow-up carries what was promised — the quote, the parts list, the time you booked.
Sent on the business number
The reply leaves from the line she called, so the answer comes back to the team.
Nothing to replay
Every call comes back as a transcript and a summary, not a file to sit through.
Missed calls, ranked
Repeat callers and open work sort above a number that rang once and left nothing.
Yours before it goes
Nothing sends itself. The draft is there to edit, to send, or to delete.
Straight answers
No. The follow-up is written and the attachment is on it, and then it waits. You read it, change what you want, and send it — or you delete it and nothing happens. That is deliberate: the value here is that the work is already done, not that a machine is talking to your customers while you are driving.
It reads the transcript of the call and pulls out the sentences where somebody committed to doing something — a quote by Friday, a callback today, a start date after signing. Each one is shown with the words that produced it and the moment in the call they came from, so you can see what it is working off rather than trusting a summary of a summary.
You change it or you delete it. The owner and the date are editable, and a task nobody should be doing comes off the list in one action. It is worth saying plainly: this reads speech, and speech is ambiguous, so the page you see after a call is a first draft of the work rather than a verdict on it.
It is built out of what you already have on that customer: whether they have called more than once today, whether there is an open quote or an unpaid deposit against their name, whether they are a customer at all. A stranger who called for four seconds and left nothing goes to the bottom. Nothing is scored on a hunch — if there is nothing on the record, the row says so.
In the customer’s thread, next to the call that created them, and in one list per person so somebody can open their own morning. The point of keeping them beside the call is that the evidence is one line away: whoever picks up the task can read the sentence that made it before they ring back.
They get the same treatment. A call the assistant took ends as a summary with what the caller wanted, what was promised to them and what is now somebody’s job — filed under that customer, in the same thread as everything else. A call nobody on your team heard should still leave the same trail as one they did.