When a contact is just a contact...
-
I've done a search in the forum and through the AppColl documentation, but haven't found an answer to my question, so assistance from Support or the community would be most appreciated!
I have created a Role:Client record for a business entity. I want to create a contact role for the CEO, who is our main point of contact for the client. The CEO is neither an inventor nor a "manager" nor a client, per se. How do I relate the CEO to the Client? I want to be able to use separate records, so that it's easier to manage if the contacts change for the client, or if there are multiple contacts. So far, I've created the contact record as a "Manager" or "Other", and have been using the "Primary Contact" field with in the Client record, or sometimes the "Add Contact" field, but it just doesn't work as well as the other role types.
-
@GeorgeJ4336 Thanks, George. That's a great idea! I'll likely use that, going forward. Thank you!
-
@TarC6989 I generally use Role=Employee in these situations. "Employee" seems to be generic enough to cover anything that isn't one of the specific roles, such as Paralegal, Docketing Manager, Attorney, or Corporate Counsel. Sometimes, I use Role=Other. I have not used Role=Manager. I figured I would use that to keep track of managers of inventors, if that ever becomes useful. So far, it has not.
As you noted, a Role=Client contact has a field called "Primary Contact." That is how I link my clients to their respective primary contacts. In some cases, the primary contact is a Role=Paralegal. In other cases, the primary contact is an Inventor or (in case of a CEO) an Employee. This has worked well for me, for example in generating reporting messages using a "To" address of:
{Matter.Client.PrimaryContact.First} {Matter.Client.PrimaryContact.Last} <{Matter.Client.PrimaryContact.EmailNoCC}>
and a salutation of:
Dear {Matter.Client.PrimaryContact.First}:
What about your arrangement has not worked well for you?
-George
