The folder knows the client. Now the whole team can talk in it.

If you make material for more than one client, or for one client over many weeks, you know the problem. Every new conversation starts from nothing. You explain who the client is, who will read the thing, what tone they want and what you must never promise them — and then you explain it again tomorrow, and your colleague explains it a third time, slightly differently.

Folders in Projects were built for that. A folder gathers the conversations, the material and the images for one client or one series, and it has instructions: what ANVL should know about the assignment, sent along with every message in the folder's conversations. Two things changed about folders in the last week, and they belong together.

Instructions, written by answering questions

Until now the instructions were an empty text box. An empty box is the hardest thing to fill in well. People wrote one line, or pasted the whole brief, or left it empty.

Now Edit on a folder opens a conversation instead. ANVL asks about what is missing, one thing at a time: who the client is, what the assignment is, who reads the result, how it should sound, what to stress, what must never be promised. Attach the brief or paste a link to the client's own site, and ANVL reads that first and only asks about what it did not find.

While you talk, a draft fills in at the edge of the window — seven fields, and each one says where it came from: You said, From the brief, or ANVL's suggestion. You can change any field with a click, or switch the draft from Cards to Text and write the whole thing by hand. Nothing reaches the folder until you press Save to folder.

The same thing works in the other direction. In an ordinary conversation in a folder, say something that sounds like it should apply to everything — never mention the price in a headline — and ANVL offers to add it to the folder's instructions, as a card with Edit first and Add to the folder. It offers. It does not save on its own.

One conversation, several people

A folder could already be shared with the team, so colleagues could read its conversations and continue in a copy of their own. That is useful for handing something over. It is not how a team actually works on a client, where two or three people are in the same thread on the same afternoon.

So a folder can now be set to The team can write. In that folder, colleagues write and build in the same conversation as the person who started it. Every line shows who wrote it, and ANVL knows who said what when it answers, so your request and your colleague's do not blur into one.

If someone writes while you have the conversation open, it tells you: New messages, and reloading keeps whatever you had half-typed in the box, attachments included. And when an answer or a build finishes while you are in another tab, the tab title says (1).

Some things stay personal even in a shared thread. When several people write in a conversation, ANVL does not read anyone's review queue or recently opened projects into it.

Conversations outside a folder can be shared too, from the conversation's own menu: with one person or the whole team, read-only. They find it under Shared with you and can continue in their own.

Why these two belong together

The instructions are what everyone in the folder agrees the client is. The shared conversation is where the team works on top of that agreement. Without the first, three people in one thread each bring their own idea of the client. Without the second, the instructions are good but everyone uses them alone.

If you are evaluating ANVL for an agency or a team: this is the unit to think in. One folder per client, the brief written once by answering questions about it, and one place where the people on the account talk to ANVL — and to each other — with the same starting point.