Custom fields


If you require specific information during your booking flow that the existing fields do not collect, you can setup custom fields to procure this data. Custom fields can be configured for different models (contexts): for example, fields that appear during checkout (and are stored on transactions), or fields that appear when creating or editing Stations in Operations. In order to create or edit definitions, navigate to Admin > Sales Flow > Custom Fields and click +Add new (or edit an existing one) to arrive at the configuration screen.

CustomFields0

Configuration

CustomFields01

  • Title: Enter the text that you would like to appear in the custom field here.
  • Type:
    1. Text: Allows the user to type subjective information
    2. Checkbox: Can be configured as mandatory before allowing to continue through to the next screen.
    3. List: Will appear as a drop-down menu and prompt users to select one of the added sub-categaories. For lists you can add sub-categories by typing the list item and then **clicking the "plus" button**.
  • Required: If =true, it will make completing the new custom field mandatory.
  • Disabled: If =true, the custom field will not appear in the flow where it applies (e.g. purchase flow or station form).
  • Model: Select the context where this field is used—e.g. **Stations** for station create/edit in Operations, or the option used for checkout (transaction) custom fields.

The last step is to click Save to save your new custom field.

Where custom fields appear

  • Checkout (Sales flow): Custom fields configured for the checkout/transaction model appear in the final window of the checkout process and are stored on the transaction; they can be included in the Transactions report (see Sales flow (checkout custom fields) below).
  • Stations: Custom fields with model Stations appear when creating or editing a station under Operations > Stations. Values are stored on the station record and are included in the station API and in station webhooks. Required station custom fields must be filled before saving the station.

Sales flow (checkout custom fields)

For custom fields configured for the checkout/transaction model: once created, the new custom field will appear in the final window of the checkout process, right before the payment is finalized. For example, in the image below you can see a a customer field to collect information about how the customer heard of the service.

CustomFields1

For tracking all the custom field information, users will need to go to the Transactions report under Intelligence menu, then select the customer field from the gear sign located right beside the download button.

CustomFields2

Use case examples

  1. Compliance to an important policy of your company
  2. Where did you hear about us
  3. Additional company information