Touchpoints

Driving Omnichannel Operations through Configurable Touchpoints

Touchpoints are Thalamus's tool for identifying the origin of each event or action, as well as the data that enters the system. This functionality transforms Thalamus into a robust database and a quick-response service, making it the core for operations that extend beyond a single point of contact. By registering not just the action and the data, but also the origin of the information, Thalamus provides a detailed record of the data's source.

There are no default touchpoints; all of them must be created and configured beforehand. Their properties, such as password protection or login session duration, can be adjusted. A touchpoint can represent a digital medium (e.g., a website), a physical one (e.g., a store), or an integrated service. For example, some touchpoints are integrated through a REST API, while others are utilized through a Call Center application.

Any external provider implementing and communicating through Thalamus will do so via one or multiple touchpoints, depending on the project's requirements. This architecture is ideal for projects where clients interact with the system through various channels, including websites, mobile apps, points of sale, or call centers.

How to Create and Edit a Touchpoint

A touchpoint can be created and managed within the Thalamus Back Office (BO) platform. This functionality is located under the "Configuration" section.

Essential Considerations for Touchpoint Configuration

• Touchpoint Type: This field designates the type of touchpoint and its intended use. The available configurations are REST (for integrations with external systems via a REST API) and Call Center (for interfacing with the Call Center application).

• Name: This mandatory field provides a clear identifier for each touchpoint.

• Code: A mandatory and unique identifier. Along with the token, it is a key credential for accessing the REST API services.

• Token: An automatically generated credential that can be regenerated on demand. Both the code and the token are mandatory for developers to access the REST API services

• Maximum Invalid Login Attempts: This field sets the maximum number of failed login attempts a touchpoint will permit before a user is restricted.

• Duplicate Strategy: This setting defines the system's protocol for managing conflicts that arise when a new record's primary fields match an existing one.

• Countries: This setting specifies the countries where the touchpoint will be active and available for use.

• Brand Families: This field specifies the brand families that are authorized to operate on the touchpoint.

• Session Time (in minutes): This field defines the duration, in minutes, of a user session.

• Minimum Validation Status for Login: This setting defines the minimum validation status a party must have to be granted login access to the touchpoint.

• Age Validation: This field defines the method for age validation.

Additional Considerations

Tokens and Codes

Both the code and the token are mandatory for the developer to successfully interact with the REST API services. These credentials are a prerequisite for authentication and authorization, ensuring secure and validated access to the API endpoints.