Here's what to look for in the June 26th release. 

The guidance in this document is offered for early planning purposes and is subject to change up to the time of release. 

RELATE 

Advisor/Agent Message Templates

Problem Solved: Users cannot create or use message templates and are required to manually input text for each interaction. As a result, more time is spent creating the same message content many times over. 

Expected Value: Message templates will allow users to save time communicating with multiple clients (with the same content) and promote best practices in those communications. Administrators will be able to create and customize message templates, allowing them to create consistent messages that align with their organization's best practices.

Expected Solution: A Message Template library will be implemented to provide an interface where admins can draft, edit, delete, and view message templates. This message template library will show each template card alongside a status indicator of Draft, Pending, Approved, or Denied, as well as a creation date, and edit/delete icons.

Advisors/agents will be able to search, select, and send message templates from the Relate message composer.

Message templates will only be available on the Relate web platform initially.

Who is impacted: Advisor/Agent, Compliance Admin, Marketing Admin, Program Admin
Archiving and Compliance Implications: N/A
Availability: Off by default. To enable this feature, contact your Customer Success Manager.

Platform

Increased API security after creating a token

Problem Solved: API tokens/keys are always visible in the Administration view by clicking Settings in the main side menu, then clicking the Integrations tab. This makes it easy to copy and misuse a token.

Expected Value: Better token security improves the safety of customer data.

Expected Solution: The API Token value will only be shown immediately after it is created. After that, it will be hidden in the list of tokens in the Integrations tab. If access is needed for a new application, a new token must be created.

Who is impacted: Integrator and Program Admin
Archiving and Compliance Implications: N/A
Availability: On for all organizations.

Add Hierarchy filter to Workspaces & Accounts page

Problem Solved: There was no way to filter records on the Workspaces & Accounts page based on hierarchy/region, making it difficult to search for accounts or workspaces in the same hierarchy.

Expected Value: A Hierarchy filter on the Workspaces & Accounts page allows for more useful, finely-tuned searches.

Expected Solution: The Hierarchy filter will be added to the Workspaces & Accounts page, allowing you to see the status of all workspaces and accounts that exist under a selected hierarchy/region. To access the page, in the Administration view, click Organization in the main side menu, then click the Workspaces & Accounts tab.

Who is impacted: Compliance Admin, Program Admin, Integrator
Archiving and Compliance Implications: N/A
Availability: On for all organizations.

More fields can be hidden using Financial PII Detection

Problem Solved: Our current Financial PII Detection feature only detects and automatically hides credit card numbers and doesn’t detect and hide bank numbers, routing numbers, tax numbers, etc.

Expected Value: Detecting and creating alerts for more types of financial PII decreases manual user intervention and mitigates risks that come with handling sensitive information.

Expected Solution: The following types of PII will now be hidden and will generate an alert in Supervision:

• Credit/Debit Number (Credit Card # - 1234)
• CVV (CVV #)
• Credit/Debit Expiry (Credit Card Expiration Date)
• International Bank account number (Int’l Bank Account #)
• PIN (PIN #)
• Swift Code (SWIFT #)
• Bank account number (Bank Account #)
• Routing Number (Bank Routing #)

Who is impacted: Advisor/Agent, Compliance Admin
Archiving and Compliance Implications: More types of financial PII are hidden and generate alerts.
Availability: On for all organizations.

Data & Analytics

Report descriptions visible in Hearsy Desktop

Problem Solved: There are no in-app descriptions of the fields used in the Content, Compliance, Enterprise Management, and Performance Breakdowns reports that are available to admins. Admins have to refer to Hearsay documentation to get these descriptions, which causes some friction in their experience.

Expected Value: Administrators will get descriptions for each field in the Report pages, relieving them of the need to refer to Hearsay documentation for this information.

Expected Solution: Administrators will see a description of the fields by hovering over the headers in their reports. Additionally, the color of the report headers will be changed to improve its look and feel.

Who is impacted: Compliance Admin, Marketing Admin, Program Admin
Archiving and Compliance Implications: N/A
Availability: On for all organizations.

New Breakdown by Sites report will provide performance measures for individual Sites

Problem Solved: Administrators do not have visibility of the business performance of individual Sites. They only have data on Sites performance at an aggregated level for all Sites.

Expected Value: The new Breakdown by Sites report will allow administrators to list and compare key business measures of individual Sites.

Expected Solution: The new Breakdown by Sites report will be implemented to provide the following measures for each Site:

• Site ID
• Site name
• Site URL
• Workspace ID
• Workspace name
• Number of sites publishes
• Number of events publishes
• Number of visitors
• Number of new visitors
• Number of returning visitors
• Number of Leads
• Lead conversion rate%
• Number of Page Views
• Average page views per visitor
• Bounce rate%
• Average session duration

Who is impacted: Marketing Admin, Program Admin
Archiving and Compliance Implications: N/A
Availability: On for all organizations.