EliseAI SSO & Pre-Launch User Login

EliseAI provisions SSO user accounts using just-in-time (JIT) provisioning. This means user accounts are automatically created the first time a user logs in via SSO. This approach:

• Ensures permissions always align with the your directory and PMS.
• Avoids duplicate or manually misconfigured accounts.
• Enables centralized access control through your existing identity systems.

For this reason, EliseAI strongly recommends requiring users to log in one time before launch.

Why Users Need to Log In Before Launch

Certain EliseAI features require an existing user account for full configuration. These include

• Voice hub routing plans
• Team setup and task routing
• Calendar integrations

You cannot add team members to these features until they have logged in at least once.

Requiring your team to complete a single, one-time SSO login prior to launch allows our team to confirm that everything works correctly before day one. This prevents launch day issues such as missing access, incorrect routing, and incomplete setup.

Why This Is the Lowest-Effort, Lowest-Risk Approach

This is the simplest way to ensure EliseAI is fully ready on day one without introducing operational risk.

A pre-launch login:

• Takes <1 minute per user
• Requires no password (users sign in with their normal SSO credentials)
• Does not require training or product usage
• Dramatically reduces support tickets and confusion at go-live

Training Role for Early Access

For organizations that want to complete SSO setup and account provisioning without enabling full production access, we recommend using a temporary “Training” role during the pre-launch phase.

With this approach:

• All users (or a pilot group) are initially mapped to a limited-access training role.
• This allows for user account creation without enabling full system functionality or operational changes.

This provides several benefits:

• Prevents unintended use of the system before formal training or go-live
• Allows technical validation (SSO, provisioning, routing readiness) without operational risk
• Gives leadership confidence that staff cannot “explore” or change workflows prematurely

At go-live, users will receive final access and role mappings with no additional action required.

Sample Communication to Onsite Staff

Subject: [Action Required] Enable your EliseAI account

Body:

Hi [name],

Please sign in once via SSO at https://app.meetelise.com before [date] (this will take less than a minute). This step automatically creates your EliseAI account so the platform works correctly on day one.
No new password is required—just enter your email, click continue, and SSO will authenticate you.

Best,

[admin team]

Frequently Asked Questions

What if we haven't announced the EliseAI rollout to staff yet?

This is not a blocker. Pre-launch logins do not require a broad rollout announcement or formal launch communication. 

You may choose to begin with a limited user group, such as site leaders, managers, or a pilot cohort, to complete the initial sign-in. This allows your organization to quietly finalize system setup before expanding access.

Will pre-launch sign-in confuse staff before training or go-live?

While we understand this concern, we do not believe this process will cause any confusion. The pre-launch sign-in is not training and does not require staff to use the product. Completing this step actually reduces confusion and risk at go-live, so teams can focus on training and usage without technical issues getting in the way.