Cultural intelligence inside the AI your company already uses.
What it is
Many companies give their employees an AI assistant, such as Claude, ChatGPT or Copilot. Your company can connect these assistants to UC.
From then on, when a colleague asks something that involves more than one culture, the assistant retrieves UC’s research and answers from it.
Our cultural expertise comes to your colleagues, inside the tool they already use. They do not need to learn a new tool or visit another site.
How it works
An American engineer has prepared a presentation for a decision-maker in Germany. She asks her AI assistant to critique it.
The assistant sees that the question involves an American and a German. It asks UC for research on persuasion, once for Germany and once for the United States.
UC sends back the research for each country, with links to the pages it comes from. The assistant writes its answer from that research.
It explains how each side sees the situation, and it includes the links. If she wants to read the analysis and the evidence, she clicks a link.
A question can involve more than one topic. The assistant then asks UC once for each country and each topic.
If UC does not cover a country or a topic, it says so. The assistant can then tell your colleague that its answer does not come from UC’s research.
What your assistant sends to UC
Each time an assistant asks UC for research, it sends two pieces of information: one country and one topic. It does not send the question, the conversation or any documents. UC never receives what your colleagues write.
UC records the country, the topic and the time with the user’s account. It needs this to charge for the call.
Many AI assistants show each call to UC and what it sent. Your colleagues and your IT department can check this themselves.
How your company sets it up
A manager opens a team account on UC, pays for it and invites colleagues. Each colleague registers and finds one web address on their account page. In the AI assistant, they open the settings, add a connector and paste in the address. The assistant then asks them to sign in to UC and to allow the connection. This takes about two minutes, and each person does it once.
In many companies, an administrator must add UC first. This applies, for example, to Claude Team and Enterprise plans. In Microsoft Copilot, a specialist usually sets up UC once for the whole company. Each colleague then signs in to UC once.
What you also get
Your account also gives you full access to UC on the site. You can read all of the research under Countries, with the evidence where it exists. You can also ask the culture advisor on the home page up to 20 questions per month.
You pay only for the calls your assistant makes to UC. Reading on the site and asking the advisor are not charged as calls.
What your company pays
The calls are charged to the team account. The manager sees the total use on the account page. [Price to be added.]
Each colleague’s account also gives full access to UC on the site. This includes all of the research under Countries, with the evidence where it exists, and up to 20 questions per month to the culture advisor on the home page. Reading on the site and asking the advisor are not charged as calls.
A team can start with a company credit card. If your company requires a supplier review or a contract, we will work with you on it.
For your IT department
Many companies decide which connectors employees may add to the company’s AI assistant. If yours does, your IT department may need to approve UC first.
UC connects through MCP, the Model Context Protocol. MCP is the standard way for AI assistants to connect to outside sources. The connection only reads research from UC. Each user signs in to UC. For the details see: How the connection works.