Re:PREZIO
Knowledge & behaviour

Variables / Business context

Under "Business variables" you store fixed facts about your business as simple key/value pairs — for example opening hours, phone number, address or prices. Unlike knowledge content, which the agent has to look up first, these variables are fed directly into the agent's instructions always and on every reply. Use this area for the few hard facts that the agent must never overlook.

You'll find this area in the dashboard under Agents → (your agent) → Variables.

How it works

Each variable consists of two parts:

  • Key — the name of the piece of information, e.g. opening_hours. Displayed in a monospace font in the editor so that technical names are easy to read.
  • Value — the actual content, e.g. Mon–Fri 9–18, Sat 10–14.

Behind the scenes, Prezio builds a fixed block for the agent from this, headed "# Business context", in which each variable appears as its own line in the format - key: value. This block is appended to every reply regardless of the channel — whether WhatsApp, SMS, web chat, email or phone.

Step by step

Step 1: Create your first variable. As long as no variable exists yet, you'll see an empty view with the note "No variables yet" and the "Add variable" button. Click it to create the first row. The table with the two columns "Key" and "Value" then appears.

Step 2: Enter the key. On the left, enter a short, descriptive key. We recommend English identifiers in lowercase with underscores, because the agent processes these cleanly in the prompt — for example: - opening_hours - phone - address - parking - price_haircut or lunch_price (specific prices)

The key is automatically trimmed of leading/trailing whitespace when saved. Important: there is no enforced rule for the spelling — you could in theory also use German keys such as öffnungszeiten. However, stick to a consistent style within a single agent.

Step 3: Enter the value. On the right, enter the specific content, in completely normal language. Examples: - opening_hours → Mon–Fri 9–18, Sat 10–14, closed on Sun - phone → +49 30 1234567 - address → Musterstraße 1, 10115 Berlin - price_haircut → Women from £45, men from £28

The value may contain punctuation, currency symbols and several details. Even so, keep it concise and unambiguous — the agent often passes these details on to customers almost word for word.

Step 4: Add more variables. Using the "Add variable" button (with the plus symbol), you can create as many additional rows as you like. There is no fixed upper limit on the number of variables; technically the field is an open mapping of key to value. Even so, don't overdo it (see tips).

Step 5: Delete a variable. At the right-hand edge of each row you'll find a red trash icon (the "Remove variable" action). One click removes the entire row.

Step 6: Save. Changes only take effect once you click "Save changes" at the bottom. As long as there are unsaved changes, you'll see the "Unsaved changes" note and the save button is active. With no changes, the button stays disabled — so Prezio never sends an empty save.

Key fields at a glance

  • Key — name of the piece of information.
  • Function: heading of the row in the agent's business context block.
  • Default: empty (no variables predefined; the default is an empty list).
  • Recommendation: short, English snake_case identifiers such as opening_hours, phone, address.
  • Value — content of the piece of information.
  • Function: passed to the agent after the key as - key: value.
  • Default: empty.
  • Recommendation: one precise, complete detail per variable; not whole paragraphs.

Tips & pitfalls

  • Empty values are ignored. If you leave the value field empty, the variable silently drops out when the agent instructions are assembled — the key alone has no effect. So a variable you've created only takes effect once a value has also been entered.
  • Rows without a key disappear on save. If you enter only a value with no key, that row is discarded when you save. The key is mandatory for the information to be retained.
  • Duplicate keys overwrite each other. If you use the same key twice, only one value remains in the end. Assign each key only once.
  • Variables are not a knowledge base. They are intended for a few, permanently valid key facts that are always sent along. Long texts, FAQ collections or menus belong in the knowledge base, not here — otherwise you needlessly bloat the agent instructions and increase the cost per reply.
  • "Always in the prompt" means: it costs on every reply. Because the business context block is sent along with every single reply, very many or very long variables drive up token consumption (and thus the agent's daily budget). Keep the list lean.
  • Facts entered here are given priority. Because variables are fixed in the instructions, they are more reliable than content the agent first has to look up in the knowledge base. If a figure absolutely must be correct (e.g. the current phone number), a variable is the safest place.
  • Save on every change. Switching to another menu item in the sidebar does not automatically discard your edits, but they only take effect after you click "Save changes". Watch out for the "Unsaved changes" note.