THE AUGURY · MSP AI MARKETING

Why ChatGPT Business Hub Claims Fail (and How MSPs Fix Them)

Why ChatGPT Business Hub claims and Persona checks stall for MSPs, and how to fix DNS records, name mismatches, locked listings and disputes.

The Verification tarot card: a woman holding a business-profile medallion and a magnifying glass over a checklist.

If your MSP's ChatGPT Business Hub claim is stuck, it's almost always one of three things: a legal name that doesn't match your registration, a code sent somewhere nobody watches, or a DNS record added in the wrong place. Verification has two checks. Claim verification proves your MSP is connected to the listing, and Persona proves who you are.

All three are fixable, and an MSP can fix them faster than most businesses because you already run DNS, phone systems and email for a living. If you haven't started your claim yet, get your account, records and DNS access ready first, then claim your listing step by step. This post is for when it goes sideways.

ChatGPT Business Hub verification errors and fixes

Find what you're seeing in the first column. Items marked "early reports" come from businesses going through the claim, not from OpenAI's guide.

What you seeLikely causeFix
Phone code never arrivesThe number on your listing routes to a phone tree, answering service or queueUse domain verification if it's offered
Email code never arrivesThe address on file is a shared inbox nobody watchesUse domain verification, or check that inbox
Domain won't verifyThe record went to your registrar, but your DNS is hosted elsewhereAdd the record where your nameservers point
Domain won't verifyRecord saved as an A record (early reports)Change the record type to TXT
Domain won't verifyYour domain doubled in the host fieldEnter only the host ChatGPT shows you
Domain won't verify right after you add the recordThe record isn't public yetWait, run a TXT lookup, then select Verify domain
Verification record no longer worksRecord expired after 24 hours (early reports)Start again and finish the same day
Persona check failsThe name, address or ID number on the form differs from your official recordsCorrect the form or the record, then resubmit
"Couldn't read website" (early reports)ChatGPT can't reach your site, often because of bot protection or a WAFCheck your firewall and bot rules
"Contact support" on your listingThe listing is lockedSelect the button to ask OpenAI for access
Claim has to start from a specific adminThe listing is tied to a ChatGPT Enterprise workspaceHave the workspace's designated administrator start it
Product feed domain error (early reports)The feed's domain doesn't match your websiteMost MSPs can skip the feed
Someone else manages your listingIt was already claimedFile a dispute from the ••• menu on the profile
Your claim seems to have disappearedYou're signed in with a different ChatGPT accountSign in with the account you started the claim with

The sections below explain each fix in detail.

In this post:

When your records don't match the form

Persona compares what you type against your official records: your legal business name, your registered address, and your registration or tax number if you have one. The basic rule, from OpenAI's setup guide, is that Persona wants your registered name, and the name you go to market under belongs in the trade-name field when the form has one.

That rule covers the MSP that goes to market as a brand and is registered as an LLC. It doesn't cover every MSP, and the cases below are where claims stall.

Sole proprietors

Early users report that the form asks whether the business is a sole proprietorship or an entity. If you run your MSP as a sole proprietor with no separate company registration, choose sole proprietorship and enter your details the way the official record you do have shows them.

OpenAI's guide doesn't spell out which document Persona checks for a sole proprietor, so don't guess, and don't invent a company name to fill the field. If the form asks for something you don't have, stop and ask OpenAI Support before you submit. A rejected check costs you more time than a support ticket.

The registration number field

The registration-number field, according to early users, shows a placeholder that looks like a U.S. EIN, even when the form wants a different identifier. Read the field label and ignore the placeholder. This matters most for MSPs outside the U.S. Early users report a Canadian business completed the full flow, including domain verification, so Canadian MSPs can claim. Give the form the identifier its label asks for.

Old addresses and acquired names

MSPs move offices and buy other MSPs, and the paperwork usually trails behind. Persona checks against the official record, not your website, so the record wins.

The physical address and the legal registered address are separate fields in early users' claims, and P.O. boxes aren't accepted. Put the address on your registration in the legal field and the office you work from in the physical field. If your registration still shows an office you left three years ago, update the registration before you claim, because Persona only compares the form to the record.

Acquired brands follow the same logic. The legal name is whichever entity your records say owns that brand today. If the acquired company's LLC still exists and still owns the brand, that's the name Persona expects.

DNS verification fails for boring reasons

Phone and email codes tend to land in phone trees, answering services and shared inboxes, which is why we recommend domain verification for MSPs when Business Hub offers it. When DNS verification fails, it's almost always one of a few mistakes.

ChatGPT shows you the record to add, and OpenAI's guide is clear that every part of it has to match what's on screen. Early users report the record is a TXT record with the host openai-business-profile, a value that starts with openai-business-profile= followed by a code, and an expiry of 24 hours. OpenAI doesn't publish those values, so treat your own screen as the source of truth.

Work through it in this order:

1. Find where your DNS is hosted

Look up your domain's nameservers. If they point to your web host or a CDN instead of your registrar, add the record there. ChatGPT will never find a record left at the registrar in that setup.

2. Create a TXT record

Check the record type before you save. Some DNS panels default to an A record, and early users report that's a common reason verification fails.

3. Enter the host exactly as shown

Many DNS panels add your domain to the host automatically. If you type the full name, you can end up with openai-business-profile.yourdomain.com.yourdomain.com. When the panel shows your domain next to the field, enter only the part ChatGPT gave you.

4. Paste the full value

Copy it from ChatGPT instead of retyping it, prefix included.

5. Confirm the record is public before you click Verify

OpenAI notes that new DNS records don't show up right away, and early users report that checking too soon is a common failure. Run a TXT lookup on the host from outside your network and wait until the value comes back.

6. Finish the same day

