On this page
- First: which verification failed? Claim methods vs the Persona identity check
- Phone verification failed or no code arrived
- Business email verification failed or the code never lands
- DNS TXT record verification failed (host field, propagation, registrar quirks)
- Shopify verification failed (permissions and the wrong store login)
- When every method fails: Try again, OpenAI's review email and what to send Support
- After you are verified: keep your business showing up correctly in ChatGPT answers
- FAQ: ChatGPT business verification failed
- Pick the method you control fully, then put verification to work
- Related Business Hub guides
When ChatGPT business verification fails, work out which check failed first, then retry with a different claim method if one is offered. This guide goes method by method: what the failure usually means, what to change, and when to stop retrying and write to OpenAI Support. Beta behaviour as checked 18 November 2026. OpenAI can change any of this without notice, so treat the on-screen options for your listing as the final word.
First: which verification failed? Claim methods vs the Persona identity check
There are two separate checks, and most confusion comes from treating them as one. The ownership claim proves you control the business listing. You complete one of the methods the Business Hub offers for your listing: a code sent to the business phone or email, a DNS TXT record, or a Shopify connection. Only the methods available for your listing appear, so a friend's Hub may show options yours doesn't.
After OpenAI reviews and approves the claim, a Persona identity check may be required. The blue verified badge appears after Persona verification is approved; claim approval alone does not provide it. Persona verification is required to publish changes to business information and view insights, though other capabilities like connecting a product feed are handled separately.
Use this table to place your failure:
| What you see | Which check | What to do |
|---|---|---|
| No code arrives, code rejected, DNS or Shopify step errors | Ownership claim | Use the method sections below, or pick another offered method |
| Claim submitted, nothing happening | Claim review | Wait for OpenAI's review email and do not restart the process |
| Claim approved, but the Hub still shows verification incomplete | Persona | Check your email for instructions and select Try again if it appears |
| Persona fails or expires | Persona | Follow the email, and make sure your business name, address and registration or tax number match official records |
If a claim or Persona check is pending, wait for the review email rather than starting over. Restarting can leave you with a second half-finished attempt and no clearer answer.
Persona problems get only a brief treatment here. For the full claim-then-identity sequence, read How to Claim and Verify Your Business in ChatGPT.
What does OpenAI's help center say organization verification requires?
The ChatGPT Business Hub help article explains that an authorized person must verify their connection to the business to claim it, then complete Persona identity verification to publish changes, view insights, or access certain features, which may require government-issued ID, business registration information, and proof of authorization. It is not the same as claiming a business in the Business Hub, which uses a phone, business email, DNS TXT or Shopify method. Requirements and eligibility can change, so confirm the current wording on OpenAI's help center before you submit, and make sure the ID name and the business details you provide match what you can prove.
Phone verification failed or no code arrived
If phone verification fails, don't keep requesting codes. Switch to another method the Hub offers for your listing. A code goes to the business phone number attached to the listing, which is not necessarily the number you would like to use. If that number is a landline, a main switchboard, a number nobody answers, or a number that changed since the listing was created, the code has nowhere useful to land.
Work through these checks in order:
Confirm the number shown in the Hub is the one you control right now. If it isn't, phone is the wrong method for this listing.
Check that the number can receive a text or call in the form the Hub uses. Desk phones and some VoIP lines cannot.
Wait a few minutes before asking again. Repeated requests rarely speed delivery up.
If the code still doesn't arrive, move to email, DNS or Shopify, whichever is shown.
Most phone failures are a listing problem, not a you problem. Don't spend an afternoon on it when a DNS record takes ten minutes.
Business email verification failed or the code never lands
When the business email code never lands, the cause is usually the address, the mailbox or a filter, and the quickest fix is another offered method. The code goes to a business email tied to the listing. Check the obvious places first: spam, junk, quarantine and any shared-inbox rules. A shared mailbox such as info@ or hello@ often forwards to someone who isn't watching it.
Things to check:
The address belongs to your business domain and can receive external mail.
Your mail provider or security gateway isn't quarantining messages from unfamiliar senders. Ask whoever administers your email to look at the quarantine.
You are looking at the right mailbox. Founders often check a personal inbox while the code went to a role address.
You haven't requested several codes in a row and then typed an older one. Use the newest.
If none of that helps, don't loop. Use DNS TXT or Shopify if the Hub lists them. Email failures tend to sit with IT filtering, which you can't always fix quickly.
DNS TXT record verification failed (host field, propagation, registrar quirks)
A failed DNS TXT verification is almost always a host field typo, a record that hasn't propagated yet, or a registrar that rewrote what you entered. In the Hub, select Website domain and copy the TXT record's type, host and value exactly into the DNS provider for your domain. Then return and select Verify domain.
The three usual causes:
Host field mismatch. Some DNS editors append your domain automatically. If the Hub gives a full host and you paste the full host into an editor that adds the domain again, you end up with the domain twice and the record never matches. On Shopify-managed DNS in particular, double-check the host field and enter only what the editor expects. Open the saved record afterwards and read what the editor actually stored.
Propagation. DNS changes may take time to appear. If you verify seconds after saving, you will often fail on a record that is correct. Wait, then retry rather than editing a correct record.
Value mangling. Copy the value as it is. Trailing spaces, smart quotes and a line break picked up from a chat or document can break the match. Some registrars want quotes around the value and add them themselves, so don't add a second pair.
A quick sanity check: after saving, look the record up with any public DNS lookup tool and compare the returned value character by character with the Hub's. If they match and the Hub still fails after a reasonable wait, retry once, then move to another method.
Shopify verification failed (permissions and the wrong store login)
Shopify verification fails when you approve the wrong permissions, or sign in to a Shopify account that isn't the store associated with the business. In the Hub, select Shopify store, then Connect Shopify. Approve the permissions that are requested and sign in to the Shopify store associated with the business.
The common traps:
You are logged in to a different Shopify account in the same browser, for example an agency or personal store, and the connection goes to that one. Log out, or use a clean browser profile, and connect again.
You are a staff member without the access needed to approve the connection. Ask the store owner to do it.
You declined or skipped part of the permission screen. Run the connection again and approve what is requested.
The store attached to the business listing isn't the store you think it is, which is common with rebrands and multiple storefronts.
If the store login and permissions are right and it still fails, fall back to DNS using the same domain, which doesn't depend on Shopify at all.
When every method fails: Try again, OpenAI's review email and what to send Support
If every method fails, follow any instructions in OpenAI's email, use Try again if it is available, and contact OpenAI Support only once you can't retry. Retry with accurate details. If a claim is still in review, wait for the decision email rather than starting another attempt.
When you do write to Support, give them enough to act on:
The step you reached (claim method, claim review, or Persona).
The exact error message.
A screenshot with sensitive information removed.
Which method you tried and when.
If the Hub still shows verification as incomplete after approval, say so plainly.
If Persona is the part that failed or expired, also confirm that your business name, address and registration or tax number match official records before you retry. Mismatched details are the most fixable cause there.
The Businesses in ChatGPT Terms also matter here. Under them, OpenAI does not guarantee that Businesses in ChatGPT will remain available or receive any particular placement, ranking or visibility (OpenAI, Businesses in ChatGPT Terms). Verification gets you in the door, and nothing more. For background on who can use the Hub at all, see ChatGPT Business Hub: What It Is and Who Can Use It.
After you are verified: keep your business showing up correctly in ChatGPT answers
Verification gets you into the Hub, but it doesn't keep your business showing up well in ChatGPT answers. That is a weekly job.
Revnu is an AI agent that finds customers and grows revenue across SEO, AI search, outbound and paid ads, and reports to you in Slack or iMessage. For this use, it tracks how your business appears in ChatGPT, Claude, Perplexity and Gemini answers and in Google, publishes pages that wait for review for at least a day to fix gaps, and runs outreach and ads. Pro is $99 a month, self-serve.
Revnu doesn't connect to the Business Hub or pull Hub data. Keep any Hub numbers inside the Hub: OpenAI's terms make Insight Data its confidential information, so figures don't go into public posts, case studies or screenshots without OpenAI's written authorisation; service providers working for you under equivalent restrictions are the exception. For how to read and act on what the Hub shows you, see ChatGPT Business Hub Metrics and Weekly Reporting and Turn ChatGPT Business Hub Data Into Revenue Decisions.
FAQ: ChatGPT business verification failed
Short answers to the questions people ask most are in the FAQ below. If yours is about product feeds or Business Agents rather than verification, start with ChatGPT Business Hub Product Feeds: CSV Setup Guide or ChatGPT Business Agents: Eligibility and Setup.
Pick the method you control fully, then put verification to work
Most failed verifications come down to choosing a method you don't fully control: a phone nobody answers, a shared inbox, a DNS host field the editor rewrote, or the wrong Shopify login. Use whichever method the Hub offers that you can finish today. Wait for OpenAI's review email instead of restarting, and write to Support with the step, the error and a clean screenshot only when Try again is gone. Once you are verified, the work moves to staying visible in answers. Start Revnu Pro at revnu.com and have it track how ChatGPT, Claude, Perplexity and Gemini describe your business, then publish what closes the gaps.
Related Business Hub guides
Written by
Co-founder and CEO, Revnu
