Prompt Composer

The Prompt Composer helps you build a comprehensive system prompt section by section, instead of writing one big block of text. Each section can be enabled or disabled independently, making it easy to iterate on your bot's behavior.

Accessing the Prompt Composer

Open the Prompt Composer from the sidebar in your dashboard, or navigate directly to /prompts.

  1. 1Log in to your Voquii dashboard
  2. 2Click Prompt Composer in the sidebar
  3. 3Select the bot you want to configure

Prompt Sections

Each section focuses on a specific aspect of your bot's behavior. Toggle sections on or off depending on what your bot needs.

1

Identity & Role Required

Who is the bot? Define the company name, the bot's role (e.g., "customer support assistant"), and its core personality. This is the only required section.

2

Tone & Personality

Set the conversational style — professional, friendly, casual, empathetic, or a custom blend. This shapes how the bot phrases its responses.

3

Response Rules

Control response length, formatting preferences (bullet points vs. paragraphs), and citation rules (whether to link back to source pages).

4

Knowledge & Context

Define what topics the bot covers and what it should reference. Point it to specific content areas or tell it to prioritize certain sources.

5

Boundaries & Safety

Specify what the bot should decline to answer, and provide escalation instructions (e.g., "Direct the customer to support@company.com for billing questions").

6

Voice Optimization

Tips and rules for spoken responses — shorter sentences, no markdown formatting, conversational phrasing. Enable this if your bot uses voice chat.

7

Booking Rules

When and how the bot should offer to schedule appointments. Define required information to collect and available booking slots.

8

Custom Instructions

A free-form section for any additional rules or behaviors that don't fit into the other categories.

Quality Checklist

The Prompt Composer runs 5 automated checks on your prompt to help you catch common issues before going live.

Identity defined — Bot knows who it is and what company it represents
Safety rules — Boundaries are set for sensitive topics
Escalation path — Users can reach a human when needed
Tone set — Conversational style is clearly defined
Reasonable length — Prompt is concise enough for reliable performance

Live Preview

Test your prompt against your actual knowledge base without leaving the Prompt Composer. The chat preview panel lets you send test messages and see how the bot responds with your current prompt and indexed content.

Changes in the composer are reflected in the preview immediately. Save your prompt when you're satisfied with the results.

Prompt Generator

For a quick start, the auto-generator at /prompt-generator creates a complete system prompt from a few inputs. Provide your business details and the generator builds a ready-to-use prompt.

Generator Inputs

FieldDescription
Business nameYour company or brand name
IndustryE.g., e-commerce, healthcare, legal services, SaaS
ToneProfessional, friendly, casual, or empathetic
GoalsWhat the bot should accomplish (support, sales, scheduling)
Compliance modeOptional — HIPAA, legal, or financial compliance guardrails

Prompt Writing Tips

Keep it concise

Prompts under 2000 words perform best. Long prompts can cause the model to lose focus on important instructions.

Be explicit about what NOT to do

Negative instructions are just as important as positive ones. Tell the bot what topics to decline, what promises not to make, and when to escalate.

Include escalation instructions

Always tell the bot what to say when a customer asks for a human. For example: "If the customer asks for a human agent, say: 'I'd be happy to connect you with our team. Please email support@company.com or call (555) 123-4567.'"

Optimize for voice

If your bot uses voice chat, add: "Keep responses concise, under 2–3 sentences. Do not use markdown formatting, bullet points, or URLs in your responses."

Avoid vague instructions like "be helpful." Instead, be specific: "Answer product questions using the knowledge base. If the answer is not in the knowledge base, say you don't have that information."

Next Steps