Start when the person with DNS access can see it through, so the record doesn't lapse before you click Verify.

7. Return to ChatGPT and select Verify domain

Then complete the remaining prompts.

8. Leave the record in place

Early users kept it after verification, and there's no reason to risk removing it. Note it in your documentation platform so nobody removes it during the next DNS cleanup.

Persona failed or expired

A verified domain doesn't unlock anything by itself. Until Persona approves the person behind the claim, you can't publish edits or see Insights.

According to early users, Persona runs on a phone through a QR code or link. It needs camera access, doesn't require an app, and may ask you to record a short video of your face. The person who starts the check has to be the person who finishes it. If you planned to hand it to an office manager, plan again.

A failed or expired check comes with an email from OpenAI that tells you what to do next. If it offers a retry, find what didn't match first. Most failures trace back to the records section above: a brand name in the legal field, an old registered address, or the wrong identifier in the registration-number field. Resubmitting the same details gets you the same answer, and a second check started while the first is pending won't help either.

New profiles carry one more trap. If you create a profile through Persona, approval publishes it on the spot, so write the description before you submit.

Other errors early users are hitting

"Couldn't read website." Some businesses hit this error during setup. It suggests ChatGPT can't reach your site, and an MSP with aggressive bot protection, a WAF or geo-blocking on its own website should check those rules first.

"Contact support" on your listing. A locked listing shows this button instead of a claim option, and selecting it sends OpenAI your access request. If your company runs ChatGPT Enterprise, the listing may sit under that workspace, and only its designated admin can start the claim. Find out who that is before anyone else tries.

Product feed domain errors. Early users report these when a product feed's domain doesn't match the listing's website. Product feeds are built for businesses that sell catalog products, and most MSPs don't need one. The simplest fix is not connecting a feed.

When another account already holds your listing

It could be a former employee, a marketing agency you stopped paying two years ago, or someone you've never heard of. Either way, you can get it back at no cost.

The fix lives in the profile itself: the ••• menu has a Dispute ownership option, and Persona confirms you have the authority to represent the business. Filing a dispute doesn't affect how visible the profile is in ChatGPT, according to OpenAI, so there's no downside to filing.

If the person holding the listing is someone you can reach, such as your old agency, ask them to add you through Business Hub, since the admin who claimed a business can add teammates. Dispute ownership if they won't.

Don't pay anyone who offers to remove the listing for you. OpenAI's guide says Support won't remove a live profile when you ask for setup or ownership help, so a paid removal offer is promising something OpenAI says it won't do.

What to send OpenAI Support

Rule out the most common false alarm first: a different login. A claim lives under the ChatGPT account that started it, so sign in with that account, then look under Business in Business Hub. Many "my claim disappeared" tickets turn out to be the wrong account.

When you do contact support, send what your own help desk would want from a client:

  • The step you were on and the verification method you used.
  • The exact error text, copied, not paraphrased.
  • A screenshot with ID numbers, tax numbers and personal details blurred.
  • The date you started the claim, and whether a review is still pending.

Support can't undo much. A draft you haven't published can be deleted from the profile's Overview menu, but a live profile stays live, so don't open a ticket hoping to start over.

A verified listing is the start of your AI search strategy

Once you're verified, you control what your listing says, and the next decision is what it should say. That depends on who you're up against. When a buyer asks ChatGPT for an MSP in their city, the answer often names several MSPs side by side. Your listing, your website and your reviews get read next to your competitors', and the MSP that most clearly describes the service the buyer asked for has the better shot at the click.

ChatGPT also has no managed services category, so every MSP in your market is deciding how to describe itself without a box that fits. Ian Richardson covers what the missing category means for MSP sales in ChatGPT Doesn't Know What an MSP Is. That's a Sales Problem. on Fox & Crow Group.

MSP competitive intelligence is how you make those decisions on purpose instead of by guessing. A Jackdaw reading compares your MSP with the local competitors a buyer would weigh you against, across search results, reviews, websites and AI-search readiness. It shows you which services your competitors already claim and where none of them are showing up yet.

Once you have the report, you can build your AI search strategy from it yourself with the free MSP marketing guide, or work with Carrie Richardson to build it with you.

Request a Reading to see where your MSP stands against the competitors in your market.

Frequently Asked Questions

Why did my MSP's ChatGPT Business Hub verification fail?

Your MSP's ChatGPT Business Hub verification most likely failed because the legal name, registered address or registration number didn't match your official records, a phone or email code went somewhere nobody was watching, or the DNS TXT record was added in the wrong place or with the wrong type. Correct the record that didn't match, then resubmit.

Where does an MSP add the ChatGPT Business Hub DNS TXT record?

An MSP adds the ChatGPT Business Hub DNS TXT record wherever its domain's nameservers point, which is often the web host or CDN instead of the registrar. Copy the host and value from your ChatGPT screen instead of retyping them, and early users report finishing within 24 hours, before the record expires.

Can a sole proprietor MSP register on ChatGPT Business Hub?

A sole proprietor MSP can register on ChatGPT Business Hub if it meets OpenAI's eligibility rules, and early users report the setup form offers sole proprietorship as a business type. Match your official record word for word, and check with OpenAI Support before you submit if a required field doesn't apply to you.

How long does ChatGPT Business Hub verification take for an MSP?

ChatGPT Business Hub verification for an MSP takes as long as OpenAI's review, which ends with an email that either approves the claim or asks for more details. Some early users report same-day approval, but Persona identity verification is a separate step, and features stay locked until it's approved.

What should an MSP do if someone else claimed its ChatGPT listing?

An MSP that finds someone else claimed its ChatGPT listing should file a dispute from the profile's ••• menu and confirm through Persona that it's authorized to act for the business. Filing is free and doesn't affect the profile's visibility, according to OpenAI.