Skip to content

DOSSIER

Every brand gets a dossier that grows with every meeting, file and revision, and becomes the brief your whole team works from.
Take the 3-minute tour
IN THE PRODUCT

When Acme asks for a revision in the portal, the note lands in the brand's dossier as a rule SAI won't break.
Too little to go on? SAI says so. It needs 3 analyzed meetings or 2 finished projects before it judges a brand.

  1. 01

    Feed it

    Upload a guideline, portfolio or brief. SAI reads it and suggests what belongs in the dossier.

  2. 02

    Approve it

    Your team approves each suggested entry. Until it does, SAI doesn't use it.

  3. 03

    Every "no" is written down

    When a client asks for a revision in the portal or for changes to a social post, the note becomes an Avoid rule.

  4. 04

    SAI follows it

    SAI treats each rule as "don't suggest this again". Meeting decisions join the dossier and give context to the next meeting.

Approved knowledge

Voice, tone, likes, dislikes, visual identity, positioning, decisions and history, in one place per brand.

Reads your files

Guidelines, portfolios and briefs become suggested entries your team can approve.

Rejections log

Every client "no" as an Avoid rule. Newest first, up to 50 kept, and your team can delete any.

Decisions that carry over

Decisions from each analyzed meeting are saved to the brand and inform the next one.

Confidence score

A 0 to 100 score on the Memory tab shows whether there's enough to judge the brand.

Outside data status

GA4, Search Console and Buffer connection status stays current for each brand.

What it won't do

Below 3 analyzed meetings or 2 finished projects, SAI refuses to analyze the brand. Nothing is used until your team approves it.

A dossier is the memory SmoothOS keeps for each brand: the client's taste, decisions, files and every rejected direction, gathered from meetings, files and revisions. Your team works from it as the brief, and SAI uses it when it drafts.

From the files you give it, from SAI suggestions your team approves, from meeting decisions and from client revisions in the portal and on social posts.

SAI's brand agent refuses without calling a model, in your language, and says what's missing, for example two more meetings or two more finished projects. The refusal costs nothing.

Yes. A revision note from the portal or a change request on a social post goes into the rejections log on its own. Your team can delete any entry, and the 50 newest are kept.

Yes. SAI reads the dossier with your permissions and treats every Avoid rule as something not to suggest again.