CRM

Confusing Field Mapping Between “Account,” “Location,” and Business Profile
I’ve noticed an inconsistency between the custom field names used in automations and those defined in the “Business Profile,” which creates confusion during workflow setup. For example, within a workflow, selecting Account → Address Line 1 inserts the value {{location.address}}. However, this value corresponds to a field labeled “Street Address” in the Business Profile. This mismatch in naming conventions applies across multiple fields. Additionally, it is unclear why selecting Account fields results in values prefixed with {{location...}}. The term “location” appears to refer to the Business Profile, but this relationship is not explicitly explained. This adds another layer of confusion, as users must mentally map “Account” fields in automations to “location” variables and then to differently named fields in the Business Profile. Because of these inconsistencies, it becomes difficult to understand what data is actually being referenced when building workflows. This often leads to unnecessary trial and error to verify outputs, which slows down the process and makes it harder to confidently select the correct fields from the start. Improving naming consistency across the platform—or clearly documenting and aligning how “Account,” “location,” and Business Profile fields relate to each other—would significantly improve usability and reduce the need for repeated testing.
0
·
Enhancement
Static and Smart Lists
ASK: Add Static Lists as an option. WHAT ARE THEY: Static lists include records that meet a set of criteria when the list is saved. Static lists do not update automatically, so new records that meet the criteria will not be added to the list. Records can be manually added and removed from static lists. CURRENT STATUS: The only way to group contacts into a "list" is dynamically with a tag or field. THE ISSUE: If you want to keep that contact in that "list," you have to ensure that you persist that tag or field, which causes CRM clutter. ENHANCEMENT: Having the ability to set up Static (non-dynamic) lists that we can simply place our customers in enables us to maintain a cleaner CRM and provides clarity. To go along with this, we can have a workflow that adds a contact to a static list and removes them from a static list based on behavior. This person can be a part of multiple static lists. USE CASE: Examples of when static segments should be used include... 👉 Setting up a list of people from a networking event you attended. 👉 Setting up a list of people who filled out a specific form 👉 Quickly create a list of contacts you want your outbound team to reach out to 👉 Flexible list management without tag clutter 👉 Create a group of contacts or companies that you do not want to change 👉 Manually adding records to a workflow. 👉 Sending one-time email blasts, email campaigns that you don't run often, and for a group of contacts that doesn't change (e.g., event attendees, staff segments for an internal newsletter, or segments from a trade show). 👉 Manually grouping records that may not have shared attributes or behavior. 👉 Segmenting to bulk-delete records from your account. plus many more.. SUMMARY: Having the ability to choose to create a Static AND Dynamic Smart list would improve data control and user experience by create easy segmentation options.
0
·
Enhancement
Load More