> For the complete documentation index, see [llms.txt](https://docs.roadmap.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roadmap.so/forms/save-into-a-customer-profile.md).

# Save into a customer profile

Save form details against a customer record and create the profile if it does not exist.

Use this when a form submission should become part of the customer's record.

This is useful for trade applications, onboarding forms, and account requests.

### What this setting does

When **Save details into a customer profile** is enabled, Roadmap saves the submitted details against the customer.

If the customer profile does not exist yet, it is created.

> **Screenshot placeholder:** Form settings with **Save details into a customer profile** enabled inside **Advance Settings**.

### Enable customer profile saving

{% stepper %}
{% step %}

#### Open the form settings

From **Forms**, open **Settings** for the form.
{% endstep %}

{% step %}

#### Open Advance Settings

Expand the advanced options for the form.
{% endstep %}

{% step %}

#### Enable customer profile saving

Check **Save details into a customer profile**.
{% endstep %}

{% step %}

#### Save and run a test submission

Submit the form once and confirm the customer record updates as expected.
{% endstep %}
{% endstepper %}

### When to use it

Use this setting when you want to:

* keep application data tied to the customer
* create a profile from a submitted form
* reuse form data later in support or sales workflows

### Good setup habits

* Include a reliable customer identifier in the form.
* Keep field names consistent across related forms.
* Test with a new submission after changing the field list.

### Troubleshooting

#### The customer profile was not created

Check these first:

* the setting is enabled
* the form changes were saved
* the submission included enough data to identify the customer

#### The wrong details were saved

Review the form fields and run a fresh test submission.

### Related guides

* [Building with forms](https://docs.roadmap.so/forms/building-with-forms.md)
* [Push to customer metafields](https://docs.roadmap.so/forms/push-to-customer-metafields.md)


---

# 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 by asking a question.

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

```
GET https://docs.roadmap.so/forms/save-into-a-customer-profile.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 `automate deployments from our CI pipeline` 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.
