Writing good company and brand input
Aivie writes only with what it is given. Its instructions forbid inventing facts, figures, prices, opening hours, cases or customer names, so whatever is not in your input, in the idea group or in the datasources is not on the page. This page explains where your details end up and how to write them so that they help. The screens themselves are described in Company and brand.
Where each detail ends up
The chat assistant, the idea generator and the keyword generator get a block with your details with every request. Which fields are in it:
| Field | In the block |
|---|---|
| Company Name: and Industry: | Always. |
| Mission: and Vision: | Yes, with the switch Include mission and vision. |
| Tone of Voice: | Yes, with the switch Include tone of voice. |
| Services (name and description) | Yes, with the switch Include services. |
| Audiences (name and description) | Yes, with the switch Include audiences. The agents are told to use only these audience names. |
| USPs (name and description) | Only when you turn on Include USPs in the Aivie settings resource under AI → Contexts. It is off in a new installation. |
| Image style | Yes, with the switch Include image style, and always in the prompt of a generated image. |
| Goals | No. You pick one per idea group, and only its name goes to the generator. |
The switches are on the Aivie settings resource in the Aivie contexts, as described in How Aivie uses these details.
Services, audiences and goals
The generator uses these three differently, so write them differently.
- Services. Aivie works a service out in the content: which problem the audience has, how the service solves it and what it delivers. Name the service and use the description for exactly that: the problem, the solution and the result.
- Audiences. An audience decides the tone, the level of knowledge, the examples, the objections and the call to action. Use the name your team uses, because the agents repeat it, and use the description for what this group wants to know and what they doubt.
- Goals. A goal steers the call to action and how commercial the page is, not the subject. Only the name reaches the generator, so make the name say it, for example "Book a demo".
Tone of voice
We recommend describing the tone with examples instead of adjectives alone. "Friendly" can mean many things, but "we write 'you', short sentences, no jargon without a one-line explanation" can be followed. Add a sentence you would write yourself and one you would never write.
Aivie applies the tone of voice to every page, even when another tone would seem to fit the subject better. If blog posts and service pages should sound different, say so in the Layer 2 document of each page type. See Link Layer 2 to your page types.
USPs
Put the selling point in the name and the proof in the description: the number, the certificate, the year. Because Aivie does not invent facts, the proof can only appear on a page when it is written down here. A USP such as "high quality" gives the generator nothing to build on. USPs reach the agents only when Include USPs is on.
What to leave out
- Things that change often, such as prices, offers and opening hours. The details go into every page, so a change leaves every page that repeated them out of date.
- House rules and agreements, such as spelling, words to avoid and the names of your button styles. They belong in the Layer 3 document. See Import a Layer 3 document.
- Long texts. All of it goes with every request, to the chat as well, so short, specific entries work better.
- Words like "customer-oriented" or "innovative" with nothing behind them. Aivie is told to avoid empty superlatives.