The block editor and the AI assistant
When you review a draft, the content is edited as blocks: text, images, buttons and dividers. The preview shows the email as it will land in the inbox, in your brand colours rather than the generic ClevMail palette.
Where the assistant is configured
The assistant's voice, facts and limits are set in Clevi settings, under the Account group in the menu. The screen has five tabs: Brand profile, Knowledge, Memory, Control and Activity.
- Brand profile: who you are and how you sound. The voice comes from here
- Knowledge: documents holding your facts, prices, opening hours, offers
- Memory: what it kept from earlier sessions
- Control: how far it is allowed to go on its own
- Activity: the log, showing where what it wrote came from
Do not confuse Clevi settings with Clevi. The latter, under Content, is where you actually work on an email. The former is where you configure it.
Knowledge holds facts, not orders
Documents in Knowledge reach the assistant as material to read, not as instructions. A sentence written there in the imperative, such as "always write short subject lines", has no effect. Writing rules belong in Brand profile; Knowledge holds facts.
Language and style
Content language and preferred style are chosen in Client settings, in the content and AI section. They set which language it writes in and how formal it is, while the brand profile says what kind of brand you are.
The signature
The signature set in Client settings, under Branding, is added automatically at the end of every email composed after that point. Changing it does not retroactively alter emails already sent.
Articles in the same category
- How to create a campaign draft
Campaigns are created from the Drafts page, not from Campaigns. Name it at the start, because a scheduled campaign can no longer be renamed.
- Who you send to: everyone, a segment, or tags
The three targets in the draft screen, why ticking several tags widens your list instead of narrowing it, and how to read the counter.
- I sent to more people than I expected
Three causes, in the order they show up: tags ticked together, a segment rule left empty, and the templates that break after an import.