Obi by PI: Frequently asked questions

No. Obi must be either enabled or disabled at the organization level. It cannot be turned on/off on a per-user basis.

Obi works with PI Inspire, PI Hire, PI Design, and PI Diagnose.

No. While an active Inspire subscription is required to enable Obi for your organization, an employee does not need module access to Inspire to use Obi.

At this time, there are no plans to incorporate Obi into Perform.

Yes. Once your organization receives access to Obi, you will start to receive emails from our team to let you know.

The most likely reason is that either:

Assuming your organization has Obi enabled, tell the individual user to add "/pi" to the webpage they're on (e.g., app.predictiveindex.com/inspire/client/ would become app.predictiveindex.com/pi/inspire/client/).

Not yet. A "User Profile" (where users can provide context as to who they are) as well as conversation memory are in consideration for our Q3 roadmap.

Yes. Learn how to add organizational context to Obi.

You can add the following items:

Learn how to add organizational context to Obi.

When users are on a specific page (e.g., a person, job, team, or survey page) in PI2, Obi will automatically grab relevant context about that entity. This will show up as a visual context "chip" in the chat box.

At any time, you can remove that chip (or add new ones) to help contextualize your conversation.

Yes, previous chats are saved. You can search for and select recent chats (with saved chat history) by clicking the ellipsis (...) button, followed by "Chat history."

While questions can certainly get specific, the ability to search across all data points (such as individual BA factors) is not currently possible. That said, PI is exploring ways to improve this experience.

No. Obi is designed as a powerful, in-the-moment tool that enables dynamic conversation. The value and insights housed in various PI products are what power Obi — you'll still need those module subscriptions for Obi to function. (For example, you'll need an active Hire subscription to access candidate data in Obi.)

At minimum, an active Inspire subscription is required to access Obi. Even with access to Inspire and other products, you will likely still want to reference those products for access to visuals, reports, and other resources that may fall beyond Obi's scope.

Yes. Like any AI, Obi can occasionally make mistakes. PI uses a proprietary rubric and is continuously monitoring for accuracy. That said, please always review responses before acting on them.

Yes. Existing PI permissions are fully respected — the AI never grants access to information a user couldn't normally see. Data is never used to train third-party AI models. All information remains within your PI environment, safeguarded by GDPR and SOC 2 compliance.

Nothing about data submitted to Obi is public. A small subset of our product and engineering teams have access to prompt data submitted to Obi. This data is accessed only for quality monitoring and product improvement purposes. It is never shared or made publicly available.

Per our AI terms addendum, PI is not required to store or retain Obi prompt data. However, if the data is still available, we are happy to provide that data upon formal request.

Organization admins have the ability to turn Obi on/off for your entire organization. Currently, there are no current plans to limit file uploads specifically.

Yes. Organization admins can turn off Obi for the entire account.

No, Obi does not make decisions. PI's AI is a powerful tool designed to increase productivity and assist human decision-making. It provides scientifically aligned insights and suggested guidance for hiring, coaching, and teamwork, but the final decision and oversight always remain with the human user. Use of our AI is always optional.

Our AI is built specifically for PI. We currently instruction-train a private model using ChatGPT, and may use multiple models or change providers over time based on its performance.
​
Our model is different from third-party models in 3 critical ways:

There are 2 key ways we ensure Obi is providing accurate PI science:

PI uses strict tenant isolation; your organization's data is logically siloed within the protected PI ecosystem. We do not pool training between customer accounts, and we employ zero-trust access to the AI environment, meaning Obi honors existing user permissions and authorization boundaries.

Obi is currently available to PI clients at no additional cost. We'll communicate any changes directly to clients in advance.

PI's current Data Processing Agreement covers all processing of personal data through the PI platform, including AI-powered features. PI processing and sub-processors are entirely U.S.-based; for clients with E.U. data, the DPA includes Standard Contractual Clauses (SCCs).

These resources are available here. They're also available through your account team.

PI processes and stores data via U.S.-based cloud infrastructure (Microsoft Azure). Data is encrypted in transit (TLS 1.2+) and at rest (AES-256). For the E.U. and other regions, the DPA includes SCCs. In-scope systems use databases replicated across regions at least 300 miles apart for resilience.

System logs are retained for at least 12 rolling months. Customer data is destroyed within 180 days of contract end (or earlier on request), and is anonymized 120 days post-contract termination. Prompt data is accessible only to a small subset of our product/engineering team, and is used solely for model improvement purposes.

PI maintains SOC 2 and ISO 27001 certifications, GDPR and PCI DSS compliance, and is actively preparing for the E.U. AI Act with governance aligned to ISO 42001.

Obi is designed as a decision-support tool — it does not make autonomous hiring, promotion, or termination decisions. PI is preparing for the E.U. AI Act with governance aligned to ISO 42001. Obi should not be considered an AEDT under NYC law. PI has consistently stated that its tools should be used as one of many factors in an employer's decision-making process and strongly discourages the use of its tools in any other manner.

Currently all of Obi's UI/UX is English-only. A user could potentially ask for a response in another language; that said, any localization output would be generated by the LLM, not by PI. Always check answers for accuracy.

At this time, Obi has no compatibility with WCAG or screen-reader capabilities.

Our team is exploring ways to bring Obi to more places where people work (Slack, Teams, etc.). We are currently in closed beta for Teams, and are also exploring Slack for the future.

To share feedback about Obi, click the thumbs up or thumbs down button on individual Obi responses.

A pop-up will open, allowing you to provide additional context about your feedback.

For support questions, please refer to the same resources you would for traditional PI2 software support: