Set your business context and voice

What business context is

A set of facts about your business — what you sell, who buys it, what you decline — which are condensed into a compact brief and attached to every generation.

Two things follow from that design:

• Only the brief is sent, not your raw answers or uploaded documents. It is capped in length, which is why concise, factual answers outperform long ones.
• Rebuilding the brief is an explicit step. After editing your answers, rebuild it so the change reaches your drafts. This is deliberate — it means the reply path never pays for a summarising call while you are waiting for a draft.

The brief is supplied to the model as reference material, not as instructions, with a standing rule to use those facts only where they genuinely answer the post and never to state anything the facts do not cover.

What to write

Write it as a briefing for a competent new employee, not as an About page. The two have opposite goals: one is written to be specific, the other to impress.

The "what you decline" field does more work than its size suggests. It is what stops a draft being accommodating about work you do not want, and it is what makes a "no" come back as a clear no.

If your description would also be true of four competitors, you have described a category rather than a business — and drafts will read like the category.

Social accounts

You can record the accounts you post from and the pages and groups you follow. Each entry is a title and a description, both required.

The description is the point. "12k agency owners, workflow questions, self-promo gets removed" teaches the model something; a bare link teaches it nothing. These feed into the brief so drafts know whose rooms you are writing in.

These are stored notes, nothing more. Nothing fetches, scrapes or signs in to any account you list here.

Your voice

Separate from the facts, and the highest-leverage setting in the product: your voice instructions are layered last in the prompt, after the structural scaffold, the length default and the style rule. Last means they win where they contradict anything else.

Write it concretely:

Short sentences. Contractions. First person singular — I, not we.
Direct: say what the problem is before saying what it will take.
No exclamation marks, ever.
Never say "reach out", "touch base", or "at your earliest convenience".

That final line — the words you never use — is worth more than every positive tone adjective combined, because a prohibition can be checked and an adjective has to be interpreted.

Learn my writing voice

If describing your own style feels like guesswork, do not describe it — derive it.

Learn my writing voice reads a sample of writing you have already published and produces a reusable description of how you write: tone and register, sentence length and rhythm, vocabulary level, punctuation habits, emoji and hashtag use, how you open and close, and recurring quirks.

1. Gather a sample of your real posts or replies — the ordinary ones, not your best ones.
2. Run Learn my writing voice over the sample.
3. Read the description. It will name habits you did not know you had.
4. Cut anything that was an accident of the sample rather than a habit.
5. Save it as your voice instructions.

It describes only what the sample evidences, so a thin sample produces a thin description. Twenty real replies beat three polished posts.

Checking it worked

Test on the hard cases, not the easy one:

The saying-no test is the most diagnostic. If your "no" comes back as a soft maybe, the missing piece is the "what you decline" field.

Change one field at a time between tests, or you will not know which change fixed it.