Skip to main content

Understand runtime context

The text saved in the Prompt Editor is the authored prompt. It is not the complete instruction set a model receives. Wirevox compiles it with current context and configured capabilities before the conversation.

Compilation sequence​

The core prompt compiler processes the authored prompt in this order:

  1. Resolve custom variables.
  2. Resolve configured built-in variables.
  3. Prepend current local date, time, and caller-phone context.
  4. Inject attached knowledge-base instructions or description.
  5. Replace any remaining {{...}} placeholders with not provided.
  6. Resolve exact function markers against actions available to the conversation.
  7. Add channel, language, interruption, voice-delivery, direction, and transfer context where applicable.

The runtime can add further provider-specific session instructions, but authors should not duplicate provider implementation details in the business prompt.

Date and time​

Wirevox prepends:

  • the current local date in a readable format;
  • the ISO date;
  • the current local time; and
  • an instruction to use them for relative dates and business-hours reasoning.

The value uses the timezone configured for the agent. If no timezone is configured, the current compiler falls back to America/New_York.

Do not hard-code today's date or current time in the system prompt. Configure the correct timezone and write business rules instead:

For same-day requests, follow the current local date and time supplied by Wirevox. Do not promise service outside {{business_hours}}.

Known caller phone​

For a voice call with a known caller number, Wirevox tells the model that the number is already confirmed and should not be requested or reverified. When an action requires a phone argument, the runtime instructs the model to use that number unless the caller voluntarily provides a different one.

When no number is available, the runtime states that the agent must ask for it if an action requires it.

Do not add a blanket instruction to ask every caller for a phone number. Define only the business condition under which contact information is required.

Known website visitor details​

Website chat uses the same core compiler and can include known visitor or contact details. The chat runtime tells the model not to request information that has already been supplied.

The chat runtime also adds channel rules that prohibit references to calls, speaking, listening, or voice delivery and asks for concise, scannable responses.

Knowledge-base context​

When a knowledge base is attached and has instructions or a description, Wirevox injects that guidance:

  • at {{knowledge_base}} when the token exists; or
  • at the end of the compiled prompt when the token is absent.

When no knowledge base is attached, a {{knowledge_base}} token becomes a safe instruction not to guess business-specific information.

The injected description or instructions are not the same as the retrieved source content. During a conversation, the knowledge-search capability retrieves relevant chunks according to the attached base and retrieval threshold.

Function context​

A during-conversation action should be referenced with its exact marker:

[[Function: exact_tool_name]]

When that action is available, the compiler replaces the marker with a reference to the available action. If a legacy reference is unavailable, it becomes a safe human-follow-up instruction instead of permission to pretend the action succeeded.

The prompt must still define the trigger, required inputs, confirmation, ordering, and success or failure behavior. Attachment and prompt authoring remain separate responsibilities.

Unresolved placeholders​

After configured values and knowledge have been processed, Wirevox replaces any remaining double-brace placeholder with:

not provided

This avoids exposing editor placeholders in a live conversation. It can still produce an incomplete or awkward instruction, so resolve warnings before testing or publishing.

Draft and published context​

Browser tests use the current saved draft configuration. Live conversations use the published version, including its variables, knowledge-base association, functions snapshot, model, and other settings.

Real-time date, time, caller, and visitor context are computed for the new conversation; they are not frozen at publish time.

Keep the authored prompt clean​

Do not duplicate:

  • current date or time;
  • known caller-number rules;
  • known visitor details;
  • raw knowledge-base content;
  • internal tool schemas;
  • provider implementation instructions; or
  • voice-delivery configuration already controlled by the editor.

Use the authored prompt for durable business policy and use each runtime layer for the type of information it is designed to supply.

Next steps​