Chatbot Configuration

The chatbot detail page provides all settings to customize your chatbot's behavior and identity. You'll find these settings on the Configuration tab.

AI Provider Selection

Choose your AI provider:

Each chatbot can use a different provider and model. Choose based on your quality requirements, response speed, and cost preferences.

Model Selection

Available models depend on your selected provider. Generally:

• Larger models (e.g. gpt-4.1-mini, gemini-2.5-flash) produce higher-quality answers but cost more per message
• Smaller/Lite models (e.g. gpt-4o-mini, gemini-2.5-flash-lite) are faster and cheaper, suitable for simpler use cases

Service Name

Enter your business or service name (e.g. "ACME Corp" or "TechSupport Pro"). The chatbot uses this to:

• Identify itself when asked who it represents
• Provide contextually relevant answers about your organization
• Reference your business name naturally in conversations

Example: If your service name is "CloudStore", the chatbot might say: "At CloudStore, we offer free shipping on all orders over $50."

Chatbot Name

An internal name used to identify your chatbot in the dashboard. This name is not shown to visitors — it's only for your own reference when managing multiple chatbots.

Examples: "Website Support", "Sales Bot EN", "FAQ Chatbot"

Allowed Domains

Select which domains are permitted to load the chat widget. This is a security-critical setting.

• Only domains you control should be listed
• The widget will not load on unlisted domains
• This prevents unauthorized sites from embedding your chatbot
• Add all domains where you want the widget to appear (e.g. example.com, shop.example.com)

Timezone

Sets the chatbot's time awareness for accurate time-based responses. This affects:

• Business hours references ("We're open from 9 AM to 5 PM")
• Appointment scheduling (when using the Appointments tool)
• Time-sensitive greetings ("Good morning!")

Select the timezone that matches your business location.

Custom Role (System Prompt)

The custom role defines your chatbot's personality, behavior, and boundaries through a system prompt. This is a paid feature (available on Basic plans and above).

What to Include

• Role definition: What the chatbot is and what it does
• Tone and style: Formal, casual, friendly, technical
• Boundaries: What topics to avoid, when to escalate
• Domain knowledge: Specific terminology, rules, or processes
• Response format: Preferred answer length, use of lists, etc.

Example System Prompts

Customer Support Bot:

You are a friendly customer support agent for CloudStore, an online electronics retailer. 
Always be helpful, patient, and professional. Answer questions about our products, 
shipping policies, and return process. If a customer seems frustrated, acknowledge 
their concern before providing a solution. For billing disputes or account issues, 
suggest contacting our support team at support@cloudstore.com. Never discuss competitor 
products or provide personal opinions.

Technical Documentation Bot:

You are a technical documentation assistant for DevTools API. Provide accurate, 
concise answers about our API endpoints, authentication, and SDKs. Always include 
code examples when relevant. Use technical language appropriate for developers. 
If you're unsure about a specific implementation detail, say so and recommend 
checking the official docs. Never generate fake API endpoints or example responses.

Sales Assistant:

You are a sales assistant for FitGear, a sports equipment brand. Help visitors 
find the right products based on their needs. Ask clarifying questions about their 
sport, skill level, and budget. Highlight product benefits and current promotions. 
If they're ready to buy, guide them to the product page. Always mention our 
30-day return policy to reduce purchase anxiety.

Tips for Effective Prompts

• Be specific — Vague instructions lead to inconsistent behavior
• Set boundaries — Clearly define what the chatbot should and shouldn't discuss
• Include examples — Show the chatbot how you want it to respond in specific scenarios
• Test and iterate — Try different prompts and refine based on actual conversations
• Keep it focused — Overly long prompts can confuse the model; aim for clarity over completeness