Glory CRM is offering early access to six custom-field additions through an optional Labs switch: URL, flexible date and time, user, images or icons beside radio-button choices, images beside checkbox choices, and rich text.
In the account we checked on September 17, the switch was off and the standard field menu was still in place. The feature was available to activate in Labs, but it was not enabled in the account we checked. Check your own account before you build around it.
The early-access description places these fields directly on contacts. The examples do not establish support across every object, public form or native mobile view. Each surface needs its own test.
A field should answer one clear question
A field earns its place when it gives one useful fact a clear home. Before adding one, write down the question it answers, who keeps it current and what somebody will do with the answer.
“Website” and “estimate link” may both be URLs, but they serve different jobs. “Preferred contact time” and “renewal date” both involve time, but they should not share a field. Separate values that lead to separate decisions.
That small planning step matters more than the length of the field menu. It keeps a contact record readable and makes later filters, reports and follow-up rules easier to understand.
URL fields: one link, one purpose
A URL field can allow every domain, allow only named domains or block named domains. It supports one URL, so give the field a precise name. A business website, quote link and shared document link should live in separate fields when the business uses them differently.
Domain rules are useful when a link is supposed to come from a known system. If an estimate link should always use the company’s quoting portal, an allow-list can catch the wrong domain before it becomes part of the record.
Date and time fields: store the value you will use
Choose date only, time only, or date and time together. Date selection can be limited to future dates, past dates or a specific range.
Use the smallest format that answers the question. A renewal date usually does not need a time. A preferred contact time may not need a date. Clear field names make the difference visible when somebody opens the record months later.
User fields: add the people who need visibility
A user field can accept one person or multiple people. Selected users receive follower-level access to the record. The one-versus-many setting is chosen when the field is created and cannot be changed later, so decide that rule first.
Keep the record’s owner in the existing owner field. Use the new user field for additional people who need to stay connected to the contact. That keeps ownership clear while making collaboration visible.
Visual choices: keep the label clear
Radio buttons still represent one choice. They can now show an image or icon beside each option. Checkboxes allow multiple choices and can show an image beside each one.
The picture should help somebody recognize the option faster. Keep a stable text label and useful alt text with it. A photo can make a finish, layout or product style easier to spot, while the label keeps the record understandable in another view.
Rich text: make longer context readable
Rich-text fields support formatting such as bold, italics, headings and lists. They can make inspection notes, project context or structured instructions easier to scan.
Keep facts you need to filter or report in their own fields. Rich text works best for human-readable context. A status, amount, date or choice becomes much harder to use when it is buried inside a long note.
A hypothetical contact record
Imagine a home-service business preparing an estimate. This example is hypothetical, but it shows how the fields can stay separate by purpose:
- Estimate link: a URL field restricted to the approved quoting domain.
- Preferred follow-up: a date and time field limited to future dates.
- Internal reviewers: a multi-user field for the people who need follower access.
- Finish preference: a radio field with labeled images because the contact chooses one option.
- Requested add-ons: a checkbox field with labeled images because several options may apply.
- Site notes: a rich-text field with short headings for access, existing conditions and open questions.
This layout gives each value one job. It does not assume that every field belongs on a customer-facing form or works in every app view. Those are separate checks.
Test the field where the work happens
Start with one test contact after the feature is activated in your account. Check the field in the contact record, then check every other place where people are expected to read or edit it.
Try a valid and invalid URL. Test the edge of a date range. Confirm who receives follower access. Read the visual choices without relying on the pictures. Open the rich-text entry wherever staff will use it.
If a form, workflow, report or mobile app depends on the value, test that surface directly before changing the live process. A field appearing on the contact record proves only that view.
In Glory’s CRM & Revenue Infrastructure work, this mapping is part of the build: field purpose, folders, ownership, pipelines and automation rules are set around the way the business already handles inquiries.
Start with one missing piece of information. Write the question, maintainer, allowed value and next action. Then check the early-access setting and test the field from entry to use. A smaller field set that people understand is easier to maintain and more useful when the next lead arrives.