# Name question reference

You'll see how to collect a full name or separate first and last names, then save them to the fields your email platform uses.

Available on the Grow, Scale, and Pro plans.

A **Name** question lets you collect someone's name and save it as one answer or separate first and last names.

## When to use it

Use it when you want a name for your contact record or follow-up. A name alone doesn't identify a visitor by email or verify who they are.

![Name question draft with wording, type-specific settings, behavior, and internal name](https://rightmessage.com/help/screens/questions-name-settings.light.webp)

## Settings

**Name format** defaults to **First and last name**. Each part has a **Label** and **Placeholder** under **Field text**. The default labels are **First name** and **Last name**, with empty placeholders. Empty overrides use the default text.

**Full name** displays one field instead. Its **Placeholder** defaults to **Full name**. This format has no separate visible field label and doesn't split first and last names.

**Required** defaults off. Visitors can skip the question. When submitting the first-and-last format, both name parts must be present. A partial name fails validation even when the question is optional. Full-name format requires a nonempty value when Required is on.

## How answers are stored and synced

The two-part format keeps the first and last names separately and joins them with a space for the complete answer. **Full name** keeps the entered name as one part.

### Choose one destination or separate fields

**First and last name** supports **One field** or **One field per part**. A new unmapped question opens per-part mapping. You can map **First name** and **Last name** to native or custom fields, or save the complete answer to one field. **Full name** uses one destination.

To switch a populated mapping:

1. Choose **One field** or **One field per part**.
2. Review **Clear existing mappings?**.
3. Choose **Switch and clear** to remove the old mappings.

Switching doesn't migrate historical field values.

A name answer doesn't automatically create a segment or an answer branch. Use [input-answer conditions](https://rightmessage.com/help/conditions-answers) to compare the stored value. A [linked form field](https://rightmessage.com/help/form-fields-reference) submits with its form.

The question-editor preview doesn't record answers or send data to your email platform. Edits to an existing question save to your draft automatically and affect every use after you publish.

See [shared question settings](https://rightmessage.com/help/question-settings-reference) for wording and button labels, the [Questions library reference](https://rightmessage.com/help/question-library-reference) for creation and reuse, and [answer sync](https://rightmessage.com/help/synchronizing-contact-data-with-your-email-platform-or-crm) for identification and destination checks.