Third Party Recipients (TPR) in Blend

Modified on Fri, Apr 11 at 4:20 AM

Blend offers the ability to manage and send Follow-ups to Third Party Recipients (TPRs). As Lenders have expanded usage of Blend Follow-Ups and Tasks beyond borrowers, this feature is intended to offer more formalized support for adding Third-Party Recipients (TPRs) and issuing follow-ups to these user types within Blend.

 

Overview

TPRs are able to complete custom follow-ups through a Blend-built TPR portal without the need for the TPR to have lender credentials or an account.

TPR user types can be added to a loan by a Loan Officer in the Lender Workspace. Once added, they will receive an email with directions to access Blend’s new TPR portal, and will be able to complete the assigned custom follow ups.

There are two categories of TPR user types - and two similar flows included here:

  • Single Tenant: a third party who only has tasks for loans at a single lender.
  • Multi Tenant: a third party who has to complete tasks across multiple loans across multiple lenders - the primary difference is that Multi Tenant TPRs will have a Lender selection screen after logging in.

 

Third Party Type

The TPR experience varies on whether the user type will need to complete follow-ups across multiple lenders, or if the relationship is tied to a specific lender.

Single Tenant

Multi Tenant

  • Attorney in Fact
  • Authorized Representative
  • Authorized Third Party
  • Gift Donor
  • Non-Title Non-Spouse Ownership Interest
  • Non-Title Spouse
  • Property Seller
  • Settlor
  • Settlor Trustee
  • Spouse
  • Title Holder
  • Title Holder Settlor Trustee
  • Title Holder Trustee
  • Trustee
  • Other
  • Unspecified
  • Appraiser
  • Builder
  • Hazard Insurance Agent
  • Landlord
  • Real Estate Selling Agent
  • Real Estate Listing Agent

To learn more about the Third Party Type experience, please refer to the Release Notes Custom Follow-Ups for Third Party Recipients with Blend Sign.

 

Adding a Third Party Recipient

  1. In the Application tab, click the Third Party Recipients link under Borrower information.
    blend_lender_tpr.png
  2. Click Add recipient.
    blend_lender_add_recipient.png
  3. Fill out the Third party details then click Save.
    blend_lender_tpr_details.png
    The recipient will receive an email to activate their account and access the documents.blend_tpr_activation_email.png

exclamation_mark_triangle.png Note:

  • Adding a TPR using the email address of a lender with an account in Blend will result in an unexpected error. Please use a different email.
  • An "Email already in use" message will appear when adding a TPR that has a borrower application in Blend. This is an informational message and you may proceed to add the TPR.

blend_lender_tpr_email_already_in_use.png

 

Edit, delete, or add another Third Party Recipient

Lenders can edit, delete, or add another Third Party Recipient from the Third Party Recipients link.

  1. Click the Third Party Recipients link in the Borrower information section in the Application tab.
    blend_lender_tpr.png
  2. In the next screen, you can edit, add, or delete a Third Party Recipient.
    blend_tpr_manage.png

exclamation_mark_triangle.png Note: TPRs with requests assigned cannot be deleted. If a TPR needs to be removed, please contact Blend Support for assistance.

blend_lender_delete_tpr_error.png

TPR has manually assigned assigned loan requests. Cannot delete.

 

Send Follow-ups to a Third Party Recipient

Loan Officers can create and send Follow Ups in Blend Sign for Third Party Recipients.

  1. Add a Follow-Up.
  2. Once the Follow-Up has been created, Loan Officers can select the third party to receive the request as well as the borrower if needed.
    blend_lender_follow_up_tpr.png
  3. Set up e-Signature for Blend Sign if needed and proceed to send the request.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article