Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.vivi.bot/llms.txt

Use this file to discover all available pages before exploring further.

A prompt is a written set of instructions that defines how an agent should act, respond, and communicate. The prompt is the foundation of every agent. It determines how the agent answers questions, applies knowledge bases, and interacts with users. Each prompt is given a name for clarity and organization and versioned automatically to help you track and manage changes over time. To create a prompt, navigate to the Prompt tab in your workspace. You can either build your own prompt or use one of our templates to get started. Prebuilt templates provide a strong foundation for common use cases and can be fully customized to fit your needs. Follow these steps to create a prompt:
1

Set a Name

Assign each prompt a clear, descriptive name that reflects the agent’s purpose or function.
2

Add the Prompt Body

Add the prompt body information, formatted in Markdown text. A prompt body should contain the following sections:
  • Role and persona definitions
  • Tone and style guidance
  • Guardrails or behavioral rules
  • Instructions for referencing knowledge bases and integrations
  • Example inputs and outputs for better clarity
3

Save and Version

  • Each time a prompt is saved, it automatically becomes a new version.
  • Agents use the latest prompt version by default, but you can pin a specific version to use if needed.
4

Archive and Reuse

Archived prompts are removed from the active dashboard but remain accessible for restoration or reuse in future agents.

​
AI Assist

AI Assist helps you transform rough ideas into polished, production-ready prompts without starting from scratch.
1

Start with what you have

Open any prompt and click on the AI Assist button. Describe what you want to change or improve, as generally or specific as you’d like to be.
2

Review suggested changes

AI Assist restructures your prompt into clear sections with role definitions and tool guidelines, then presents the suggestions in a side-by-side diff view that highlights changes in green.
3

Accept or reject

Accept the changes that work, reject what doesn’t, and keep iterating. Your full prompt history is preserved throughout the process.

​
Best Practices

  • Write clearly and directly — be explicit about the agent’s goals and boundaries.
  • Include guardrails to prevent unwanted behavior.
  • Reference how to use knowledge bases or tools (e.g. “Use the CRM integration for customer lookups”).
  • Start with a template, then refine based on your use case.