# ChatGPT Business Hub: How to Claim Your Business and Check Verification

Business Hub adds a new place to manage your company’s information, but claiming a profile, publishing an agent and earning recommendations are different steps.

By Paras Madan | 2026-11-11


OpenAI launched Businesses in ChatGPT on November 10, with Business Hub for claiming company profiles and Business Agents for answering customer questions. For a founder, the first useful job is to establish who controls the profile and which information it should contain before treating this as another acquisition channel.

The [launch announcement](https://openai.com/index/introducing-businesses-chatgpt/) separates business information, aggregated engagement insights and an optional agent experience. Eligible businesses can claim profiles where ChatGPT is available. Business Agents currently target eligible US ecommerce and online service businesses. An agent conversation is visibly separate from ChatGPT’s independent answer, and sponsored placements are labeled separately too.

## Claim the profile before planning the agent

The [setup guide](https://help.openai.com/en/articles/20001635-setting-up-your-business-on-chatgpt) describes two checks: approval of your business claim and Persona identity verification. Open Business Hub, find the right listing and follow an offered verification method, such as business email, phone, domain or Shopify. Persona approval unlocks publishing business changes, insights and eligible agents. A submitted check is still pending until approved.

Choose the account responsible for maintaining the business, rather than whoever happens to discover the feature first. Before starting, decide who can verify the domain, who owns the product feed and who approves policy changes. An abandoned founder login is a poor foundation for a business profile that needs regular maintenance.

One detail deserves attention: when Persona is used to create a new profile, OpenAI’s approval publishes that profile automatically. Publishing an agent remains a separate choice. Prepare the public description before you enter that path.

## Prepare information that can survive a customer question

For an illustrative developer-tool company, the useful input is more specific than “AI infrastructure for modern teams.” A buyer needs to know what the tool does, who it supports, what the quoted price includes and which limitations change the purchase decision.

I would prepare a small evidence sheet first:

- Product: a hosted service for evaluating support-ticket classifiers.
- Intended customer: engineering teams running their own classification pipeline.
- Billing: the actual pricing unit and any minimum commitment.
- Limits: supported integrations, retention settings and excluded use cases.
- Policies: cancellation, refunds and the route to a human when an answer is uncertain.

These are example fields, not claims about a real company. The point is to make every commercial statement traceable to an owner and a current source. If sales says one thing and the help center says another, resolve that disagreement before giving either version to an agent.

## Test the awkward question before publishing

Business verification does not establish agent eligibility. OpenAI’s [Business Agents Policy](https://openai.com/policies/business-agents-policy/) also requires accurate offerings and fees, honest identification of the agent and appropriate limits on data collection and regulated advice.

Use a short acceptance test rather than asking the agent to introduce the company. For the fictional evaluation service, ask what happens if a customer cancels halfway through a month, whether a particular integration is supported and whether customer data can be deleted. Then ask a question the approved material cannot answer.

The last question matters most. A convincing invented exception can cost more than a cautious answer that sends the customer to support. Write down the expected answer for each test and review the result against that answer, rather than judging whether the wording sounds friendly.

## Diagnose the blocked step

If the listing is locked, use Support. If verification is pending, wait for the decision rather than repeatedly submitting. If approval was received but the interface still blocks progress, send Support the failing step and a redacted screenshot.

A profile can be eligible while an agent is not. The current agent cannot complete purchases, bookings or order lookups; it directs customers to the website. Do not build a customer journey that depends on it completing those operations.

That leaves three separate troubleshooting questions: is this the correct profile, is verification approved, and is this business eligible for the requested agent feature? Keeping those questions separate is quicker than rewriting the description each time a button is missing.

## Measure the result without promising a ranking boost

**Claiming a profile is information management, not a ranking guarantee.** OpenAI explicitly says claiming does not guarantee more visibility or control independent recommendations. Business Hub insights are aggregated; a blank metric does not prove zero activity.

For the first month, maintain a dated record of material profile changes alongside website referrals and actual qualified enquiries. Avoid declaring a successful acquisition channel because one number moved after setup. You need enough observations to distinguish a useful source of customers from a new dashboard.

The practical opportunity is straightforward: make the business easier to understand when a customer already asks about it. Whether that produces additional demand is something to measure, not a promise to put in the launch pitch.

I’m Paras. I work at the intersection of AI, engineering and distribution.

I help technical founders turn product details and practical lessons into clear stories that developers and buyers can use.

[Book a 30-minute call](https://cal.com/paras-madan/30min).
