Menu
Outcome Testing Teams (OTTs) are teams within financial services organisations that are responsible for evaluating the effectiveness of their policies and procedures in meeting regulatory requirements and ensuring that customers are treated fairly. These teams typically report to the compliance or risk management function within the organisation, but may also work closely with other departments such as customer service, product development, and marketing.
Their main role is to perform testing and audits to ensure that the policies and procedures of the organisation are meeting the regulatory requirements in terms of consumer protection and fair treatment, and also to identify any potential issues or areas for improvement. They review the outcomes of different activities of the organisations and test the compliance of business practices with the relevant rules and regulations. They analyse data, assess the customer experience and conduct testing, examining the customer journey through different touch-points and interactions with the business.
OTTs use a variety of testing methods, such as mystery shopping, file reviews, and other forms of testing, to evaluate the customer experience and identify areas where improvements could be made. The results of the testing are then used to inform the development of new policies and procedures, or to make changes to existing ones, to ensure regulatory obligations are met.
Outcome Testing Teams play an important role in ensuring financial firms are providing fair treatment to their customers, in compliance with regulations by assessing the effectiveness of policies, procedures and the overall customer experience, identifying areas of improvement and making necessary changes.
Cookie | Duration | Description |
---|---|---|
__cf_bm | 30 minutes | This cookie, set by Cloudflare, is used to support Cloudflare Bot Management. |
__hssc | 30 minutes | HubSpot sets this cookie to keep track of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. |
bcookie | 2 years | LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser ID. |
lang | session | This cookie is used to store the language preferences of a user to serve up content in that stored language the next time user visit the website. |
lidc | 1 day | LinkedIn sets the lidc cookie to facilitate data center selection. |
Cookie | Duration | Description |
---|---|---|
__hstc | 1 year 24 days | This is the main cookie set by Hubspot, for tracking visitors. It contains the domain, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). |
_ga | 2 years | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. |
_ga_LJ9092N12M | 2 years | This cookie is installed by Google Analytics. |
_gat_gtag_UA_156387185_3 | 1 minute | Set by Google to distinguish users. |
_gcl_au | 3 months | Provided by Google Tag Manager to experiment advertisement efficiency of websites using their services. |
_gid | 1 day | Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. |
CONSENT | 2 years | YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data. |
hubspotutk | 1 year 24 days | This cookie is used by HubSpot to keep track of the visitors to the website. This cookie is passed to Hubspot on form submission and used when deduplicating contacts. |
Cookie | Duration | Description |
---|---|---|
bscookie | 2 years | This cookie is a browser ID cookie set by Linked share Buttons and ad tags. |
IDE | 1 year 24 days | Google DoubleClick IDE cookies are used to store information about how the user uses the website to present them with relevant ads and according to the user profile. |
test_cookie | 15 minutes | The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies. |
VISITOR_INFO1_LIVE | 5 months 27 days | A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface. |
YSC | session | YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages. |
yt-remote-connected-devices | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
yt-remote-device-id | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
Cookie | Duration | Description |
---|---|---|
AnalyticsSyncHistory | 1 month | No description |
AWSALB | 7 days | AWSALB is a cookie generated by the Application load balancer in the Amazon Web Services. It works slightly different from AWSELB. |
browserupdateorg | 7 days | No description available. |
li_gc | 2 years | No description |
UserMatchHistory | 1 month | Linkedin - Used to track visitors on multiple websites, in order to present relevant advertisement based on the visitor's preferences. |