The run-through is the mode for the afternoon you spend calling forty contacts. It turns a browsing view into a queue: you no longer decide who is next, only what happens to the contact in front of you.
Why this is its own mode
In the normal view you look for a card, click it, read, close it, and look for the next one. Across forty contacts that is roughly two hundred actions that have nothing to do with any contact. The run-through removes them: after each outcome the next contact is already there, with its briefing, history, and call buttons.
Starting
The Run-through button sits in the toolbar, next to Sync. It takes exactly the contacts that are currently visible, in the order they appear.
The queue is frozen
At start the order is taken once and never touched again. This is the most important property of the mode, and it is deliberate.
The obvious build would be to always use the current list. That breaks the moment the first outcome is pressed: “Not interested” disqualifies the contact, the findings list reloads, the contact you just handled is no longer in it, and the pointer at “number 7 of 40” now points at somebody else. You would skip contacts without noticing.
So: the stack does not shrink because a colleague changes something, and it does not shrink because you disqualify somebody yourself.
The bar at the top
Above the panel runs a bar of its own:
The five outcomes
At the bottom, the outcomes replace the briefing button. Each one writes something and then moves on.
The first two sit on top in wide buttons, the three rarer ones below. The split follows frequency, not importance: “Appointment” is the most valuable outcome and still the rarest.
Moving on only happens after a successful write
If the write fails you stay on the contact and see the error. Otherwise you would be on the next contact while the previous one had nothing in its history, and that only surfaces weeks later when somebody asks why nothing is there.
What still works inside a run-through
The three-dot menu of the panel stays reachable. It holds the marketing objection, "Open in onOffice", "Copy opener" and “Exclude from scan”. Without the menu you could only reach a marketing objection by leaving the run-through, which is exactly the wrong moment for that.
Also available: writing a note, changing the phase, setting the assignee, adding a property. You can page backwards too; correcting a contact a second time still counts it as handled once.
The summary
When the stack is done, the summary replaces the next contact: how many contacts you handled and how they split across the outcomes. From there you return to the normal view.
The queue deliberately has no wrap-around: after the last entry it does not start over. Without an end there is no end of day, and that is exactly what the run-through is meant to deliver.