Assistant Configuration

The Assistant Configuration system provides a streamlined, unified approach to customizing your DataQI assistants. This single configuration page makes it easier to define your assistant’s purpose, behavior, and capabilities in a clear, consistent way.

What You Can Configure

Basic Information

• Assistant Name: Clear, descriptive name for easy identification
• Description: Define the assistant’s role and purpose to improve context and response accuracy

Behavior Settings

• Instructions (Optional): Add specific rules or behaviors

  • Example: “If the question involves pricing negotiations, instruct the user to contact the Procurement Manager”
  • Example: “Always cite sources when providing information”
  • Example: “Use only information from the provided documents”

• Tone of Voice (Optional): Choose the communication style that best suits your environment

  • Professional: Formal, business-appropriate tone
  • Friendly: Conversational, approachable style
  • Technical: Precise, detailed responses
  • Concise: Brief, to-the-point answers

Technical Settings

• AI Model: Select the underlying model powering your assistant
  • Choose based on your specific needs and license tier
  • Balance between speed and accuracy
  • Consider the complexity of your use case

Where to Find Configuration

The Configuration section appears in two places:

During Assistant Creation

• Accessible in the assistant creation flow
• Configure settings before the assistant goes live
• Ensures proper setup from the start

Manage Assistant Page

• Available for existing assistants
• Modify settings as your needs evolve
• Test changes before applying to live assistants

Configuration Benefits

Focused Control

• Single interface for all assistant settings
• Clear, organized configuration options
• Consistent experience across all assistants

Improved Accuracy

• Better context through detailed descriptions
• More relevant responses through specific instructions
• Appropriate tone matching your use case

Easier Management

• Streamlined configuration process
• Clear relationship between settings and behavior
• Reduced complexity for administrators

Best Practices

Assistant Name

• Use descriptive, clear names
• Include department or purpose (e.g., “HR Policy Assistant”)
• Avoid generic names like “Assistant” or “Chat Bot”

Description

• Be specific about the assistant’s role
• Mention the target audience
• Include key capabilities or limitations

Instructions

• Keep instructions clear and specific
• Focus on important behaviors or constraints
• Test instructions with sample questions

Tone Selection

• Match tone to your organization’s culture
• Consider your target users’ preferences
• Ensure consistency across similar assistants

This unified configuration approach gives you focused control over how your assistant behaves while ensuring a more consistent and effective experience across all use cases.