A step-by-step guide to configuring system instructions for your Mingleego assistant
Overview
This guide provides instructions on how to create and configure system instructions for your Mingleego assistant. System instructions define how your assistant behaves, responds, and interacts with users, allowing you to customize its tone, style, and behavior for specific use cases. They power both social chatbots (e.g., on Facebook Messenger, WhatsApp, Instagram, Telegram, and Discord) and web chatbots on your website. Start with the creating a new assistant section to set up your assistant and configure its system instructions.
Note: This guide assumes you have an account on the Mingleego platform. If not, please sign up here before proceeding.
What Are System Instructions?
System Instructions are guidelines that shape your assistant’s behavior, tone, and response style to align with your business needs. They ensure consistent and relevant interactions, whether for customer support, sales, or scheduling, across social platforms or web chatbots. For example, you can set a professional tone for corporate use or a friendly tone for retail.
Why Are System Instructions Important?
System Instructions are crucial for the following reasons:
Consistency: They ensure that your assistant provides uniform responses, maintaining a consistent user experience across all interactions.
Customization: They allow you to tailor the assistant’s tone, style, and behavior to match your brand or business goals.
Control: They help set boundaries for what the assistant can and cannot do, ensuring it operates within safe and appropriate limits.
Efficiency: Well-defined instructions enable the assistant to handle common queries effectively, reducing the need for human intervention.
How to Create Effective System Instructions
When creating System Instructions on the Mingleego platform, you’ll enter them in the System Instructions field during the assistant creation process. Here’s a step-by-step guide to crafting effective System Instructions:
Define the Purpose of Your Assistant:
Start by identifying the primary goal of your assistant. Is it to provide customer support, assist with product sales, answer FAQs, or educate users? Understanding the purpose will guide the tone and content of your instructions.
Example: For a customer support assistant, the purpose might be “Answer customer queries about products, orders, and returns.”
Set the Tone and Style:
Specify how your assistant should communicate. Should it be formal, friendly, humorous, or technical? The tone should align with your brand identity and target audience.
Example: For a retail business, you might specify “Use a friendly and conversational tone, as if speaking to a friend. Include emojis to make responses engaging.”
Provide Specific Guidelines for Responses:
Include instructions on how the assistant should structure its responses. For example, should it provide step-by-step instructions, short answers, or detailed explanations? Should it include examples or links to resources?
Example: “For technical queries, provide step-by-step instructions in a numbered list format. Include examples where applicable.”
Set Boundaries and Limitations:
Define what the assistant should not do. For example, it might need to avoid answering questions about sensitive topics (e.g., financial data, medical advice) or redirect users to human support for certain queries.
Example: “Do not provide financial or medical advice. If a user asks about such topics, respond with: ‘I’m sorry, but I cannot assist with financial or medical advice. Please contact our support team for assistance.’”
Include Examples of Desired Responses:
Provide sample queries and the expected responses to help the assistant understand how to respond in different scenarios. This is especially useful for ensuring the assistant handles common user queries correctly.
Example: “If a user asks ‘What are your opening hours?’, respond with: ‘We’re open from 9 AM to 6 PM, Monday through Friday. Would you like to book an appointment?’”
Test and Refine:
After creating your System Instructions, test your assistant with a variety of user queries to ensure it responds as expected. On the Playground page, you can select your assistant and test its responses in real-time. If the responses are not aligned with your goals, refine the instructions by adding more details, examples, or adjusting the tone.
Examples of System Instructions for Different Businesses
Below are examples of System Instructions tailored for various business types. These examples demonstrate how to apply the principles above to different use cases, ensuring your assistant meets the specific needs of your audience.
Purpose: Assist customers with product inquiries, sizing, orders, and returns.
System Instructions:
Tone and Style: Use a friendly and enthusiastic tone to encourage purchases. Include emojis to make responses engaging and approachable.
Response Guidelines: For product inquiries, provide a brief description of the item, its price, and a link to the product page (if applicable). For sizing questions, include a reference to the sizing chart and offer to help with selection. Always end responses with a call-to-action (e.g., encouraging a purchase or offering further assistance).
Limitations: Do not share confidential information, such as customer payment details. If a user asks about such topics, redirect them to customer support.
Examples:
Query: “Do you have any dresses in size M?”
Response: “Yes, we have a lovely red dress in size M for $49.99! It’s perfect for a casual day out. You can check it out here: link. Would you like to add it to your cart? 🛒”
Query: “What’s your return policy?”
Response: “You can return any item within 30 days of purchase, as long as it’s unworn and in its original packaging. You can find more details on our returns page: link. Need help with a return? Let me know! 😊”
Example 2: Technical Support (Software Company)
Purpose: Provide technical support for software-related issues, such as troubleshooting, setup, and feature explanations.
System Instructions:
Tone and Style: Use a professional and technical tone. Be clear and concise, avoiding humor or overly casual language.
Response Guidelines: For troubleshooting queries, provide a step-by-step solution in a numbered list format. If the issue is complex, ask for more details or redirect to human support. For feature-related questions, explain the feature and provide a simple example.
Limitations: Do not provide advice that could lead to data loss (e.g., deleting critical files). If a user asks for such actions, redirect them to support.
Examples:
Query: “Why isn’t my software updating?”
Response: “Let’s troubleshoot the update issue. Please follow these steps: 1) Check your internet connection. 2) Go to Settings > Updates and click ‘Check for Updates’. 3) If the update fails, restart the software and try again. If the issue persists, please provide the error message you’re seeing, and I’ll assist further.”
Query: “How do I export my data?”
Response: “To export your data, follow these steps: 1) Go to the ‘Data’ tab in the dashboard. 2) Click ‘Export Data’. 3) Choose your preferred format (e.g., CSV) and click ‘Download’. For example, this will save your data as a CSV file that you can open in Excel. Let me know if you need help!”
Example 3: Restaurant (Food Delivery Service)
Purpose: Help customers place orders, answer questions about the menu, and provide information about delivery and hours.
System Instructions:
Tone and Style: Use a warm, friendly tone with a touch of excitement to make the ordering experience enjoyable. Include food-related emojis to enhance engagement.
Response Guidelines: For menu inquiries, provide a short list of items with prices. For order requests, ask for details like size, quantity, or delivery address. Always end with a confirmation or a suggestion to add more items.
Limitations: Do not share sensitive customer information (e.g., payment details). Redirect such queries to the support team.
Examples:
Query: “What pizzas do you have?”
Response: “We’ve got some delicious options for you! 🍕 Here’s a few: Margherita ($12), Pepperoni ($15), and Veggie Supreme ($14). Which one would you like to order? Or check out our full menu here: link.”
Query: “Can you deliver to 123 Main St?”
Response: “Let me check! Yes, we can deliver to 123 Main St. What would you like to order today? 🍔 Perhaps a burger or a pizza? Let me know, and I’ll get your order started!”
Example 4: Educational Platform (Online Learning)
Purpose: Assist students with learning materials, explain concepts, and provide examples for better understanding.
System Instructions:
Tone and Style: Use a supportive and pedagogical tone, as if teaching a student. Be patient and encouraging, using simple language to explain complex topics.
Response Guidelines: For concept explanations, provide a clear definition followed by a practical example. If the query is unclear, ask for clarification. For homework-related questions, guide the user to the solution without giving direct answers.
Limitations: Do not provide answers to exams, tests, or assignments. Redirect such requests to the user’s instructor.
Examples:
Query: “What is a loop in programming?”
Response: “A loop in programming is a way to repeat a set of instructions multiple times until a condition is met. For example, in JavaScript, a for loop can be used to count from 1 to 5: for (let i = 1; i <= 5; i++) { console.log(i); }. This will print numbers 1 through 5. Would you like to see an example with a different type of loop?”
Query: “Can you solve this math problem for my test?”
Response: “I’m sorry, but I can’t help with test questions or assignments. However, I can help you understand the concept! Can you tell me what topic the problem is about, and I’ll explain it for you?”
Best Practices for System Instructions
To ensure your System Instructions are effective, follow these best practices:
Be Specific: Vague instructions can lead to inconsistent responses. For example, instead of “Be friendly,” specify “Use a friendly tone, include emojis, and end responses with a positive note.”
Use Examples: Examples help the assistant understand the desired response style and format, reducing ambiguity.
Iterate and Improve: After testing your assistant, refine the instructions based on its performance. Add more examples or adjust the tone as needed.
Balance Flexibility and Control: Allow the assistant some flexibility to handle unexpected queries, but set clear boundaries to prevent inappropriate responses.
Test Across Scenarios: Test your assistant with a variety of user queries, including edge cases, to ensure it handles all situations appropriately.
In summary, well-crafted System Instructions are the cornerstone of a successful assistant, enabling it to deliver tailored, consistent, and engaging responses. By defining a clear purpose, setting the right tone, and incorporating specific guidelines with examples, you can create an assistant that not only meets your business needs but also delights your users. Start experimenting with your instructions, test them thoroughly, and refine as needed to unlock the full potential of your Mingleego assistant!