# A “done” activity in Pipedrive tells you nothing: make the Outcome field work for you

https://salesbond.app/blog/pipedrive-activity-outcome-field/
Published: 2026-10-03 · Updated: 2026-10-26

Make the Outcome field required before calls and meetings in Pipedrive can be marked done, and agree as a team what each outcome value means before you switch it on. Since July 2026 an admin can set this per activity type in the Activities tab under Settings ( [Pipedrive product updates, July 2026](https://www.pipedrive.com/en/product-updates)). The point is a “done” that says what came of the call, not only that it ended.

## Forty calls marked done, zero answers

Picture a manager on a Friday afternoon. One rep’s week shows forty call activities, every one of them marked done. The manager opens the first. Title: “Call Dana”. Done, Tuesday 10:14. No note. The second: “Follow up”. Done. The third has a note that says “called”. Twenty activities in, the picture has not changed. Forty green checkmarks, and not one of them says whether anyone picked up.

This is a made-up scene, but every manager we talk to recognises it. The rep did not do anything wrong. Pipedrive asked for one thing when the call ended, a click on “done”, and the rep gave it. The checkmark records that an activity ended. It records nothing about how.

So the week gets judged on volume, and volume is the first number reps learn to inflate (we have written about [why a call quota turns into junk calls](https://salesbond.app/blog/sales-activity-metrics-small-team/)). The Outcome field puts the “how” on the activity itself, at the moment the rep knows it.

## What changed in Pipedrive: the activity Outcome field, Priority, Note per type

Pipedrive’s July 2026 release note says it in two sentences: admins can configure field visibility and requirements per activity type in the Activities tab under Settings, and can “make the new Outcome field, Priority or Note required before an activity is marked as done”. The stated goal is “sharper reporting, coaching and automations” ( [product updates](https://www.pipedrive.com/en/product-updates)). In the API the field is `outcome`, an integer ID, and its values depend on the activity type ( [Pipedrive API: Activities](https://developers.pipedrive.com/docs/api/v1/Activities)).

Three things follow from that wording.

1. The setting is per activity type, so a call can demand an outcome while a task or a deadline does not.
2. The gate is “marked as done”, not “created”. A rep can still schedule a call in two seconds. The field is asked for when the call is over, which is the one moment the rep actually knows the outcome. The evening is where it pays off: a ten-minute routine of [closing the day in Pipedrive](https://salesbond.app/blog/daily-sales-report-close-the-day-in-pipedrive/) turns those outcomes into the daily report.
3. The values are not one global list. What a rep sees for a call may differ from what they see for a meeting.

Pipedrive’s Help Center does not describe the field yet. The release note and the API reference are the sources here, and neither says how the values are set or whether you can change them. So the next section is about what your team agrees each outcome means. Not about which button to click.

## Agree what each outcome means before anyone clicks it

An outcome list goes bad the same way a required deal field does: the moment there is an option that is always safe to pick, every activity gets that option. Whatever values your Pipedrive account shows for a call, the team needs one shared answer to “which of these do we use, and what does each one mean?”

Here is the set of meanings we would agree on for a call. Map them onto the values you have; if a meaning has no matching value, say where it goes instead (usually the note).

- **Connected, next step agreed.** The only outcome that moves a deal. If this one is rare, the rest of the week is about why.
- **Connected, no next step.** The buyer talked and nothing was scheduled. This is the one a manager asks about first.
- **Connected, not now.** A real conversation with a deferral. The next activity should carry the date they gave.
- **Voicemail or no answer.** One meaning, not two. Nobody has ever made a decision based on the difference. Pick the outcome, then add [the one-line log](https://salesbond.app/blog/voicemail-follow-up-pipedrive/) that tells the next caller what the buyer already heard.
- **Wrong contact.** The number or person is dead. It is a data-quality signal and should trigger a cleanup rather than another call.

For a meeting, four: held, next step agreed; held, no next step; no-show; rescheduled. We leave “held, not a fit” off on purpose. A buyer who is not a fit is a lost deal with a reason, and that belongs in the [lost reason](https://salesbond.app/blog/pipedrive-lost-reasons/) on the deal, not on the meeting. If customers book through a scheduler link, the same outcome list applies, but keep [self-booked meetings](https://salesbond.app/blog/pipedrive-meeting-scheduler-booked-meetings/) on their own type so the report can tell them apart.

If the outcome reads rescheduled for the second time, we wrote down [what to do with a meeting that is rescheduled again and again](https://salesbond.app/blog/prospect-keeps-rescheduling-pipedrive/).

![Outcome values a team agrees to use for calls and meetings in Pipedrive, with the "no next step" rows flagged](https://salesbond.app/wp-content/uploads/2026/10/pipedrive-activity-outcome-field-2.png)

Notice what the lists do. Every meaning either ends in a next step or explains why there isn’t one. That is the whole structure, and its why a short list is enough.

Write the definitions down once. “Connected” means a two-way conversation with the person on the activity. “Next step agreed” means the next step already exists as a dated activity on the deal, the same rule as the last line of a [five-line call note](https://salesbond.app/blog/sales-call-notes-minimum/). Ten minutes at one team meeting, and nobody argues about it again.

## Required or not: where friction pays off and where it does not

We would make Outcome required for calls and meetings and for nothing else. The reason is the one we gave for [required deal fields](https://salesbond.app/blog/required-fields-pipedrive/): a field earns the requirement when the person filling it knows the answer at that moment and someone else will decide something from it. At the end of a call both are true. The rep knows what happened, and the manager will act on the pattern.

Tasks fail the first half. “Send the proposal” has one outcome, which is that it got sent, and a required field there is a click with no information in it. Deadlines are the same. For the Email type the problem is worse: since March 2026 Pipedrive can create a completed email activity the instant you hit Send ( [product updates](https://www.pipedrive.com/en/product-updates)), and at that instant nobody knows the outcome. A required Outcome on an activity whose result is unknown invites a placeholder, and a placeholder in a required field is worse than a blank, because it looks like data.

Priority we would leave optional everywhere; it describes the rep’s intention, not the result. Note is the one we would require for meetings, and only meetings. A meeting without a note is a meeting the rest of the team cannot use, while a call with a clear outcome and a dated next step often needs nothing more.

If you want Priority to mean the same thing for every rep, we wrote down [what each priority level should mean](https://salesbond.app/blog/pipedrive-activity-priority-labels/) and how to keep High from becoming the default.

A required field doesn’t make reps thoughtful. It makes them fast. Keep the agreed set short enough that the fast answer and the honest one are the same click.

## Keeping automation and auto-logged email activities out of your counts

Two of Pipedrive’s 2026 changes quietly add activities that no human performed, and both end up next to the calls above.

The first is the one just mentioned. When “Automatically add emails sent from Pipedrive as activities” is switched on (under Personal preferences > Email sync > General), each email sent from the composer becomes an activity that is already marked as done and linked to the same deal and person as the email; those email activities are included in the activities performance report ( [Pipedrive: add emails as activities](https://support.pipedrive.com/article/add-emails-as-activities)). Useful for seeing outreach volume. Terrible if it sits in the same bucket as a connected call. Here is what that does to a per-rep comparison: how [auto-logged emails inflate the Pipedrive activity report](https://salesbond.app/blog/pipedrive-email-activities-activity-report-inflated/).

The setting lets each user choose which activity type these emails get, and the available types come from your company settings. So the fix is a type, not a filter: have the admin create a dedicated activity type for sent email (call it “Email (sent)” or similar) and ask everyone to pick it in that preference. From then on a count of calls and meetings can leave that type out, and a look at outreach can take it alone. It takes one person five minutes and the two numbers never mix again.

The second change arrived in August 2026: an activity added by an automation now says so in its detail view ( [product updates](https://www.pipedrive.com/en/product-updates)). That helps when you open one activity and wonder where it came from. It does not, by itself, separate them in a count, and the release note doesn’t claim it does. The same idea works here: give the activities an automation creates their own activity type, or at least a fixed prefix in the title, so they can be left out or looked at on their own. A deal that moved to “Proposal sent” and triggered a follow-up task did not generate rep effort, and your numbers should not say it did. As we argue in [what not to automate](https://salesbond.app/blog/what-not-to-automate-sales-process/), automate the reminder, never the record of what the human did. [Two-way calendar sync does the same with calendar events](https://salesbond.app/blog/pipedrive-calendar-sync-meetings-activities/), filed under whichever type you picked for incoming ones, so give that type the same treatment.

What is left is calls and meetings a person actually held, each with an outcome the rep chose at the moment of done.

## One question for the next 1-on-1

Overdue activities are a different job, and we covered the [manager’s sweep for those](https://salesbond.app/blog/pipedrive-activity-reminders/) separately. This is not that. It is one question, and it only works once the team has used the outcome field for a week or so.

Ask the rep: “Of the conversations you had this week, which ones ended with no next step? Walk me through two.” That is the whole question. It is not about volume, it does not accuse anyone of anything, and it goes straight to the moment where deals are actually won or quietly lost: the end of a conversation where nobody proposed what happens next. Before the field the honest answer lived in the rep’s memory. Now the rep recorded it at the moment of done, so the conversation starts from what they said then, not from what they remember on Friday. Sometimes the answer is a buyer who genuinely cannot commit yet, and the right move is a dated “not now” and a scheduled check-in. Sometimes it is a rep who does not know how to ask for the the next step, and that is coaching, not a dashboard problem. A count of forty checkmarks will never tell you which. If part of the team works in HubSpot, here is [the same outcome rule for HubSpot calls](https://salesbond.app/blog/hubspot-calls-log-outcome-next-step/).

We build SalesBond, a sales management layer on top of the CRM a team already uses; we started with Pipedrive. Its Deal Health product checks every deal against more than 20 rules, Activity among their categories, explains the factors that lowered a deal’s score and recommends a corrective action for each violation. That covers the deals; the 1-on-1 question above is still yours to ask. If you want the deal side checked without reading every deal, [check your CRM with SalesBond](https://salesbond.app/).

If you already run a [1-on-1 agenda](https://salesbond.app/blog/sales-1-on-1-agenda/), the question slots in where the pipeline review usually starts. Try it for three weeks and watch whether the “no next step” answers get shorter.