There are many cost & time saving benefits associated with keeping your Ocrolus integration as efficient as possible. Since your Ocrolus integration depends on listening to all loan-level activity in your Encompass instance, the best way to refine your workflow is by having more control over the loan activity sent to Ocrolus. Every loan attachment sent to Ocrolus adds time to the overall indexing process regardless of being a rejected, unknown, or a duplicate.
To refine your workflow:
- Limit the number of loans sent to Ocrolus
- If there are any loans which do not require processing or underwriting, it is helpful to exclude these from Ocrolus processing. We recommend working with the Ocrolus support team to refine our webhook filter logic listens for specific loan files. Loan-level filters can be set on any Encompass standard field (i.e. Creation Date), Milestone, Pipeline, Loan Folder, or Loan Channel.
- Limit the number of attachments sent to Ocrolus
- As a best practice, we recommend utilizing a dedicated document container for Ocrolus processing within the loan E-Folder so that only attachments which need to be processed get sent to Ocrolus. If there are attachments coming from unassigned or a combination of document containers, it is likely there are extra/unnecessary attachments getting processed in Ocrolus. By designating a specific document container (e.g. “Processing Required”), Ocrolus will only pick up attachments in that container.