Key Terms of the Agenium Platform

In order to understand the Agenium Platform better here is a list of frequently used terms that are used by all members of the Agenium team.  

Account Access

Clients can have many accounts and users can be granted access to accounts on a individual basis

Account Number

Each client can have several accounts or "products". The account number lets the user know which product they are working with (ex: a final expense app or a pre-need app) the account number is always four (4) digits and is included in the Case Number

Application

The term Case, Order, Interview, and Application can be used interchangeably in the Agenium system (See Case)

Bug

A bug is when the system/platform is not performing as intended. For example: a question should be showing in an interview but it is not. Bugs should be reported to the helpdesk immediately

Case

The term Case, Order, Interview, and Application can be used interchangeably in the Agenium system. Clients use the Agenium platform differently so a case may be a tele-interview, an e-app or an underwriting opportunity, to name a few options. Typically clients bill upon completion of a case in the production environment.

Case Number

A unique identifying number that will refer to a specific case in an environment. The format of the case number is ###-####-###### where the:

### = the Client Number

#### = Account number

###### = Case Identifier.

The same case number can be found in different environments (ex. Prod, Demo, Stage) but they will be separate unrelated cases.

Case Summary 

The case summary allows users to review a case without having to edit the interview.  This can include all answered questions, notes, documents etc. Different roles have different permissions so not every user will have access to every feature on the case summary

Client Number

Each client at Agenium is assigned their own unique client number. This number is three (3) digits and will be the same across environments. The client number is included in every case number

Configuration

The ability to change the logic of the platform without coding. Many parts of the platform are customizable and can be configured to provide a better experience for the client or user. Example: An account can be configured to apply underwriting labels automatically. Configuration is done either by an Implementation Team at Agenium or a Self-Service Configurator.

Configurator 

Someone who makes code-free changes in the Agenium platform

Customer Success Team

The CS team focuses on supporting customers after they have products go live on the Agenium platform. The CS team includes the helpdesk, training and account managers

DEV Team

The DEV team supports Agenium as back end users. They do all coding for the platform including fixing bugs and improving the platform with new features. The DEV team may consist of developers, quality assurance and UX/UI team members.

Environment

The Agenium platform has many environments that users can interact with that all have the same functionality but different uses. For example, the Production environment is used for billable cases and has the highest level of security, the Demo environment is used to show the platform off to new potential clients

Environment - Production

The environment that is used for real, live cases. It does contain personally identifiable information (PII), can incur third party integration costs and has the highest level of security precautions. This environment's access is limited and follows SOC 2 compliance.

Environment - Stage

The environment that is used to make products and test them before moving them into production. There is no personally identifiable information (PII) and should not be used for billable cases

Environment - Training

The environment that is used for training purposes. There is no personally identifiable information (PII) and anyone can have access to it.

Feature Request

A feature request is when a user would like to see something added or changed in the Agenium platform. There is no guarantee that a feature request will be implemented by the DEV team, but they will prioritize the request and investigate if it makes sense to create/change the feature

Helpdesk

A resource for all users to get help for the Agenium platform. The helpdesk can assist with many issues such as: end user questions, configuration requests and bugs.

Helpdesk Ticket

Tickets are used to track issues and requests sent to the helpdesk by users and clients. Tickets can be manually created, or automatically created when a user emails the helpdesk at Helpdesk@Agenium.ai

Implementation Team

A team made up of Agenium employees that configure products for clients. Can consist of a project manager and builders and may vary in size. Typically, an implementation team will build a product from start to finish for a client

Integration

An integration allows the Agenium platform to talk to third party software and products.  Initial set up of an integration requires DEV work and therefor must be approved by the DEV team but once an integration is coded into the platform any client may use it. Integrations with third parties may require separate contracts and costs with that third party (example: IRIX or Lexus Nexus). 

Interview

The term Case, Order, Interview, and Application can be used interchangeably in the Agenium system (See Case)

Mapkey

Mapkeys are data elements that the system can use in many ways. Mapkey data can come from an application, an API or even a third party through an integration. The platform can be configured around mapkeys . For example: If an applicant answers that they use tobacco, their tabacco status can be tied to a mapkey. This could then be used to customize follow up questions or influence the underwriting decision

Multi-Factor Authentication (MFA)

An additional level of security that is used by Agenium when users are signing into the platform. This will usually require a one-time passcode being sent and confirmed by the user logging in

Order

The term Case, Order, Interview, and Application can be used interchangeably in the Agenium system (See Case)

Role

A role defines the permissions that a user has in the platform. Roles are universal so anyone with the same role will have the same permissions no matter what accounts they have access to

Section

Interviews can have many sections to help organize the questions for a positive user experience. For example, all questions about the owner can be in an "Owner Section" and all underwriting questions can be in the "Underwriting Section". Sections can be configured to further improve the user experience, for example: a section can be hidden or shown to certain roles or based on previous answers. 

Self-Service Configurator

A user who is not an employee of Agenium and can make changes to their company's individual accounts. They must complete the Agenium Self-Service Configurator training before getting permission to make changes in the platform.

Single Sign On (SSO)

Users' credentials are managed by a third party but have been set up to be able to log into the Agenium platform without a password. This feature is set up by the DEV team

User

An individual who has access to the platform

User Management

User creation, deletion and platform access all fall under user management. Each user is assigned a role as well as access to accounts, this can be updated as needed

Virtual Mapkey (VMK)

Virtual Mapkeys are data elements that did not come from outside sources (such as an API or Manual Entry). Virtual Expressions are used to manipulate already existing data within the Agenium platform.  For example: a VMK may reference an applicant's birth date (mapkey) and calculate how old they are.