> For a complete page index, fetch https://developer.close.com/llms.txt

# Outcomes

Outcomes represent standardized results that can be applied to activities such as calls and meetings. They help sales teams track and categorize the results of their interactions with prospects and customers.

Each outcome has a name, optional description, and specifies which activity types it applies to (calls, meetings, or both). Outcomes can be of type `custom` (user-defined) or `vm-dropped` (automatically applied when any team member performs a [Voicemail Drop](https://help.close.com/docs/calling-from-close#dropping-a-voicemail)).

Organizations can create multiple outcomes to match their sales process. Examples: "Qualified", "Demo Booked", "Not Ready", "Bad Fit", etc.

To set an Outcome on a Call or Meeting, send a PUT with the desired `outcome_id: "outcome_xyz"` to the [Call API](/api/resources/activities/calls) or [Meeting API](/api/resources/activities/meetings).

> Outcomes represent standardized results that can be applied to activities such as calls and meetings.


## API Docs

- Outcomes [List or filter outcomes](https://developer.close.com/api/resources/outcomes/list.md)
- Outcomes [Create an outcome](https://developer.close.com/api/resources/outcomes/create.md)
- Outcomes [Fetch a single outcome](https://developer.close.com/api/resources/outcomes/get.md)
- Outcomes [Update an outcome](https://developer.close.com/api/resources/outcomes/update.md)
- Outcomes [Delete an outcome](https://developer.close.com/api/resources/outcomes/delete.md)

## OpenAPI Specification

The raw OpenAPI 3.1 specification for this API is available at:
- [OpenAPI JSON](https://developer.close.com/api/resources/outcomes/openapi.json)
- [OpenAPI YAML](https://developer.close.com/api/resources/outcomes/openapi.yaml)