> 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/assistants/creating-an-assistant.md).

# Creating an assistant

How to create a new assistant, and what to put in the three fields you are asked for.

Go to **AI assistants → Assistants** and choose **Create assistant**. You need the create right for assistants; if you do not see the button, ask whoever administers your organisation.

## The three fields

| Field               | What it is                                                                                                                                           | Example                                                    |
| ------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------- |
| **Name**            | What the assistant is called, everywhere in the platform.                                                                                            | `HR Helpdesk`                                              |
| **Scope**           | A one-line description of what it is for. It appears under the name on the overview card, and is later called **Short description** in the settings. | `Answers questions about leave, salary and staff policies` |
| **Opening message** | The first thing the assistant says when someone starts a conversation.                                                                               | `Hello! Ask me anything about our HR policies.`            |

A preview panel on the right shows how the assistant will look while you type.

Choose **Create assistant** to save. You land on the settings, where the real configuration happens.

## Writing a good opening message

The opening message does more work than it looks. It sets expectations, and it is the cheapest way to prevent disappointment.

* Say what the assistant knows about, not just hello. `Hello, how can I help?` tells the user nothing.
* Say what it does **not** cover, if that is a common misunderstanding.
* Keep it to one or two sentences.

A useful shape: *"Hi, I can answer questions about our HR policies, based on the staff handbook. For anything about your own contract, contact HR directly."*

## What to do next

The assistant exists but is empty. Continue with:

1. [Settings](/en/for-administrators/assistants/settings.md): the instructions that shape its behaviour.
2. [Knowledge and sources](/en/for-administrators/assistants/knowledge-and-sources.md): what it may draw on.
3. [Preview and embedding](/en/for-administrators/assistants/preview-and-embedding.md): try it before anyone else does.

{% hint style="warning" %}
Deleting an assistant cannot be undone, and any chat window embedded on a website using it stops working immediately. The confirmation asks you to type the assistant's exact name, on purpose.
{% endhint %}