Page 1 of 1

lock custom field to dispo

PostPosted: Wed Oct 28, 2020 2:43 pm
by dreedy
Hello everyone,

Is there a way to lock a custom field to dispo?

what i would like to do is create a custom form with several fields in it. one of them being a date and another one being time. When the rep clicks dispo of APPT for instance it would check to make sure that the 2 fields are filled in and finish lead if they are. if not give a warning to rep that they have not filled in the date and time fields.

Thanks for your help.

Re: lock custom field to dispo

PostPosted: Thu Oct 29, 2020 2:01 am
by striker
while creating custom fields you have to enable Field Required

Field Required
If the campaign option allowing required fields is also enabled, this field allows you to force an agent to fill in this field before they can hang up the call. Y will affect all calls, INBOUND_ONLY will only affect calls received by the agent through an In-Group. This option will only work for the following custom field types: TEXT, AREA, DATE, SELECT, MULTI, RADIO, CHECKBOX. Default is N.

Re: lock custom field to dispo

PostPosted: Thu Oct 29, 2020 8:54 am
by dreedy
Thank you striker,

Just curious if the agent/rep doesn't make the appt/sale and goes to dispo it as NI instead of SALE. would the field still be required to continue to next lead?

Re: lock custom field to dispo

PostPosted: Fri Oct 30, 2020 12:03 am
by striker
this field allows you to force an agent to fill in this field before they can hang up the call. ie pressing the Hangup customer button in agent screen

Re: lock custom field to dispo

PostPosted: Fri Oct 30, 2020 6:13 pm
by williamconley
dreedy wrote:Thank you striker,

Just curious if the agent/rep doesn't make the appt/sale and goes to dispo it as NI instead of SALE. would the field still be required to continue to next lead?

Conditional Requirement does not yet exist.

Javascript would be required to either override the required field "unless" the dispo was a match or impose the requirement if the dispo was a match even though it's not actually configured as a required field.