Customizing Your AI Assistant

This comprehensive guide will help you tailor your AI assistant to best serve your specific needs, optimize its performance, and create a unique, engaging experience for your users.

Understanding Customization Options

Agent One provides multiple layers of customization:

Personality: How your assistant communicates and presents information
Knowledge: What your assistant knows and can reference
Tools: Special capabilities your assistant can use
Appearance: How your assistant is presented to users
Behavior: How your assistant handles different scenarios

Basic Customization

Accessing Settings

Go to your dashboard at app.agnt.one
Select the assistant you want to customize
Click "Settings" in the left navigation
Navigate between the different customization tabs

Profile Settings

In the "Profile" tab, you can adjust:

Name: Choose a name that reflects your assistant's purpose or personality
Description: Provide a concise explanation of what your assistant does
Initial Message: Customize the first message users see when they start a chat
Icon: Upload a unique image to represent your assistant (recommended size: 192x192px)

Welcome Message Tips

Your welcome message sets the tone for the entire interaction. Consider:

Clearly stating what your assistant can help with
Suggesting starter questions users might ask
Keeping it concise but friendly

Example welcome messages:

Hi there! I'm TechBot, your technical support assistant. I can help with product troubleshooting, installation guides, and warranty information. What can I help you with today?

Welcome! I'm your travel planning assistant. I can recommend destinations, provide budget tips, or help plan itineraries. How can I assist with your travel plans?

Configuring Assistant Behavior

The "Instructions" tab is where you define how your assistant behaves.

Writing Effective Instructions

Instructions directly influence how your assistant responds to queries. They should include:

Role and Identity: Who the assistant is and what it represents
Tone and Style: How the assistant should communicate (formal, casual, technical, etc.)
Knowledge Areas: Topics the assistant should be knowledgeable about
Limitations: Topics to avoid or specific responses to certain questions
Response Format: How information should be structured

Example Instructions Template

You are [ROLE], representing [COMPANY/ORGANIZATION].

TONE:
- Maintain a [FORMAL/FRIENDLY/TECHNICAL] tone
- Use [SIMPLE/TECHNICAL] language that's easy to understand
- [INCLUDE/AVOID] humor and personality in responses

KNOWLEDGE AREAS:
- You specialize in [SPECIFIC TOPICS]
- You can help with [SPECIFIC TASKS]
- When discussing our products, emphasize [KEY FEATURES/BENEFITS]

LIMITATIONS:
- Do not provide information about [RESTRICTED TOPICS]
- If asked about pricing, [GIVE GENERAL RANGES/DIRECT TO WEBSITE/etc.]
- Never [SPECIFIC BEHAVIORS TO AVOID]

RESPONSE FORMAT:
- Keep responses [BRIEF/DETAILED] but comprehensive
- Format technical instructions as numbered steps
- Include relevant links when appropriate
- For complex topics, break information into sections with headings

COMMON SCENARIOS:
- If a user asks about [COMMON QUESTION], respond with [PREFERRED RESPONSE]
- When users need technical support, collect [SPECIFIC DETAILS] before providing solutions
- If you can't help with a query, suggest [ALTERNATIVE RESOURCES]

Best Practices for Instructions

Be specific: Vague instructions lead to inconsistent responses
Provide examples: Include sample responses for common questions
Update regularly: Refine based on actual user interactions
Test thoroughly: Try various queries to ensure instructions are effective

Knowledge Base

The knowledge base is what allows your assistant to provide accurate, specific information.

Setting Up an Effective Knowledge Base

In the "Knowledge" tab, click "Upload Files"
Select documents relevant to your assistant's purpose
Supported formats include PDF, DOCX, TXT, CSV, and more
After upload, you can organize and add context to documents

Knowledge Base Best Practices

Chunk information logically: Break large documents into topical sections
Use descriptive filenames: Help your assistant understand what each file contains
Include comprehensive information: Cover common questions and edge cases
Keep information current: Remove outdated information and add new content as needed
Structure matters: Well-organized documents are easier for your assistant to reference

Example Knowledge Base Structure

For a product support assistant:

Product_Specifications.pdf
Installation_Guide.pdf
Troubleshooting_Common_Issues.pdf
Warranty_Information.pdf
FAQ_Compiled.pdf

For a real estate assistant:

Property_Listings_Current.pdf
Neighborhood_Guides.pdf
Mortgage_Information.pdf
Buying_Process_Overview.pdf
Rental_Policies.pdf

Email Collection

Email collection allows you to generate leads while providing valuable assistance.

Configuration Options

In the "Tools" tab, find the Email Collection section
Toggle the feature ON
Choose when to collect emails:
- Beginning: Asks for email when the conversation starts
- End: Asks for email as the conversation concludes
Customize the collection prompt to match your brand voice

Example Prompts

Beginning of conversation:

To provide you with the best assistance and follow up if needed, could you share your email address with me?

End of conversation:

I'd be happy to send you additional resources on this topic. What email address should I use?

Email Collection Tips

Explain the benefit: Tell users why sharing their email is valuable
Keep it optional: Don't force email collection if the user declines
Offer value: Provide a reason why the user would want to share their email
Respect privacy: Assure users their email will only be used for relevant communications

