Loading
Because logging a call usually means a free-text note. It takes two minutes, produces nothing countable, and is therefore skipped whenever the day is busy — which is every day that matters.
Call logging records an outcome, a duration and a next step against the contact and deal, either from the interface in three clicks or from a telephony system through the API.
The outcome is a structured value from a short list, the duration comes from the call where telephony is connected, and the next step creates a scheduled task. Free text is optional and sits beside them.
Making the next step mandatory at log time took the proportion of open deals with no scheduled follow-up from 38% to 6% in a month, which deal scoring then had far less to flag.
Treepie does not record or transcribe calls. It stores what your telephony system sends it and what the person logging chose to say.
The activity timeline shows it, activity reports count outcomes rather than volume, deal scoring reads recency, and assignment queues clear when a first call is logged.
Yes, through the API. Duration and direction come across; the outcome stays a human judgement.
You decide. Requiring it is the single change most teams notice.
Yes — outcomes are structured values, which is why they are a list rather than a text box.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.