Moxie allows you to extend the core CRM database objects with custom fields to keep track of the information that is important for your business. Custom fields are supported on:
Clients
Contacts
Opportunities
Projects
Tasks
Watch this video or continue reading below.
You can access the Custom Field configuration in Workspace settings --> Custom Fields. From there you will see the five sections, one for each of the CRM database objects.
Adding Custom Fields
You can add new fields to each object by clicking the plus sign. This will add a new row that allows you to configure various properties of the data field.
Icon (optional) - select from over 500 icons to represent the field. Used in certain scenarios where the custom field data is displayed
Field name - this will be the label that you see in the various interfaces within Moxie
Mapping Key - the unique identifier for the data element that is used to move data between classes of objects (more on this later)
Type - Defines the type of data to be stored in this field. The options are:
Text - used for open ended text
Phone - validated phone field including country code
Email - validated email field
Link - HTTP hyper link
Numeric - any numeric value
Currency - any numeric value that stores monetary values
Date - Date
Select - single option select box
Radio - single option select radio buttons
Checkbox - multiple option select checkboxes
Options - used when the Type is one of Select, Radio, or Checkbox and allows you specify the items you can select from
Setting the data in your Custom Fields
Once your custom fields are configured, you will see them alongside the standard CRM fields. The fields can be manually configured when adding or updating database elements in both the browser and mobile versions of Moxie.
Using Mapping Keys
Mapping keys are an important component of the Custom Field features in that they allow data to flow between core modules within the CRM. The concept with mapping keys is to support moving data between stages of the client acquisition flow. Let's take a (not so real) example where you want to capture a leads birthday in a lead generation form submission.
Setting the form "Mapping Key" to the same value as your Custom Field mapping key let the system know that you want to move data from the form submission into your Custom Field. Likewise if you have custom field values on your Pipeline Opportunity that match to fields on your Client, Contact, or Project objects, the system will automatically set those values as your data moves from Lead --> Opportunity --> Client/Contact --> Project.
Pro-tip: If you'd like to be able to reference something from a form in an agreement, make sure to add the custom field to the client record. This will allow them to appear in the tokens dropdown in agreements under {{Clients.Custom.customfieldname}}
Tokens for Custom Fields
Your custom fields are made available in areas of the app where tokens can be utilized. This includes all of the template modules as well as the workflow automations. The format for accessing a custom field token is {{ModuleName.Custom.MappingKey}}. To reference our Date of Birth on the Contact object, we would use: {{Contact.Custom.DoB}}. You will also see your custom fields in many of the helper sections that display the available token values.
Importing data into Custom Fields
You are able to import data into your custom fields using the standard CSV data import module. Your custom fields will sit alongside the standard CRM fields as options to map during the import process.
