The assistant editor brings together everything that determines how your phone assistant behaves. It's split into two tabs: "Behaviour" (how the assistant talks and what it knows) and "Technical" (availability, routing, delivery, security). This article describes the sections in that order.

The assistant editor is the central configuration surface for a Loomira assistant: every setting — from the persona to number blocking — is maintained there, and only takes effect on new calls after you save.

Persona, Instructions, and Languages

Under "Persona", you set how the assistant introduces itself on the phone: its name, a role description (e.g., "Front desk" or "Appointment booking"), the tone, and the grammatical form of address. These settings feed into the system prompt — they aren't just a display name, they actually shape how responses are phrased.

In the "Instructions" field, you enter free text that the assistant takes into account on every call — for example, industry-specific details, things it must never promise, or how to handle certain requests. The editor shows a preview of the last saved, actually assembled prompt, so you can see how your instructions play out together with the other settings.

Under "Languages", you enable which languages the assistant speaks — German, English, French, Italian, Dutch, and Spanish are available — and set the default language it opens conversations in. The default language must itself be enabled, so its toggle is locked.

Greeting & AI Disclosure

The greeting and the AI disclosure are managed together, because both merge into one spoken opening at the start of every call. A live preview in the section shows, word for word, what callers will hear in the default language — making it easy to spot, for instance, if a custom greeting duplicates the disclosure.

The disclosure is on by default: at the start of the call, callers learn that they're speaking with an AI system — as required by Article 50 of the EU AI Act. This isn't a cosmetic setting but a legal obligation for automated voice interaction with consumers, which is why we turn it on by default.

You can turn off the automatic announcement, but doing so is deliberately given a hurdle: you must explicitly confirm how you ensure disclosure instead (for example, via an announcement before the call, on your website, or in your terms), and that statement is logged with your name. Without such confirmation, the disclosure stays on.

What Does the Assistant Know? FAQ and Knowledge Sources

Two sections give the assistant factual knowledge:

  • "FAQ" — short question-and-answer entries (title + content, up to 50 per assistant), ideal for the ten things people ask on the phone again and again.
  • "Knowledge" — here you attach your workspace's knowledge sources (text, PDFs, websites) to the assistant, up to 20 per assistant. You manage the sources themselves centrally; details and plan limits are under Knowledge Base.

Availability and Routing

Under "Availability", you maintain one or more time ranges per weekday (up to eight per day), along with a timezone; a day with no time range counts as closed. Under "Routing", you decide what happens after hours — take a voicemail, announce hours, or transfer the call to a number of your choice — and what the assistant does on an unrecoverable error: apologize and end the call, or also transfer.

Delivery, Integrations, and Website Widget

  • "Email": Enter an address that receives a full transcript after every call — your own inbox, never the caller's. Leaving it blank turns off transcript emails (see Transcripts & Messages).
  • "Integrations": Per assistant, you turn on which connected tools it uses after a call — for example, a short call summary posted to your Slack channel, or logging to your HubSpot CRM. Providers themselves are connected centrally on the portal's integrations page.
  • "Website widget": A code snippet for your website that lets visitors talk to the assistant directly in the browser — no phone number needed at all. For security, you explicitly list the allowed website addresses (origins).
  • "Webhooks" and "Tools" are aimed at technical users: signed events sent to your own systems, and connecting your own tools (e.g., MCP servers).

Recording, Spam & Security

Call recording is off by default — the transcript is created independently of it. If you turn it on, you must inform callers (an automatic announcement can be enabled) and ensure its data-protection lawfulness yourself; more on this under Privacy.

Under "Spam & security", you block individual phone numbers (calls are declined before they reach the assistant) and can optionally set a usage limit — a cap on calls or minutes per day or month that limits abuse and cost spikes.

Saving Changes, Activating, Testing

Changes only take effect after saving; as long as a draft is unsaved, your assistant answers calls with the last saved version, and the editor warns you before leaving if you have unsaved changes. Required fields and conflicts are shown directly at the relevant section via a checklist. Activated assistants can be tried out with a test call in the browser — you hear exactly the opening that real callers hear.