> For the complete documentation index, see [llms.txt](https://software-help-docs.gitbook.io/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://software-help-docs.gitbook.io/knowledge-base/software-guide/settings/settings-custom-values.md). # Settings: Custom Values Custom Values, or Merge Fields, are values you can put into a template that will auto-populate when generating communication with your contacts. They are a great way to save time and maximize O*ur Software*, by automating information so you can send out customized communication more quickly. For example, an email templated can say "Hey {{ contact. name }}" and O*ur Software* will auto-populate the name of the contact so you can send a personal email to a group of contacts or through an ongoing campaign that leads are consistently being added to. Here are some common examples of custom values you may use in O*ur Software*: * Contact > Full name: {{ contact.name }} * Contact > First name: {{ contact.first\_name }} * Contact > Last name: {{ contact.last\_name }} * Contact > Email: {{ contact.email }} * Contact > Phone: {{ contact.phone }} * Contact > Company name: {{ contact.company\_name }} Some custom values are by default built into O*ur Software*, for most commonly used things like name, email, phone number, etc. These standard custom values are useful for common merge fields, such as a greeting/intro to an email like "Hey {{ contact. name }}". To view all the custom values in O*ur Software*, navigate to any You can also create your own custom values specifically for O*ur Software*. These can be useful if you want to set up automation by pre-setting defined values. (In the example below, the "Custom Email" will always populate test\@demoaccount, so you won't have to type it out every time.) **Step 1: Creating Custom Values** * You can create your own custom values by navigating to Settings > Custom Values * Click +Add Custom Value to create a new one. * You can click the trashcan icon to delete an existing one, or the pencil icon to edit. * These will be pre-set custom values with a defined value. **Step 2: Using Custom Values.** You can add a standard or self-created Custom Value into an email or SMS template, trigger, campaign, and more. * Navigate to the communication you wish to customize. * In the video example, we use a trigger setup to send a custom email. * In the screenshot example below, we are sending a bulk email from the Contacts section. * Choose "Custom Values" and the dropdown menu will appear (with a sub-menus). {% embed url="" %} * Click the value you wish to use, and it will be added to the body of the message. {% embed url="" %} * Now, the email intro essentially says "Hey \_\_\_\_\_," and O*ur Software* will automatically pull the first name of each contact into the email when it's sent out. ***NOTE*****:** the custom values used in this example contain a space between the symbols { } but in actual usage, there will be no space between the symbols and text. --- # 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://software-help-docs.gitbook.io/knowledge-base/software-guide/settings/settings-custom-values.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.