Working with Custom Fields

Custom Fields can be used to categorize, prioritize or further diagnose conversations based on the support needs for your product or service. Fields can be required so that reporting data is always accurate month-to-month. Custom fields work alongside workflows, reports and the API right out of the box. The Custom Fields feature is only available on the Plus plan.

In this article

How custom fields work 

Custom fields can be created per mailbox, via your mailbox's settings page. There are five supported field types: 

  • Dropdown: Your classic dropdown list with an option to select one choice. You can define your choices and drag-and-drop to order them below.
  • Single line: A traditional free-entry textfield.
  • Multi line: A larger text area for longer bits of free-entry text.
  • Number: This field type validates the entry to be sure it's a number (no letters allowed).
  • Date: This field type validates the entry to be sure it's a date.

You can also choose whether to make a field required or not. Required fields will have to be filled in before updates can be made to the conversation. Once you've created some fields, they'll appear in two places within the app: 

  • At the top of a conversation when the editor is not open, or at the bottom of the editor when composing a reply. 
  • On the new conversation page when sending a new email, or when logging a new phone conversation. 

Creating and editing fields

Creating a new field

Only Administrators can add or edit custom fields. Each mailbox has a maximum limit of ten Custom Fields.

1

To create new fields, open the mailbox where you'd like the fields to appear, then select Custom Fields from the mailbox settings dropdown.

2

Click on the New Custom Field button to start creating new fields. 

3

Start building the field: 

  • The field name is visible only to Help Scout Users. 
  • Select a field type. You can create a field as a dropdown, single line, multi line, number, or date type. 
  • Make the field required by flipping the Required ON/OFF switch. If a field is required, it must be populated before the conversation can be Closed. 

Our example below is a dropdown field. You can add new options by clicking the  + button, then re-order each option by dragging and dropping. Click the Save Field button to save the field. 

Editing existing fields

To edit existing fields, click on the field title bar to expand the field. You can change the field name, drop down options, or whether or not the field is required. You cannot change the field type after a field has been created. 

Reporting on fields

Views make it easy to drill down on custom field values alongside other conversation values, such as tags and conversation types. 

Common questions

Is it possible to show custom fields in a Beacon?
Not just yet, but this is something we'd like to support in the near future. 

Can I add custom fields to customer profiles? 
Custom fields can only be added to conversations at this time. 

Still stuck? How can we help? How can we help?