Most people call the same handful of colleagues repeatedly. The history surface is built around that fact rather than around the theoretical case of calling everybody equally.
Three views
All. Everything, most recent first, with the direction and the length of each call.
Favourites. The people you starred, in whatever order you put them.
Missed. Inbound calls you did not answer. This is the list to check after every meeting.
Speed dial
A strip of faces sits above the history: your favourites first, then the people you genuinely call most, worked out from the last ninety days of activity.
You do not have to build it. Call people and it assembles itself. Star the ones you want fixed in place regardless of recent activity.
Starring is a single click on any row or any face, it is personal to you, and it takes effect immediately everywhere the strip appears.
The floating strip
There is also a column of faces at the edge of the screen, each with a presence dot.
Tap a face and it rings that person. One action, from anywhere in the platform, with no navigation at all.
The button at the end opens a searchable directory, so anybody can be reached whether or not they are on your strip, and anybody can be pinned to it.
The presence dot is the point of the whole widget. Ringing somebody who is in a meeting is worse than messaging them, and the dot tells you which situation you are in before you interrupt rather than afterwards.
Reading a row
Direction, who, when, and how long.
Length is the most informative field and the least noticed. A pattern of forty-second calls with one person usually means the messages that preceded each one should have been a call considerably sooner.
Missed calls
A missed call leaves no voicemail, because this is not a phone system. It is colleagues reaching colleagues inside an application, and the appropriate response is a message or a call back.
Which means the follow-up is entirely yours. Call back from the row, or message. Nothing chases it for you and nothing expires.
What it does not cover
External calls are not here. Phone calls to customers through the telephony integration live in Comms HQ, and they appear on the calendar under Calls, in teal.
This surface is internal voice only, and keeping the two apart is deliberate: they have different retention, different regulation, and different people looking at them.
What the history is actually for
Three uses, in descending order of how often they matter.
Calling back. The dominant case, and the reason the call button is on every row.
Reconstructing a day. Who you spoke to and for how long, which is occasionally the only record of an informal decision and worth checking before you claim something did not happen.
Noticing a pattern. Somebody you used to speak to weekly and have not called for a month is a relationship drifting, and this is the only surface that would tell you.
Favourites versus frequency
The strip mixes two different signals and they are not interchangeable.
Frequency is computed from the last ninety days. It reflects what you have actually been doing, and it changes as your work changes, which is right most of the time.
Favourites are fixed by you. They survive a quiet month.
The case for starring somebody is precisely that frequency would get them wrong: your manager, whom you call rarely and urgently; the person covering an account while you are away; anybody whose availability matters more than your call volume with them.
Everybody else is better left to frequency, which maintains itself.
When somebody is not reachable
The strip and the history both answer "can I get hold of this person", and three answers are worth acting on differently.
Presence says busy. Message instead. The call will interrupt something and the message will not, and you will usually have your answer within the hour anyway.
They did not pick up and are shown online. They are at their desk and not at their keyboard, or they are on a call the presence has not caught up with. One message, then move on.
Repeated missed calls in both directions. This is the pattern worth breaking rather than repeating. Two people missing each other three times have collectively spent more attention than the conversation was worth. Send the question in writing, or book fifteen minutes.
What the history will not tell you
Why the call happened. There is no note field and no subject. If a call produced a decision, that decision belongs in a message, a task or a meeting record, not in your memory of a call log row.
What was said. Ad-hoc calls are not recorded. Anything worth a transcript should have been started as a huddle, which is a calendar event and leaves a proper record.
Whether they called back. Direction is per row rather than per conversation, so a call and its return are two unrelated rows minutes apart. Reading a busy day back takes a moment of reconstruction.
Missed calls deserve a rule
Because nothing chases them, a small habit prevents the common failure.
Return the call or send a message the same day. A missed internal call with no follow-up is a colleague who assumes you saw it and decided not to respond.
Two misses from the same person is a message, not a third call. They are trying to reach you about something specific, and writing it down is faster than continuing to miss each other.
Two habits worth forming
Star five people, not fifteen. A speed dial with fifteen faces is a directory, and the search already does directories better than a strip of avatars can.
Check Missed after every meeting. An hour in a call is an hour of not answering anybody, and this is the only place that tells you what you did not answer.
Did this answer your question?
No, ask a person