> 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/delpha-apps/delpha-setup/delpha-configuration/default-values.md).

# Default Values

Set default field values in Delpha for Account, Contact, and Lead creation. Ensure required fields are always filled to prevent Salesforce validation errors and streamline automated record creation.

## Default Values Configuration in Delpha

The **Default Values** screen allows you to predefine field values for **Accounts**, **Contacts**, and **Leads**. This ensures smooth record creation and compliance with Salesforce validation rules by automatically filling in required fields.

### **Key Configuration Sections**

* **Account Default Values**
  * **Action**: Use *Add New Field* to define defaults (e.g., `Industry`, `Account Type`, `Region`)
  * **Purpose**: Prevent errors during Account creation due to missing required fields
* **Contact Default Values**
  * **Action**: Add defaults for fields like `Email`, `Phone`, or `Job Title`
  * **Purpose**: Ensure Contact records are created with all mandatory info
* **Lead Default Values**
  * **Action**: Set fields such as `Lead Source`, `Status`, or `Company Name`
  * **Purpose**: Avoid issues during Lead creation where validation rules apply

{% hint style="warning" %}
These settings are critical for the Job History use case as you can be proposed to create a new account or a new contact. 
{% 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/delpha-apps/delpha-setup/delpha-configuration/default-values.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.