Skip to main content

Configuring the Fenergo Portal Outreach Functionality

Portal Outreach Journey Configuration

Configuring outreach journeys can be done via the Journey Builder. To allow the portal user to see an entire journey, simply set the channel type in journey details to External. Steps to create an outreach stage in a journey:

  1. In Journey Details, set the channel type to “Internal & External”
  2. Within each stage of a journey, there will be an option to set the "Stage Channel"
  3. Add QuickLink stage to an "Internal" stage to review and update Portal users with access to this entity.
  4. Set the stage that should be available in Portal to “External – Portal”
  5. The outreach icon will be visible on the stage to indicate that it is set to external
  6. The outreach stage cannot be initiated in parallel with previous stage. Subsequent stages can be initiated in parallel with the outreach stage.
  7. Multiple processes are now supported within the outreach stage. If a process does not contain the “Create Outreach Snapshot” task or “Import Outreach Snapshot”, the Task completion order of “In Any Order” may be selected.

Portal Outreach Journey Configuration

Parallel Outreach Tasks

The outreach stage now supports multiple processes running in parallel. If a process does not include the “Create Outreach Snapshot” or “Import Outreach Snapshot” tasks, the task completion order can be set to "In Any Order". This configuration allows users to complete tasks flexibly, either as needed or when all required information becomes available, streamlining the workflow and accommodating more efficient task management.

Enabling Different Roles to Complete Different Tasks

Journey Configuration-

  • Set the journey Channel Type to Internal and External.
  • Add an External (Outreach) Stage to the journey.
  • Put the Stage Channel to External-Portal.
  • Within this External Stage, click on the Assigned Portal Role dropdown.
  • Select the role you would like to assign the tasks in this stage to.

Note: If no role is assigned, all linked users will receive the outreach email notification.

Any users who do not have the assigned role will not be able to view or update these tasks in Portal as they haven’t been assigned to them.

Only users linked to this role (using Portal User Management or the Quick Link Task) and who have the assigned role will be capable of seeing and completing the tasks in this stage in the Portal.

Important Notes
  • If an Outreach stage is not assigned to a Portal Role, all roles and portal users will be able to complete the outreach tasks.
  • Please ensure that each Outreach stage is properly configured and assigned to the appropriate user or role to avoid any unintended access.

Enabling Different Roles to Complete Different Tasks

Other Scenarios:

  • When the Assigned Portal Role is left as an empty blank field: All portal users can view the tasks as no particular role has been assigned to it.

Note: Changes made to a stage and its assigned users will only affect the newly triggered journeys after this.

When a user does not see the tasks in an external stage in Portal, it means that their role has not been assigned to this task. They will see the below screen -

Enabling Different Roles to Complete Different Tasks

The second functionality introduced by the feature is Email Notifications.

If a user’s role is assigned to a task in the Outreach Stage, once the Snapshot task occurs, the user will receive an email notification.

For the user to receive an email notification-

  • The user must be linked to the entity
  • The “Receive Outreach Email Notification” toggle must be toggled on.

Note: This toggle is located in the Portal Configuration User Roles under the Email heading.

Enabling Different Roles to Complete Different Tasks

A user will not receive an email if:

  • They are not linked to the entity.
  • They have the Receive Email Notification toggle off.
  • They are not the role assigned to the task.

Outreach Template

This introduces a second outreach email template to the Portal Configuration section. The template will be named, “Outreach Email 2”, with the existing email template being renamed from “Outreach” to “Outreach Email 1”.

This additional template allows for a configure of what email content is to be sent to a portal user. A client may wish to send a different email template during different journeys (For example; Onboarding vs Review) or to different user roles interacting with a journey.

The client can specify the desired email template in the Outreach Stage and send the email content that they wish to.

Note: the email itself will be sent to the users with the role assigned to the Outreach Stage.

A dropdown has been added to the “ Create Outreach Snapshot” task, allowing the configurator to choose between ‘Outreach Email 1’ and ‘Outreach Email 2’. ‘Outreach Email 1’ is the default.

New Outreach Template

To configure this within the Journey Builder:

  • Add an Outreach Stage to the Journey.
  • Add a Capture Outreach Snapshot task.
  • Navigate to the Outreach Template dropdown.
  • Select Outreach Email 2 or Outreach Email 1

