OpenAI Presence

Name: OpenAI Presence
Brand: OpenAI

OpenAI Presence is an enterprise product for deploying governed AI agents across real-time voice and chat, covering customer support, outbound sales and high-risk internal workflows such as billing resolution, insurance claims and employee IT requests. Each deployment is scoped to a specific job and receives only the knowledge and system access that job requires; the company sets the policies governing what the agent may do, when it needs approval, and when a person takes over. It pairs OpenAI's models with policies and standard operating procedures, guardrails, approved actions, pre-launch simulations and graders, escalation rules and a Codex-powered improvement loop. Presence is sold through a limited general-availability program to eligible enterprise customers, with deployments led by OpenAI Forward Deployed Engineers and selected global systems integrators; it is not available self-serve and has no public pricing.

Est 2015|Valuation $852B|Raised $186.4B|24 Ref Customers

LinkedIn 11.4M|Website|Web traffic 508.0M|FTEs 4,500|HQ San Francisco, California, US

MarketsCS AI Agent Agent Builder Platforms

Platform CoversCS Quality Management & Coaching Conversation Intelligence

Published Oct 15, 2026

01Common complaints

- Company sizes or stages where this product is overkill or insufficient - Startups and small businesses needing a quick, low-cost pilot: Presence’s managed deployment approach and limited general availability likely make it slower and more expensive than API-based agents or off-the-shelf CCaaS bots. - Industries or use cases where competitors are clearly superior - If you need a full contact center platform with mature workforce engagement management, telephony primitives, and granular packaging today, established CCaaS vendors (Genesys, AWS, Google) may be a better fit. - Technical requirements that this product cannot meet - If you require immediate self-service provisioning or guaranteed feature parity across deployments; Presence capabilities are confirmed per deployment and may vary. - Budget constraints that make alternatives more appropriate - If procurement requires transparent list pricing and predictable per-unit costs, competitors with published pricing may be preferable. - Specific workflows or integrations where the product falls short - If you need a known, documented connector ecosystem out of the box, Presence may require custom scoping and integration effort. - Red flags in the buying process (e.g., requires annual commitment, no free trial) - Limited general availability and a contact-sales model imply qualification gates and potentially longer contracting cycles. - Current limitations acknowledged by the vendor - Availability constraint: Presence is in limited general availability and not self-serve. - Deployment variability: exact features, models, channels, capacity, data handling, pricing, and service commitments are defined for each deployment. - Features on the roadmap (not yet available) - note estimated dates if available - No explicit Presence roadmap items or dates were found in the sources reviewed for this report. - Scale limitations (at what volume/size does it break down?) - Presence is positioned for high-volume workflows, but no public throughput or capacity metrics were found. - Security or compliance gaps - Presence-specific security and compliance posture is contract-defined; buyers should request Presence-specific architecture diagrams, logging and retention policies, data residency options, and third-party audit coverage as it applies to their deployment. - Technical debt or architectural limitations mentioned in reviews - Not enough Presence-specific reviews are available to credibly summarize technical debt or architectural shortcomings. - API limitations or integration constraints - Tooling and integration capabilities are scoped per deployment; organizations with complex legacy systems should expect non-trivial integration effort.

Deal disqualifiers: what makes a POOR fit

Need for a self-serve product available for immediate trial: Presence’s managed deployment approach and limited general availability make it slower and potentially more resource-intensive than API-based agents or off-the-shelf CCaaS bots
Strict on-prem-only requirements or highly restricted data flows without an acceptable deployment architecture
Highly bespoke, low-repeatability workflows where automation ROI is low

02Why they buy

- Competitive advantages validated by customer feedback (not just vendor claims) - Independent validation is limited due to lack of third-party Presence reviews; the most observable differentiator is the managed deployment and governance lifecycle emphasis described in vendor documentation. - Unique features and capabilities competitors lack - It is not proven that competitors lack these capabilities; however, Presence foregrounds: - A controlled improvement loop using production signals with human approval and rollout governance. - Differentiation from competitors based on reviews - There are not enough Presence-specific public reviews to credibly claim differentiation based on customer reviews. - Value propositions with evidence from case studies - The vendor-published internal phone support metrics are notable but are vendor-published and not independently verified; treat them as directional evidence rather than guaranteed outcomes. - Areas where competitors clearly have advantages (be balanced) - Pricing transparency and packaging clarity: AWS, Salesforce, and Genesys provide more published pricing and packaging artifacts. - Mature CCaaS feature breadth and longer operational track records.

03Field reports

Important context on review availability

Presence launched publicly on July 22, 2026 and is offered via limited general availability and managed deployments, which limits the volume of public end-user reviews compared with self-serve SaaS products.
Major review platforms appear to have reviews for OpenAI products broadly (e.g., reviews for ChatGPT/OpenAI), but not clearly for Presence as a discrete SKU at the time of research.

Vendor testimonials (useful as claims, not independent validation)

The vendor page includes customer quotes from BBVA Mexico, SoftBank, and IAG describing exploratory or design partner relationships.
The vendor page also includes internal operational metrics stating Presence powers OpenAI’s English-language phone support and reporting detailed resolution and handoff metrics. These are vendor-published metrics and should be treated as claims rather than independent validation.

