> For the complete documentation index, see [llms.txt](https://help.delpha.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.delpha.io/delpha-for-salesforce/how-to-faq/delpha-data-quality/do-i-consume-a-token-when-applying-a-delpha-recommendation.md).

# Do I consume a token when applying a Delpha recommendation?

Learn exactly when Delpha uses a token and why applying a recommendation is always free of charge.

### The Short Answer

**No.** You do not consume a token when applying a recommendation.

In Delpha, the action of a user (or an automated process) accepting and applying a suggested fix is completely free of charge.

### When Are Tokens Actually Consumed?

Delpha *only* consumes a token during the **analysis and generation phase**.

As explained in our [What is a Token? ](/delpha-for-salesforce/how-to-faq/delpha-data-quality/what-is-a-token.md)guide, a token is used when the system:

* Scans a record to evaluate its data quality.
* Searches for missing information (like retrieving an email or LinkedIn profile).
* Generates the actual recommendation for you to review.

Once that recommendation is generated and waiting for you, the token has already been spent.

### Why Does This Matter?

This pricing model is designed to give you complete freedom over your data governance:

* **Unlimited Reviews:** Your team can review, apply, or dismiss recommendations as many times as they want without worrying about additional costs.
* **Predictable Usage:** Your token consumption is entirely driven by your automated data refresh schedule (Daily, Monthly, Quarterly), not by how active your users are in applying the fixes.

{% hint style="success" %}
**Best Practice:** Encourage your team to actively review and apply recommendations! Since applying them is free, doing so maximizes the ROI of the tokens you've already consumed to find those insights.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.delpha.io/delpha-for-salesforce/how-to-faq/delpha-data-quality/do-i-consume-a-token-when-applying-a-delpha-recommendation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.