To customize the template, go to Portal Configuration and scroll to the Portal Emails section.

New Outreach Template

Outreach Requests Dashboard

The Outreach Requests Dashboard is designed to allow Portal users to focus only on entities that have open requests. The key column in the dashboard is the Entity Name, the other columns are configurable so can be adjusted based on user requirements.

To configure the columns:

  • Navigate to Portal Dashboards
  • Click on the Requests Dashboard
  • Type: Outreach Requests
  • Select values from the Company Fields dropdown and Individual Fields dropdown
  • Click Save

Configuring Requests Dashboard

Linking the Portal User to a Journey:

  1. Navigate to the "Create Outreach Snapshot" task on an Outreach stage.

  2. Enable the "Link Journey" Toggle if you wish to link the portal user's journey.

    If the Link Journey toggle is enabled, the journey will be assigned to all Portal users associated with the Legal Entity and have the assigned role for the outreach stage. If no role is assigned to the outreach stage, no journeys are linked to any user.

  3. The journey will automatically link to the portal user's entity, allowing them to view the outreach requests.

Link Journey Toggle

Note: Assigning an Outreach stage to a role can be done via clicking on the Portal stage in Journey Builder and selecting a role from the Assigned Portal Role dropdown.

Assigned Portal Dropdown

Unlinking the Portal user from the Journey:

  1. Navigate to the "Import Outreach Snapshot" Task on an Outreach stage.
  2. Enable the "Unlink Journey" Toggle if you wish to unlink the journey.
  3. The journey will be deleted for the portal user, and the outreach tasks will no longer be visible.

Unlink Journey Toggle

Note: These toggles are disabled by default.

Important Notes

Once a portal user is linked to an entity, they will retain access to it - even if the entity no longer appears on the Requests Dashboard.

This eliminates the need to re-link the entity in the future, but it also means that the user can continue to access the entity's profile directly, even when it’s no longer actively displayed on the Outreach Requests page.

Trader Portal:

When using the Trader Portal:

  • The Link Journey toggle will not re-link an already linked journey.
  • The Unlink Journey toggle will remove the journey for the portal user and will not be visible in the Standard portal and Trader portal.
Important Notes

Cancellation and Referral Scenarios

Outreach request links when journeys are cancelled or are older than 90 days will be automatically removed.

If a journey has been referred to a previous stage, the portal user will be presented with an information screen indicating that the request is no longer valid and will be removed from their dashboard.

This feature introduces enhanced validation for the Related Party task within the Portal. It allows configurators to enforce mandatory review for related parties and enables portal users to clearly see the completion status of each Related Party. Clients can enable or disable this validation using the "Enforce Mandatory Related Party Data Capture" toggle.

To enforce the mandatory Related Party Data Capture:

  • Login to Fenergo.
  • Go to the Journey Builder and select the desired Journey.
  • Click on the Related Party Task.
  • Enable the Enforce Mandatory Related Party Data Capture toggle.

Data Completion Checks Toggle

When this toggle is enabled, a user will be required to review all existing related parties before completing the related party task within the Portal.

info
Notes
  • This toggle is disabled by default.
  • This toggle will only be visible when Channel Type is External, or Internal/External with the current Stage being External.
  • The toggle will not be visible when Channel Type or Stage is Internal.

Configuration

In order to have Related Parted Documents included in the Related Party Outreach tasks the "Enable Related Parties Documents" switch on the task properties must be enabled. This will be set to disabled by default.

Configuration

For the Outreach Existing Related Parties task :

  • Document Requirements will be visible
  • Document linked to requirements will be available to view or download
  • Additional documents can be linked to a requirement
  • Linked documents can be deleted.

For the New Related Parties task:

  • Document Requirements will be visible once the Related Party is created
  • Document can be linked to requirements and metadata added
  • These documents will be available to view or download
  • Linked documents can be deleted.
Note:

The New Related Party task supports multiple configurable categories, beyond the standard categories available in Fenergo Tasks.

Due to a current technical limitation, documents stored in the Related Party ID&V (Identification & Verification) category are not displayed in the Portal. Please ensure that documents are uploaded to another category to guarantee visibility.