Review platforms (Gartner/G2/TrustRadius) — what we could and could not access

- Gartner hosts vendor-level reviews for OpenAI, but not clearly Presence-specific reviews; some snippets reference the OpenAI API rather than Presence specifically. - G2 hosts a seller page for OpenAI (including ChatGPT reviews), which provides sentiment about OpenAI’s products broadly but does not constitute Presence-specific review coverage. - TrustRadius and other review sites did not provide clear Presence-specific reviews in the sources available during this research.

Community/Social (Reddit) — example quotes and themes

- Skepticism that Presence is primarily packaging for existing bespoke deployments: - "OpenAI Presence, as a named and purchasable product, is new. The technology, deployment methods, and custom systems being bundled into Presence are not." - Framing Presence as consultancy-like for enterprises (implying higher cost and less productized self-serve experience): - "That’s exactly what OpenAI is offering with this consultancy service" - Caution about voice channel risk and disputability: - "That’s why I avoid voice - people just lie and it’s hard to prove later."

Common reasons customers might choose Presence (inferred from vendor materials and limited community discussion)

Need for a governed, production operations layer (evaluations/guardrails/rollouts/rollback) in addition to LLM calls.
A managed deployment path (Forward Deployed Engineers / partners) rather than building and operating the stack internally.

Common reasons customers might avoid / leave (evidence-limited; inferred from constraints)

Not self-serve; access depends on eligibility and delivery capacity, which could be a barrier for teams needing immediate rollout.
Preference for vendor-neutral stacks (avoid lock-in) or on-prem requirements that are incompatible with a managed cloud deployment.

OpenAI internal phone support (vendor-published metrics)

- Claim: Presence powers OpenAI’s English-language phone support, "resolves a large portion of inbound issues without human assistance," reportedly met or exceeded human-support quality within a short timeframe, and reduced human handoffs by a noticeable margin within days via an improvement loop. These figures are presented by the vendor. - Critical evaluation: - These are vendor-published and not independently audited in the sources accessed. - Methodology gaps: - No public definition of "resolves" (containment vs. full resolution), how quality was measured, sample size, or whether complex cases were excluded. - Voice support outcomes are sensitive to call types, authentication approach, and tooling permissions—elements that the vendor indicates vary per deployment.

Design partners / pilots (BBVA, SoftBank, IAG)

The vendor materials use terms such as "exploring," "opportunity," and "design partner," which suggests pilots or co-development rather than broad production rollout (though production deployments may exist; the quotes alone do not verify scale).

Independent commentary on feasibility/limitations

Analyst coverage frames Presence as potentially automating frontline work but notes practical limits from fragmented enterprise systems and suggests impacts may be slower and more incremental than vendor messaging suggests.
Industry commentary ties the product positioning to broader conversations about agent security and operational risk.

04Best fit

Company sizes

Best fit (inferred from "high-volume, high-stakes" and managed deployments):
- Enterprise-scale organizations, particularly those with large contact centers or shared services
- Mid-market organizations may be a fit if workflows are highly repeatable and budget allows a managed engagement

Industries and verticals where adoption is strongest (with customer examples)

Financial services and telecommunications are cited as design partners in vendor materials.
Insurance claims is highlighted as a key use case.
Vendor-referenced customers include BBVA Mexico, SoftBank Corp., and IAG.

Roles and personas: decision makers AND end users

Decision makers
- CIO / CTO, Head of Customer Experience / Contact Center Operations
- CISO / Privacy counsel (due to voice, identity verification, and logging)
- Procurement and legal (managed deployment, negotiated contract)
End users
- Customers calling or chatting with support
- Internal frontline teams receiving escalations and reviewing agent performance

Pain points and challenges the product addresses

Consistent behavior across channels (voice and chat)
Governance (policies, permissions, evaluations)
Handling open-ended requests while routing edge cases to human staff

Qualification criteria: what makes a GREAT fit

High-volume workflows with measurable containment/resolution targets
Strong internal SOPs/policies and willingness to formalize them into agent governance
Ability to integrate core systems via APIs and support a structured rollout program

Real customer examples with company names when available

BBVA Mexico, SoftBank Corp., and IAG are referenced by the vendor as design partners or enterprises building with Presence.

05The pitch

What the product does (core value proposition in objective terms)

OpenAI Presence is a managed enterprise platform for building, deploying, operating, and continuously improving governed AI agents for high-volume, high-stakes workflows across voice and chat.
The vendor describes Presence as AI agents intended to operate under governance controls (policies, evaluations, guardrails, escalation rules) and an improvement loop informed by production conversations and quality signals.

Target market and market positioning

Market: large organizations that need reliability, governance, and operational oversight in production agent deployments (customer support and voice highlighted as early use cases; also internal workflows like HR/IT/procurement).
Positioning: closer to a deployed/operated enterprise program (with Forward Deployed Engineers and/or partners) than a self-serve agent builder. Presence is described as not self-serve and offered via limited general availability.

Get a comprehensive analysis of OpenAI Presence including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →