Prompt Templates

Prompt templates are configurable system prompts stored outside your application code. They define your node's personality, behavior, and instructions. You can update templates through the dashboard or API without changing code or redeploying your application.

Edit templates through the Interlocute dashboard or update them programmatically via the API. Changes take effect immediately for new conversations. Existing threads continue using the prompt they started with unless you explicitly update them.

Yes. Templates support variable substitution so you can inject dynamic context like user names, dates, or custom metadata. Variables are evaluated at runtime and inserted into the system prompt before the LLM processes the request.

Every template change creates a new version with a timestamp and audit trail. You can view the history of prompt changes, compare versions, and roll back to previous templates if needed. This makes it safe to experiment with prompt refinements.

Yes. You can create multiple prompt templates and route different users or conversations to different templates. This allows for A/B testing prompt strategies to determine which produces better results for your use case.

By default, ongoing threads continue using the prompt template they started with to maintain consistency. You can opt-in to updating existing threads with the new template if you want to apply changes retroactively.

Absolutely. Import existing prompts into Interlocute as templates. The template system is flexible — it supports plain text, structured formats, and variable substitution, so most existing prompts can be migrated without modification.

Prompt storage and updates are included in the platform. There are no separate charges for managing templates. You only pay for token usage when the node processes requests using those templates.