Make the contact source field lockable
B
Brenda Engelman
There needs to be an option to LOCK the contact source field. Where a contact originated may be different than additional opportunities associated with the contact. Every time you create a new opp. it will remove the source data if you put nothing, or replace the original source data with something like "cross sell" if you created an opportunity and put that as the opportunity source. If they book a meeting through your calendar then that calendar becomes the contact source. All of this crossing of data and replacement makes the source data useless for any metrics.
HIGHLVL-I-5037
T
Tim Colling
The perfect solution would be to make it possible to "lock" the values in fields of any sort, i.e., the "standard" Contact fields AND also custom fields.
Also, it would be extremely valuable to "lock" the values in custom values.
C
Chris Austin
This is a huge issue and really needs to be addressed. The system needs to automatically set the source for newly created contacts and then never automatically overwrite that field unless a campaign automation or API call is requesting it.
The source should never be the name of a form or calendar. For online leads it should use either UTM parameters or a hidden field on the form or a passed parameter in the querystring like ?source=myadvertisement.
For contacts created by inbound phone call, it should set the name of the phone number as the source. This is really important because many businesses generate more leads, and higher quality leads, via phone vs. filling out an online form.
B
Brenda Engelman
Actually locking the whole contact would be useful. Is there a way to prevent contact info from being overwritten by a form or appointment booking? I'm running into an issue where clients book appointments and either mispell their own names with a typo or enter a wrong digit on their telephone. Then all the appointment reminders reflect those typos and reminder texts go out to some random person. It would be nice if the appointment booking could just be tied to the contact without repopulating the information. Even something as simple as "John and Mary" they will enter for the first name field when booking and the existing contact record is compromised. If you don't catch it all future communications using {{contact.firstname}} are incorrect.