In the screenshot above - I was trying to create the custom field in our own CRM (we use REW CRM too) and I wanted to put in the URL for a customers Forum User.
Obviously URL’s can get quite long, so the display bug is - since there are no spaces in the words, it doesn’t jump to the next line as text would (easy fix)
But then I thought about it - ideally I don’t want to see the URL anyways - I want anchor text and for it to be clickable.
So why not add a new field type to the types dropdown when creating a new custom field - call it “URL”
That sounds really useful we can definitely work on that!
I was also wondering whether custom fields should at any point be visible for the lead under their preferences, maybe give them the option to add their own URLs?
Definitely! I’m thinking about a custom way to expand the lead preferences page, maybe the ability to add a new section below the Contact Information or Mailing Information where we could make those fields visible:
This way leads have the ability to add that data themselves, I think the possibilities are endless but to add to the social media links example, some potentially relevant fields could be:
Preferred Language
Specific Property Requirements
Move-in Target Date
This could ease up some of the work for agents, does that make sense? Can anyone think of other relevant fields?
I imagine we don’t want leads actually creating a million weird custom fields, so they would only be able to “fill in” fields we had created in the backend, is that right? Kind of like a “tell us more about yourself” section:
In terms of interacting with it - do we let them add, edit and delete? Or just add? (and what happens when we have added it and they want to change or delete it (and we don’t want them too?) Could it be we detect if it was agent-added (in which case they can’t touch it) but if it’s user-added, they can mess with it?
Yes! That was my vision for this, we definitely don’t want leads creating fields, but rather have the option to show it to them and allow them to fill them up themselves!
I think we can easily solve this by not making all custom fields visible to leads but rather make it an optional check, sort of a “show field yes/no” option. This way if an agent doesn’t want the lead editing something, they can opt to hide it from the frontend lead preferences. Or, we could even go further and explore making a field visible to leads but not editable if agents prefer that.
Would love to hear from our users, would any of these scenarios provide value for your leads?
