---
title: "Preferred Name"
slug: "preferred-name-merge-field"
updated: 2024-10-15T14:12:37Z
published: 2024-10-15T14:12:37Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://knowledge.technolutions.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Preferred Name

## Preferred name on a person record

If a person’s preferred name doesn’t match their first name, the preferred name appears in parenthesis.

![](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/image(278).png)

The standard preferred name field can be merged into form or event communications as `sys-preferred`. This is possible even when preferred name is not collected on the form itself.

> [!WARNING]
> 📝 Note
> 
> This field must appear as an option in the merge fields bar of the message in order to be used.

## Preferred name as a merge field

In Deliver messages, the preferred name export can be added and included as a merge field.

The preferred name merge field in a Deliver mailing automatically merges in and displays the preferred name if one exists. Otherwise, data in the first name field appears.

No liquid markup is required to conditionally display the record's first name if no preferred name is provided.

### Form and event communications

The `sys-preferred` merge field for form-based or event-based communications considers the values of preferred name and first name in the following order:

1. `sys:preferred` from the form response
2. `sys:first` from the form response
3. `sys:preferred` from the student record
4. `sys:first` from the student record

If a form only collects `sys:first`, the `sys-preferred` merge field selects `sys:first` from the form registration (number 2, above).

If no preferred name is entered on the form, Slate automatically merges in the first name entered on the form for the `sys-preferred` merge field.

> [!TIP]
> ⭐ Best Practice
> 
> To most effectively use preferred name in a form/event communication, collect and map this data point on the form.
> 
> For form or event communications using certain triggers, an export for preferred name can be added under "Edit Conditions" and used as a merge field in the communication.

### Custom dashboards and portals

If using `sys-preferred` for a custom dashboard or portal and no preferred name exists on the person record, Slate automatically merges in the first name from the person record for the `sys-preferred` merge field.

> [!TIP]
> ✨ Tip: Lived Name Custom Field
> 
> Creating a [Custom Field](/v1/docs/custom-fields) for lived name is another option for handling multiple preferred name fields. Use the [Community Forums](https://community.technolutions.com/using-the-slate-community) for suggestions.