When linking contacts to a matter in Clio, there are two ways to do it:
1. Using a "Contact" custom field.
2. Using the "Related Contacts" feature.
This article will explain how to appropriately use each of the two methods above. This information is a summary of best practice information commonly discussed on the Clio Co-Counsel Facebook page.
1. Using a "Contact" custom field.
2. Using the "Related Contacts" feature.
This article will explain how to appropriately use each of the two methods above. This information is a summary of best practice information commonly discussed on the Clio Co-Counsel Facebook page.
Almost Always Use Contact Custom Fields
If you are not sure which of the following methods to use, you should generally choose a "Contact Custom Field."
Contact Custom Fields
Contact Custom Fields are the ideal way to link most contacts to a matter. Contact Custom Fields should be used when you have an expected type of contact.
To create a contact custom field, you will log into Clio and then go to Settings > Custom Fields. From here, you will provide a name for the custom field (such as "Father" or "Guardian1") and will choose "Contact Select" as the field type.
Once the Custom Field is created, when you edit a matter in Clio, you can provide a value from the "Custom Fields" section. Once you do, it will show up on the matter dashboard.
Contact Custom Fields are designed to be used in document automation, reporting and more.
To create a contact custom field, you will log into Clio and then go to Settings > Custom Fields. From here, you will provide a name for the custom field (such as "Father" or "Guardian1") and will choose "Contact Select" as the field type.
Once the Custom Field is created, when you edit a matter in Clio, you can provide a value from the "Custom Fields" section. Once you do, it will show up on the matter dashboard.
Contact Custom Fields are designed to be used in document automation, reporting and more.
Related Contacts
Related Contacts should only be used to link unexpected, rare and infrequently used types of contacts. For example, if you have a particularly unique family law case and you need to capture "Mother's Boyfriend's Sister" this would be a good use of related contacts.
Contacts in Faster Suite
Contact Custom Fields are generally used in Faster Suite because:
1. Contact Custom Fields are designed for reporting and data export. This works great with Faster Suite.
2. It is "Easy" to know the list of all contact custom fields. If you have 10 contact custom fields that are used 10,000,000 times in Clio, Faster Suite only has to ask Clio for the 10 contact custom fields. This keeps Faster Suite Fast!
3. Contact Custom Fields represent contacts that are expected so it makes sense that we should expect to work with them.
Related Contacts are generally not used in Faster Suite because:
1. It is "Hard" to know the list of all different types of related contacts. For example, if you have 10 commonly used types of "Related Contacts" that are used 10,000,000 times in Clio, to get the original list of 10 items, Faster Suite actually has to ask Clio for all 10,000,000 items and then remove duplicates them. This would really slow down Faster Suite!
2. Related Contacts represent types of contacts that are unexpected to it makes sense that we should not expect to build workflows around them.
1. Contact Custom Fields are designed for reporting and data export. This works great with Faster Suite.
2. It is "Easy" to know the list of all contact custom fields. If you have 10 contact custom fields that are used 10,000,000 times in Clio, Faster Suite only has to ask Clio for the 10 contact custom fields. This keeps Faster Suite Fast!
3. Contact Custom Fields represent contacts that are expected so it makes sense that we should expect to work with them.
Related Contacts are generally not used in Faster Suite because:
1. It is "Hard" to know the list of all different types of related contacts. For example, if you have 10 commonly used types of "Related Contacts" that are used 10,000,000 times in Clio, to get the original list of 10 items, Faster Suite actually has to ask Clio for all 10,000,000 items and then remove duplicates them. This would really slow down Faster Suite!
2. Related Contacts represent types of contacts that are unexpected to it makes sense that we should not expect to build workflows around them.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article