Custom API Functions

Custom API functions extend your assistant's capabilities by connecting to external data and services.

Setting Up API Functions

In the "Tools" tab, find the Custom API Functions section
Click "Add API Function"
Configure each API with:
- Function Name: A descriptive identifier (e.g., "check_product_inventory")
- Description: What the function does and when to use it
- Endpoint URL: The API endpoint (e.g., "https://api.yourstore.com/inventory/{product_id}")
- Parameters: Define the input parameters using JSON Schema format

Example API Configuration

For a product inventory checker:

Function Name: check_product_inventory

Description:

Checks the current inventory status of a specific product. Use when customers ask about product availability.

Endpoint URL:

https://api.yourstore.com/inventory/{product_id}

Parameters:

{
  "product_id": {
    "type": "string",
    "description": "The product's unique identifier (SKU or product code)",
    "required": true
  },
  "location_id": {
    "type": "string",
    "description": "Store location ID to check stock at a specific store",
    "required": false
  }
}

API Integration Best Practices

Public endpoints only: APIs must be publicly accessible without authentication
Simple, focused APIs: Each API should do one thing well
Thorough parameter descriptions: Help your assistant understand what each parameter means
Error handling: Ensure APIs return helpful error messages
Test comprehensively: Try different parameter combinations before deployment

Tools and Capabilities

Enable additional tools to enhance your assistant's functionality.

Code Interpreter

Ideal for assistants that need to:

Generate and explain code examples
Format data or perform calculations
Create diagrams or visualizations

To enable:

Navigate to the "Tools" tab
Toggle "Code Interpreter" to ON

File Search

Essential for knowledge base functionality:

Toggle "File Search" to ON
Ensure your knowledge base is properly configured
Your assistant will automatically search these files when answering questions

Integration Options

You can integrate your AI assistant into your website using our embeddable chat widget:

In your agent's settings, find the "Show Embed Code" button
Click the button to reveal the embed code
Copy the provided JavaScript snippet
Paste the snippet into your website's HTML, just before the closing </body> tag

The embed code will look similar to this:

<script src="https://app.agnt.one/embed.js"></script>
<script>
  window.onload = function () {
    window.chatWidgetConfig = {
      url: "https://your-site-subdomain.agnt.one",
      id: "your-agent-id",
    };
  };
</script>

Widget Customization and Behavior

The chat widget has been designed to integrate seamlessly with your website:

Appearance: The widget appears as a circular button in the bottom-right corner of your site (by default)
Activation: When clicked, it expands into a full chat interface
Responsiveness: Automatically adapts to mobile and desktop views
Theme Awareness: Automatically detects light/dark mode preferences

When embedded on your site, the widget will:

Load asynchronously to avoid impacting your page load speed
Display your agent's icon and welcome message
Maintain conversation context throughout the user's session
Close when the user clicks outside the widget or uses the close button

Advanced Embed Options

The embed code can be customized to control the widget's behavior and appearance. While the basic implementation works for most sites, you can adjust:

<script src="https://app.agnt.one/embed.js"></script>
<script>
  window.onload = function () {
    if (typeof initChatWidget === "function") {
      initChatWidget("https://your-site-subdomain.agnt.one", "your-agent-id");

      // The following customizations are available through the widget parameters
      // Position (right or left side of screen)
      // Theme (light or dark mode)
      // Initial message behavior
      // Widget dimensions
    }
  };
</script>

Full Page Integration

For a dedicated chat experience:

Your assistant is automatically available at your site URL (e.g., https://your-site.agnt.one)
You can link to this URL from your main website
Users get a full-screen chat interface optimized for longer interactions

This option is ideal for:

Dedicated support pages
Knowledge base portals
Complex customer service scenarios
Applications where the chat is the primary interface

Testing and Refinement

Continuously improve your assistant through testing and observation.

Test Scenarios

Create a test plan covering:

Common user questions
Edge cases and unusual queries
Complex scenarios requiring multiple back-and-forth interactions
Queries that should trigger API calls
Situations where email collection should activate

Refinement Process

Review actual conversations in your dashboard
Identify patterns where your assistant could improve
Update instructions, knowledge base, or API configurations
Test changes with similar scenarios
Deploy updates when satisfied with improvements

Best Practices Summary

Clear Instructions: Be specific about how your assistant should behave
Comprehensive Knowledge: Provide well-organized, relevant information
Focused APIs: Build simple, reliable API connections
Regular Updates: Keep knowledge and capabilities current
User-Centric Design: Consider the user experience in all customizations

Troubleshooting

Assistant Not Using Knowledge Base

Verify files are in supported formats (PDF, TXT, DOCX)
Check file permissions and upload status
Ensure questions are relevant to uploaded content
Consider reformatting complex documents

API Integration Issues

Verify endpoints are publicly accessible
Check parameter configurations match expected input
Test API calls independently to ensure they work
Review error responses to pinpoint issues

Email Collection Problems

Confirm the feature is enabled
Check that the prompt is appropriate and clear
Verify the timing setting (beginning/end) matches expectations

For more detailed support, please contact our team through your dashboard or refer to the FAQs.