Started in CA-170.
The issue with the Voice benefit is that it is currently a schizophrenic solution .. Here are the problems:
Before the org dashboard was launched there was one custom field - Mail Codes – that includes Voice (yes or no), that handled Voice subscriptions.
The org dashboard now handles assigning the Voice benefit by setting a relationship “Receives Voice subscription from”. But this doesn’t handle individual members.
Besides consistency, I'm not sure there are any benefits to using a Relationship to model the Voice Subscription for individuals. It's not really a problem, but we need an organization for the Contact to be related to. This would have to be a pseudo-contact such as "Voice Subscribers".
A Group is arguably the "CiviCRM way" of approaching this. It allows for, and normalizes, the different ways of modeling the subscription.
The Voice (Explicit) Group
Group(s) In The Voice ...AND... Group Status 'Added' ...AND... Is a current member ...AND... Primary Members Only
Is a current member ...AND... Primary Members Only ...AND... Contacts with a Relationship Type of: 'Receives Voice subscription from'
!( Do Not Mail = 1 ) ...AND... Primary Members Only ...AND... Membership Status In New, Current, Grace ...AND... Voice = Yes