Businesses in ChatGPT gives companies another place to supply the information customers use to choose them. Before launching an agent, get the answers about your offer, prices and next steps into a form someone can maintain and test.
A conversation can create a promise your business has to keep.
OpenAI announced the beta on November 10, 2026. The examples below come from webvise's own website assistant, where pricing instructions, a configured booking link and separate inquiry tracking already answer some of the questions this launch raises. They give businesses a concrete way to assess the new channel.
- Profile access and Business Agent access have different eligibility rules. Check both before paying for a setup.
- Write down which answers the agent may give and which decisions need a person.
- Keep business information current in a named source, with someone responsible for changes.
- Measure mentions, website visits and accepted inquiries separately. Each records a different action.
If your customer-facing AI needs a clearer scope, webvise's AI consulting maps the workflow, data and review points before a production build.
Check profile eligibility separately from agent access
As of November 11, 2026, eligible businesses in supported ChatGPT markets can claim a profile through Business Hub. Business Agents initially cover eligible ecommerce and online-service businesses in the United States. OpenAI's eligibility FAQ separates those two cases.
| Capability | What OpenAI says is available | What to check before committing |
|---|---|---|
| Business profile | Eligible businesses with a website can claim and verify their business. | Whether the business, location and representative pass verification. |
| Business Agent | Initially available to eligible United States ecommerce and online-service businesses. | Whether the account can publish an agent, independently of profile verification. |
| Business information | Verified businesses can update details and provide product feeds with pricing and availability. | Who owns each fact and how changes reach the profile. |
| Placement and sales | Claiming does not guarantee higher placement or sales. | Which outcome the proposed work can actually demonstrate. |
For a German business, start with profile eligibility. An agency proposal should distinguish the profile work available to that account from agent work that depends on access. The launch announcement gives no date for wider agent availability.
webvise already has an assistant on its own website. That implementation is useful preparation for writing business instructions, but it does not establish eligibility for OpenAI's separate product. Keep the two scopes explicit when comparing a website assistant with a Business Agent.
Write the answers your business can stand behind
On June 10, 2026, webvise changed the default instructions for its website assistant to prohibit fixed public prices, hourly rates and old package names. The replacement tells visitors that estimates follow a discovery conversation about the workflow and its requirements. The instruction expresses how the business sells.
That is the level of detail a useful agent brief needs. If a price depends on scope, say what determines it and where a person takes over. If a return, cancellation or support rule has exceptions, identify them in the source the agent receives.
On June 12, webvise added a separate booking instruction that reads the consultation URL from the application's configured value. The assistant receives that exact destination even when the main prompt changes. A maintained link gives the model a specific next step to offer.
The current assistant also receives instructions to identify itself as AI and avoid confirming prices, delivery dates or bookings beyond its stated role. These are implementation rules, not a measured claim that every model response follows them. They still need tests.
OpenAI's Business Agents Policy requires accurate information and prohibits invented prices, availability, credentials and guarantees. Turn those requirements into examples the business can approve. The broader company knowledge-base guide covers how to organize the supporting material.
Keep conversations and sales in separate reports
OpenAI's launch announcement describes aggregate mentions, website clicks and discovery topics, subject to privacy thresholds. Businesses do not receive users' conversations or Business Agent chats. The published description does not establish a connection between an individual chat and a sale.
webvise's website code makes a smaller distinction that matters here. Its chat-request event fires before the model returns an answer. Its contact-form success event fires after the server accepts an inquiry. Neither event records a qualified opportunity or a paid project.
A report that counts conversations as leads skips those differences. For visitors who reach your website, keep the source information your consent setup allows and follow the actual inquiry path. The landing-page tracking checklist shows the separate events webvise uses for clicks, form submissions and accepted requests.
Discovery topics can suggest questions to answer more clearly. Treat them as themes in the activity OpenAI reports, with the stated thresholds, rather than a complete record of customer demand. A rise in mentions needs its own explanation before it becomes a revenue claim.
Give the setup an owner and an acceptance test
The pricing and booking changes in webvise's assistant point to a useful handover requirement. Each answer needs an approved source, and each destination needs a maintained link. A provider should show how those inputs will change after launch.
- Name the source for offers, prices, availability, policies and contact details. Give each source an owner and a review date.
- Test a pricing question that needs more information. The answer should explain the next step without inventing a quote.
- Test a booking request. Confirm the destination and make sure the answer distinguishes sharing a link from completing a booking.
- Test a request outside the agent's role. Check the handoff and any promises about support or delivery.
- Change one approved fact, then repeat the relevant questions. Save the expected answer and the observed result.
- Write down which numbers come from Business Hub, which come from the website, and which require a sales record.
For a business that can claim only a profile today, the information cleanup still has a defined result: current facts with a clear owner. For an eligible agent, add reviewed answers and working handoffs. Accept the work against those deliverables and the account's actual capabilities.
To review the information, handoffs and measurement behind a customer-facing assistant, discuss the workflow with webvise.
Development practices are aligned with ISO 27001 and ISO 42001 standards.