ChatGPT dots in the UK: availability and a practical launch checklist

If you run a UK business and cannot see dots in your ChatGPT account, the first thing to check is eligibility, not your prompts. OpenAI's launch has different rules for Pro, Business Premium and Enterprise. That distinction matters before you buy a subscription or promise a rollout to your team.

This guide separates the confirmed launch position from our recommendations for getting ready. It was checked on 29 September 2026; availability is changing quickly, so check the linked official guidance before making a purchase.

Are ChatGPT dots available in the UK?

According to OpenAI's getting-started guidance, the initial Pro rollout excludes the UK, the European Economic Area and Switzerland. Business Premium availability covers supported ChatGPT regions, including the UK. Enterprise beta access requires a workspace administrator to enable it. Rollout is gradual, so an eligible account may not receive access immediately.

Specialist enterprise dots are different from that general rollout. OpenAI describes a focused pilot programme with its engineering teams. Having an eligible ChatGPT plan does not guarantee admission. Our specialist enterprise dots guide explains that distinction.

How do you start?

For an eligible account, OpenAI says to create your dot in the ChatGPT desktop app or on desktop web. Mobile-app conversations follow setup where available; mobile web does not support dots at launch. Use the official setup instructions for current steps and account controls.

Our advice: do not connect every available business app during the first session. Decide what the agent needs to produce, then choose the minimum information needed to test that task.

Prepare a one-page brief before connecting systems

A vague instruction such as “help with operations” gives you very little to evaluate. A better brief names one recurring output and the person responsible for checking it. Write down these six decisions:

• Output: what should be delivered, in what format, and by when?
• Sources: which documents or systems may be used, and which are out of bounds?
• Evidence: how should the output point back to its supporting material?
• Authority: what may be prepared, what needs approval, and what must never happen?
• Reviewer: who can judge whether the result is correct and useful?
• Stop condition: what error or unexpected action would make you pause the test?

These are Blue Canvas's workflow-design recommendations, not a claim that every connector or permission setting is available in every account.

A worked example: preparing a weekly project update

Consider a fictional team that spends time each Friday collecting updates from three project owners. For a first test, use a sanitised folder of dated status notes rather than live inbox access.

The required output is a short briefing with completed work, overdue decisions and unanswered questions. Every material statement must link to a note. A missing update stays labelled as missing; it is not filled in from an old message or a plausible guess. The agent prepares the briefing but does not email it, change deadlines or update the project system.

The team lead checks the draft against the original notes. Include one contradictory update and one out-of-date file in the sample. This tests whether uncertainty is surfaced, rather than hidden behind confident prose.

Keep a simple record of preparation time, checking time, corrections and omissions. Compare the total with the existing process. A faster first draft is not a saving if the team lead spends longer repairing it. This is an illustrative pilot design, not a Blue Canvas client result.

What can you do while waiting for access?

Clean up the inputs. Agree where the current version of a document lives, name the process owner and write down the decisions people currently make from experience. Those improvements are useful whether you adopt dots or another tool.

You can also rehearse the output with a manually prepared sample. Ask the intended reviewer to mark what is genuinely useful and what is unnecessary. That is cheaper than building an integration around a report nobody wants.

Do not buy a higher-tier plan solely on the assumption that it provides a particular integration or specialist pilot. Confirm eligibility, necessary features and current commercial terms first. Blue Canvas does not sell ChatGPT access or promise a route around regional restrictions.

Different teams need different boundaries

A sales briefing and an invoice exception report may both involve reading records, but mistakes have different consequences. For more detailed examples, see our legal-team workflow guide and our finance-team pilot guide. These cover preparation and review, not autonomous professional decisions.

Before using sensitive records, have the relevant security, legal and data-protection owners assess the actual setup. Do not treat an attractive demonstration as evidence that the workflow is appropriate for confidential information.

Turn the launch into a useful business decision

Blue Canvas provides independent AI training, workflow planning and implementation support from Derry, Northern Ireland. We can help you decide where an agent might be useful, define a controlled first test and identify what still needs checking.

Visit our independent ChatGPT dots consulting page for a pilot checklist, explore an AI audit, or book a free 15-minute consultation. Bring one recurring task and the decision you would always want a person to own.

Sources: OpenAI's getting-started guidance and 29 September 2026 announcement. Blue Canvas is independent and is not affiliated with or endorsed by OpenAI. Recommendations and the worked example are our own, not product guarantees or measured client outcomes.

‍