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

01Competitive Landscape

| Aspect | OpenAI Presence | Amazon Connect (AWS) | Salesforce Agentforce / Salesforce Voice | |--------|-----------------|----------------------|------------------------------------------| | Starting Price | Not public; contracted managed deployments | Published pricing page; usage-based model (varies by component) | Published per-user pricing available from the vendor and bundled packages | | Best For | Enterprises needing managed, governed AI agents across voice/chat with emphasis on governance and rollout control | Teams wanting a CCaaS-native contact center with AWS ecosystem integration and transparent pricing | Organizations standardized on Salesforce CRM/service workflows seeking agents grounded in Salesforce data and governance | | Key Strength | Managed governance and a continuous improvement loop; deployment support by FDEs/partners | Mature contact center product packaging; published cost model; broad AWS services integration | Tight CRM/service integration and structured billing constructs for agent usage and voice bundles | | Key Weakness | Limited general availability and not self-serve; features/SLAs/pricing vary per deployment; harder to benchmark publicly | DIY/implementation burden can be significant; buyers may need AWS expertise/partners | Pricing complexity for certain consumption models; customers have reported complexity in some community discussions |

Narrative analysis

- Direct competitors and their key differentiators - AWS Amazon Connect - Differentiator: contact-center-first product with transparent pricing pages and AWS-native operations. - Salesforce Agentforce / Voice - Differentiator: CRM/workflow grounding and governance inside Salesforce; explicit billing constructs. - Google CCAI Platform - Differentiator: Google Cloud contact center tooling and documentation-first onboarding; typically sold via Google Cloud projects and partners. - Genesys Cloud CX - Differentiator: established CCaaS suite with AI add-ons and published packaging guidance. - Feature comparison: where Presence may excel vs lag behind - Potential strengths vs CCaaS suites - Emphasis on a governance lifecycle (simulations, evaluations, guardrails, controlled rollout/rollback) and a continuous improvement loop based on production evidence. - Potential weaknesses vs CCaaS suites - Less public detail on an integration catalog, routing/telephony options, analytics packaging, and agent desktop/co-pilot suites compared to mature CCaaS vendors. - Pricing comparison: value proposition vs alternatives - Presence: opaque, negotiated pricing and project scope (may be acceptable for large enterprises; challenging for mid-market). - Competitors: often provide published starting points or clearer units (published per-user pricing or other published usage-based units). - Customer testimonials comparing this product to competitors - No direct public quotes were found that specifically state a customer chose Presence over a named competitor during the research for this report. - Market share and adoption trends - Presence-specific adoption numbers are not publicly provided in accessible sources. - OpenAI claims broad business platform adoption generally, but this is not a proxy for Presence deployments. - When customers choose competitors instead (and why) - When they need immediate self-serve onboarding, published pricing, or standardized CCaaS features (telephony, workforce management integrations, mature admin tooling). - When they prioritize vendor neutrality or a multi-LLM strategy to avoid reliance on a single model vendor.

01Competitive Landscape

Aspect	OpenAI Presence	Amazon Connect (AWS)	Salesforce Agentforce / Salesforce Voice
Starting Price	Not public; contracted managed deployments	Published pricing page; usage-based model (varies by component)	Published per-user pricing available from the vendor and bundled packages
Best For	Enterprises needing managed, governed AI agents across voice/chat with emphasis on governance and rollout control	Teams wanting a CCaaS-native contact center with AWS ecosystem integration and transparent pricing	Organizations standardized on Salesforce CRM/service workflows seeking agents grounded in Salesforce data and governance
Key Strength	Managed governance and a continuous improvement loop; deployment support by FDEs/partners	Mature contact center product packaging; published cost model; broad AWS services integration	Tight CRM/service integration and structured billing constructs for agent usage and voice bundles
Key Weakness	Limited general availability and not self-serve; features/SLAs/pricing vary per deployment; harder to benchmark publicly	DIY/implementation burden can be significant; buyers may need AWS expertise/partners	Pricing complexity for certain consumption models; customers have reported complexity in some community discussions

Narrative analysis

Direct competitors and their key differentiators
- AWS Amazon Connect
  - Differentiator: contact-center-first product with transparent pricing pages and AWS-native operations.
- Salesforce Agentforce / Voice
  - Differentiator: CRM/workflow grounding and governance inside Salesforce; explicit billing constructs.
- Google CCAI Platform
  - Differentiator: Google Cloud contact center tooling and documentation-first onboarding; typically sold via Google Cloud projects and partners.
- Genesys Cloud CX
  - Differentiator: established CCaaS suite with AI add-ons and published packaging guidance.
Feature comparison: where Presence may excel vs lag behind
- Potential strengths vs CCaaS suites
  - Emphasis on a governance lifecycle (simulations, evaluations, guardrails, controlled rollout/rollback) and a continuous improvement loop based on production evidence.
- Potential weaknesses vs CCaaS suites
  - Less public detail on an integration catalog, routing/telephony options, analytics packaging, and agent desktop/co-pilot suites compared to mature CCaaS vendors.
Pricing comparison: value proposition vs alternatives
- Presence: opaque, negotiated pricing and project scope (may be acceptable for large enterprises; challenging for mid-market).
- Competitors: often provide published starting points or clearer units (published per-user pricing or other published usage-based units).
Customer testimonials comparing this product to competitors
- No direct public quotes were found that specifically state a customer chose Presence over a named competitor during the research for this report.
Market share and adoption trends
- Presence-specific adoption numbers are not publicly provided in accessible sources.
- OpenAI claims broad business platform adoption generally, but this is not a proxy for Presence deployments.
When customers choose competitors instead (and why)
- When they need immediate self-serve onboarding, published pricing, or standardized CCaaS features (telephony, workforce management integrations, mature admin tooling).
- When they prioritize vendor neutrality or a multi-LLM strategy to avoid reliance on a single model vendor.