> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/enterprise-guide/training-and-support.md).

# Training and Support

<figure><img src="/files/wRIXuwhCrMdQOzJngKwN" alt=""><figcaption></figcaption></figure>

Keeper Security provides business customers with training, onboarding and individual end-user support through email, phone, and web-based Zoom sessions.

## Support Hours

Monday through Friday: 24x5

Saturday and Sunday: 8:30 a.m. - 5 p.m.

## Onboarding and Training

Business customers who purchase Keeper's **Onboarding and Training** package are provided an unlimited number of dedicated user training sessions via webinars and individual Zoom sessions. Business customers are also provided a dedicated account manager in US, EU or JP regions.

#### **Chicago, IL (US) and El Dorado Hills (CA)**

This support team covers customers in the following territories: U.S., Canada, Australia, South America, and Asia-Pacific.

#### **Cork, Ireland (EU)**

This support team covers customers in the following territories: Europe, Middle East, and Africa.

* See our [Business Support packages](https://www.keepersecurity.com/professional-services-business.html)

## Ticket Submission

Business customers can submit support tickets through our website:\
<https://keepersecurity.com/support>

## Contact List

| Contact                     | Email Address                         |
| --------------------------- | ------------------------------------- |
| Business Support Team       | <business.support@keepersecurity.com> |
| Sales Team                  | <sales@keepersecurity.com>            |
| Government Sales            | <govsales@keepersecurity.com>         |
| Security Team               | <security@keepersecurity.com>         |
| Commander Team              | <commander@keepersecurity.com>        |
| PAM Engineering Team        | <pam@keepersecurity.com>              |
| Forcefield Engineering Team | <forcefield@keepersecurity.com>       |
| Customer Success Team       | <success@keepersecurity.com>          |
| Japan Office                | <infojapan@keepersecurity.com>        |

## Implementation and Integration Support

Business and Enterprise customers will receive standard implementation support for onboarding users and guidance regarding the integration of Keeper Bridge, Single Sign-On (SSO) and Advanced Reporting and Alerting Modules.

Customers engaged in a Proof of Concept (PoC) with Keeper will receive implementation support at the discretion of the account manager and the size of the opportunity.

Any custom integration or development required beyond the pre-built scope of the Keeper software will be quoted by your dedicated account manager as part of a professional services agreement.  This includes Advanced integration, custom software development, assistance with Keeper Commander APIs and other third-party integrations.&#x20;

## Support Process and SLA

#### Level 1 - Support Representative

All support tickets received are placed into the Level 1 support queue and routed by Keeper to the appropriate level. The support ticket will be handled by either Keeper Security business support team members in Chicago, IL, USA or Cork, Ireland, according to the time of day received.

A written response acknowledging a Level 1 ticket will be provided within one (1) business day of the time received. If a support ticket is deemed urgent (e.g., service outage, degraded performance or accidental administrative error occurrence), Keeper Security’s support team will immediately escalate the ticket to Level 2 or Level 3 support. If a support ticket is not urgent, the Level 1 support team member(s) will handle the ticket through its resolution.

Level 1 tickets will be resolved within two (2) business days of acknowledgement, as long as the customer is responsive. If Keeper determines the Customer has not provided timely responses to the ticket, the aforementioned resolution commitment is void.

#### Level 2 - Support Engineering

Level 2 tickets will also be acknowledged within one (1) business day of receipt. Cases will not be escalated until Level 1 is no longer able to assist. Once a case has been escalated to Level 2, it will be managed directly by one of KSI’s Support Engineers.

If the case pertains to bugs, advanced single sign-on (SSO) provisioning, Active Directory and Keeper’s Developer API, then it shall be escalated to Level 3.

#### Level 3 - Engineering

Level 3 tickets will also be acknowledged within one (1) business day of receipt. Level 3 cases will be directly managed by Keeper Security's Director of Engineering. This scenario would pertain to any critical bugs or critical blocking issues.

Support tickets that require additional engineering assistance such as Active Directory or SSO implementation are escalated to Level-2 support engineers located in Chicago, IL USA, Cork, Ireland and El Dorado Hills, CA USA.

If Keeper software updates are required to address a customer issue, the ticket will be escalated to the Director of Engineering. The Director of Engineering will coordinate any software updates with the customer, and involve the relevant software development team.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.keeper.io/enterprise-guide/training-and-support.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
