Answers.Body: <p>You could do this fairly easily with the <a href="https://civicrm.org/extensions/contact-layout-editor" rel="nofollow noreferrer">Contact Layout Editor</a> extension (assuming you're on CiviCRM 5.x).</p>
  
  <ul>
  <li>Use the extension to remove the existing Communication Preferences block from the Summary page.</li>
  <li>Build a custom block that includes the normal communication preferences fields plus "Do Not Voicemail".</li>
  <li>You'll probably want to remove "Do Not Voicemail" from the custom field block in a similar manner so it doesn't appear twice.</li>
  </ul>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-02-15T11:05:08.037Z
Answers.Text: Thanks Jon.
  
  Will bear this in mind, and discuss with client. Bit wary of doing this through an extension/ customisation. One good future update can cause problems.
  
  Will update my initial question to be more explicit.
Answers.UserDisplayName: Craig Almond
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-02-15T15:59:47.577Z
Answers.Text: The extension is well-supported and written by a member of the CiviCRM core team - but more importantly, it only affects the form level.  In the (very unlikely) event that the extension has a catastrophic failure, you simply disable it, and the field is back where it is now with no data loss.
Answers.UserDisplayName: Jon G - Megaphone Tech
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-02-17T09:26:44.387Z
Answers.Text: Thanks Jon, that is reassuring to know. Our client has seen your original suggestion and is interested in going ahead.
Answers.UserDisplayName: Craig Almond
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-02-14T18:56:59.663Z
Answers.LastActivityDate: 2019-02-14T18:56:59.663Z
Answers.UserDisplayName: Jon G - Megaphone Tech
Body: <p>For the contact field Communication Preferences> Privacy</p>
  
  <p>How difficult would it be to add a new option "Do Not Voicemail"</p>
  
  <p>One of our clients is a counselling service. So this would be useful for them.</p>
  
  <p>They have a stopgap solution usign other custom data fields- but this is in a separate section of the record to the communications info.</p>
  
  <p>What is the process for making requests for this kind of amendment in core?</p>
  
  <p>Is anyone able to pitch a rough cost?</p>
  
  <p>Would this feature be useful to anyone else?</p>
  
  <p>If I can get the client's approval I can look at the Make It Happen process.</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-02-14T18:57:09.497Z
Comments.Text: Maybe not an exact answer but there is a "Voicemail" phone type that suggests that that would be the phone to use for voicemail, so the rule could be that if the phone type is not voicemail then don't leave a message. I've seen it used this way. You could make it more explicit by relabelling the location and phone types as needed.
Comments.UserDisplayName: Demerit
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-02-15T11:01:13.113Z
Comments.Text: A useful suggestion. Will pass back to client. Thank you.
Comments.UserDisplayName: Craig Almond
Tags: <contacts><privacy>
Title: Adding a Privacy Option
ThreadText: # Adding a Privacy Option
  
  (Asked by: username_0 on 2019-02-14)
  
  For the contact field Communication Preferences> Privacy
  
  How difficult would it be to add a new option "Do Not Voicemail"
  
  One of our clients is a counselling service. So this would be useful for them.
  
  They have a stopgap solution usign other custom data fields- but this is in a separate section of the record to the communications info.
  
  What is the process for making requests for this kind of amendment in core?
  
  Is anyone able to pitch a rough cost?
  
  Would this feature be useful to anyone else?
  
  If I can get the client's approval I can look at the Make It Happen process.
  
  **Tags:** contacts, privacy
  
  > **Comments:**
  > **username_1**: Maybe not an exact answer but there is a "Voicemail" phone type that suggests that that would be the phone to use for voicemail, so the rule could be that if the phone type is not voicemail then don't leave a message. I've seen it used this way. You could make it more explicit by relabelling the location and phone types as needed.  
  > **username_0**: A useful suggestion. Will pass back to client. Thank you.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2019-02-14. Score: 4
  
  You could do this fairly easily with the [Contact Layout Editor](https://civicrm.org/extensions/contact-layout-editor) extension (assuming you're on CiviCRM 5.x).
  
  * Use the extension to remove the existing Communication Preferences block from the Summary page.
  * Build a custom block that includes the normal communication preferences fields plus "Do Not Voicemail".
  * You'll probably want to remove "Do Not Voicemail" from the custom field block in a similar manner so it doesn't appear twice.
  
  > **Comments:**
  > **username_0**: Thanks Jon.  Will bear this in mind, and discuss with client. Bit wary of doing this through an extension/ customisation. One good future update can cause problems.  Will update my initial question to be more explicit.  
  > **username_2**: The extension is well-supported and written by a member of the CiviCRM core team - but more importantly, it only affects the form level.  In the (very unlikely) event that the extension has a catastrophic failure, you simply disable it, and the field is back where it is now with no data loss.  
  > **username_0**: Thanks Jon, that is reassuring to know. Our client has seen your original suggestion and is interested in going ahead.  
  
  ---
  
  