Insights · By Jules, founder of WYN

The AI setting marketing should have a say in: what your AI can see

What your team's AI assistant can read and change, from client files to the CRM and the team chat, can be decided once, in a settings screen, by whoever runs the company account.

That is a decision about client and customer data, and it needs an owner outside IT before it gets made by default. By connections we mean the links that let an assistant read from, or act in, the other apps a team already uses. In an agency, many of them touch a client's systems, which makes it a client conversation as much as a technical one.

One example of how it is changing

On 10 November, Anthropic announced an automatic-connection option for its assistant, Claude, in beta on eligible Team and Enterprise plans. An admin sets up an app such as Notion, Atlassian or Dropbox once, and staff are connected the first time they use it, instead of each person connecting on their own.

Admins can also limit what each connection does. Anthropic's example is an assistant that can read Slack but not send messages on your behalf. On Enterprise plans, admins decide who can use which connections. The same launch adds ready-made add-ons from work apps such as Salesforce and Workday, both in beta.

To be fair to Anthropic, it says the assistant works within each person's existing permissions, however a tool is connected.

This is one vendor's version. The question it raises applies to whichever assistant your company uses.

Allowed to see, and right to use

Our point starts where the permissions end. Being allowed to see something and it being a good idea for the assistant to draw on it are different decisions. The first is set by IT and the access rules. The second belongs to the people who know what the data is for, what was promised to the client, and what would embarrass the business if it surfaced in the wrong draft.

An account director may have access to three clients' folders because she works across them. Whether her assistant should be reading all three when it drafts a pitch for one of them is a judgement about the work. The access settings can't make it for her.

We are for connecting. AI that sits in a separate tab, cut off from the brief, the client data and the reporting, stays a toy, and connecting it is how it becomes useful. That is exactly why the choice of what to connect, and whether each connection may only read or may also change things, deserves the same care as any other decision about client data.

What it means for agencies and in-house teams

For agencies, much of the data an assistant could read sits in clients' systems or in files clients sent you. Which connections are switched on belongs in client onboarding, agreed with the client, rather than discovered later when someone asks how a draft knew what it knew.

For in-house marketing teams, the person who runs the company's AI account may be deciding what marketing's assistant can see in the CRM and the reporting tools. Marketing should be part of that decision, because marketing knows which customer data is sensitive, which is out of date and which is fine to use.

The fair counterpoint: connecting everything isn't the goal. Each connection is a risk to manage and something to maintain as people, clients and tools change. The sensible start is the two or three systems your team copies from most into an AI chat today. Those are where a connection saves real time, and where a decision is needed first. The rest can wait until there is a reason.

What to do this week

  • Ask whoever runs your company's AI account what is connected today, and what an automatic-connection setting would switch on for your team.
  • Ask your team which two or three systems they copy from most into an AI chat. Those are the first connections worth deciding; the rest can wait.
  • Name one owner outside IT who signs off each new connection, including whether it may only read or may also change things.
  • Agencies: add one line to client onboarding on which client systems your AI tools may read and which they may change.

Who signs off these connections where you work: IT, the people who use the data, or nobody yet? We'd like to hear how your team has set it up.

Jules, founder of WYNStrategy Director helping agencies and marketing teams use AI properly. More about Jules

← All insights

Let's work out what you need.

Book a free 20-minute call. We'll tell you honestly whether we can help.

Book an intro call