> For the complete documentation index, see [llms.txt](https://docs.sprinthub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinthub.com/en/topics/system-settings/fields/custom-field-contacts/custom-fields-contacts-status.md).

# Custom Fields - Contacts: Status

In SprintHub, you can customize and optimize the management of your Leads through Custom Fields. One of the most used fields in this process is Status, which can be adapted to represent Lead Scoring — classifying the level of maturity or priority of a contact according to criteria defined by your team.

In this article, we will show how to access and configure this field in a practical way, using Leads Custom Fields as an example.

### How to access Custom Fields

1. In the SprintHub side menu, go to System Settings (gear icon ⚙).
2. Select the first option in the list: Custom Fields - Contacts.
3. On the next screen, you will be able to view, edit, or create new custom fields, such as the Status field.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXfUeYW2H-9SweH4VlsDhcH6-pBsdkiYtcdTG4kGE0rdaoGsR7pI-0U5vKnYLfVdqe6Ke80Pbqfhv77HqWl_TEsaa_bv8DQGUqMyC_ITNi95_yECrcr4XATMnAttdAG9hsOpBjdyNQ?key=Xla7whybXftBHrYlVc5_CQ" alt=""><figcaption></figcaption></figure>

> 💡 The Status field can be configured with different values (such as "Cold", "Warm", "Hot") to represent the Lead Scoring of your operation.

### Video example

You can check the complete step-by-step in the video below:

{% embed url="<https://youtu.be/LDTPt7uBwAo>" %}

***

### Conclusion

Using the Status field in SprintHub's Custom Fields is an effective way to implement Lead Scoring in your lead relationship strategy. With this customization, your team gains more clarity in prioritizing contacts, improves the timing of outreach, and increases commercial productivity.


---

# 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://docs.sprinthub.com/en/topics/system-settings/fields/custom-field-contacts/custom-fields-contacts-status.md?ask=<question>&goal=<endgoal>
```

`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.
