I would like to know how your organization handle cases where customer A and customer B have a subscription together but the subscription they share is on customer A's record. Does your organization track such information in special requests at the lineitem level, or in associations, or somewhere else? What's the good and/or bad of doing it your way?We want to start tracking these cases with an eye toward treating customer B as a subscriber, and would like to hear your perspectives.
Thanks very much.Matt
We have an association type of "seat with" and it throws a flag in the header of the record. The actual seating request for the subscription is usually placed in the order notes of the renewal/new order, but the flag lets the staff know that they have to coordinate with at least one other account.