> For the complete documentation index, see [llms.txt](https://docs.artific.nl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.artific.nl/en/for-administrators/tone-of-voice.md).

# Tone of voice

Saved writing styles that assistants and Toolbox elements can apply. Found under **Tone of voice**.

## What it does

Every organisation has a way of writing. Formal or informal, brisk or warm, plain or technical. Left alone, an assistant writes in a generic style that is nobody's.

A tone of voice captures yours once, so it can be applied consistently everywhere instead of being described again in every assistant's instructions.

## Creating one

**Create tone of voice**.

| Field                             | What it does                                   |
| --------------------------------- | ---------------------------------------------- |
| **Name**                          | How you will select it later.                  |
| **URLs for automatic generation** | Pages the platform can read to derive a style. |
| **Description**                   | The style itself, in words.                    |
| **Examples**                      | Sample sentences written in the style.         |

### Generating from your website

Enter one or more URLs (your about page, a few blog posts, a customer newsletter) and choose **Auto-generate**. The platform reads them and fills in the description and examples.

{% hint style="warning" %}
Generating overwrites whatever is in the description and examples. Do it first, then edit.
{% endhint %}

Pick pages that genuinely sound like you. Legal pages and product specifications will produce a tone of voice nobody wants to read.

### Writing the description

Whether generated or written by hand, this is what the assistant follows. Be concrete:

> *Write in plain Dutch, addressing the reader informally. Keep sentences short. Avoid jargon and English loanwords where a normal word exists. Be warm but not chatty. Never use exclamation marks. Get to the point in the first sentence.*

Vague descriptions produce vague results. *"Professional and friendly"* means nothing that the model can act on.

Include what to avoid. Negative instructions are often more effective than positive ones, because they rule out the specific habits you dislike.

### Examples

Two or three sentences written in the style. These do more work than the description. They show rather than tell.

Take them from real material your organisation has published, and pick sentences that demonstrate something specific about how you write.

## Types

| Type                     | What it is                                                                     |
| ------------------------ | ------------------------------------------------------------------------------ |
| **User defined**         | Created by someone in your organisation.                                       |
| **URLs**                 | Generated from web pages.                                                      |
| **Organization defined** | Set at organisation level.                                                     |
| **Predefined**           | Provided with the platform. Read-only: you can view and use it, not change it. |

## Where it is applied

**On an assistant.** In its settings, the **Tone of voice** field under **Messages**.

**In a Toolbox element.** Give the element an input of type **Tone of voice**, and the user picks one when they run it.

The second is the more flexible: one element can write in whichever register the situation needs.

## How many to keep

Most organisations need two or three:

* One default house style.
* One more formal, for external or official communication.
* One more informal, for internal use.

More than that and nobody remembers which to pick. If you find yourself creating a tone of voice per assistant, that content belongs in the assistant's own instructions instead.