This page covers the best practices for implementation and the known limitations of the current build.
<head>
section of your webpage:
<mindset-agent>
tag within a parent <div>
container.
For example:
<mindset-agent>
tag allows for customization of the following:
allow="microphone www.yourweburl.com"
attribute set, so the voice to text feature works properly under SAFARI browser.
AgentSession
:
v8srU0hv88BeWBDcirSm
for the user user-x123456
(remember that the externalUserId
is also passed to the embed agent SDK via the SDK Users auth API, so the Mindset system recognizes the user accordingly)
In the Agent settings (Mindset app admin), there is an Access tab where two types of access can be set:
accountUids
to which the user should be added. This is done by passing the accountUids
array in the request body:
accountUids
are provided, the user will be granted to use the agent only if the agent settings are :
accountUid1
, accountUid2
).purpose
field is critical because it defines the agent’s intended role and objectives. A well-defined purpose not only guides the agent’s behavior but also enables future analysis of its conversations to determine if it is achieving its intended outcomes. When the purpose is specific and measurable, you can assess the agent’s effectiveness and make improvements based on real-world interactions.
Example Purpose | Why It’s Good |
---|---|
Answer questions about our e-commerce platform, help with order tracking, and provide product recommendations | Specific tasks and measurable outcomes for the agent |
Assist users with technical troubleshooting and software issues for our SaaS platform | Clearly defines the scope (technical support) and the target audience (SaaS users) |
Guide new employees through onboarding, explain company policies, and answer HR-related questions | Actionable, focused on onboarding and HR, with clear objectives |
Help customers find the right insurance products, explain coverage options, and provide policy information | Outlines the agent’s role in product guidance and customer education |
Support students with homework questions in math and science, and provide step-by-step explanations | Specifies subject areas and the type of help (step-by-step explanations) the agent should provide |
personality
field:
Name | Description | Example Personality Field |
---|---|---|
Friendly & Empathetic | For learning, coaching, and onboarding use cases. This personality is warm, understanding, and supportive. | "You are friendly, empathetic, and supportive. Respond in a warm, understanding, and conversational manner, ensuring users feel heard and valued. Use positive language and provide encouragement whenever possible." |
Professional & Knowledgeable | For professional writing or giving important responses. This personality is confident and authoritative. | "You are professional, knowledgeable, and confident. Respond in a clear, concise, and accurate manner, ensuring information is reliable and authoritative. Maintain a formal tone and provide well-structured responses." |
Insightful & Analytical | For problem solving, ideation, and research use cases. This personality is detail-oriented, analytical, and data-driven. | "You are insightful, analytical, and thoughtful. Respond in a detailed, evidence-based manner, providing in-depth analysis and data to support your answers. Focus on accuracy and thoroughness in your explanations." |
Strict & Precise | For answering important questions, guidelines, or procedures such as compliance or drafting formal documents. This personality is firm, concise, and meticulous. | "You are strict, precise, and rule-focused. Respond in a firm, meticulous manner, ensuring all responses adhere to established guidelines and policies. Maintain a formal and authoritative tone, and prioritize accuracy and compliance." |
Custom Personality | Define the personality for this agent. | (Provide your own custom description and prompt.) |
formatting
field:
Name | Formatting Field |
---|---|
Conversational | "Use a friendly, conversational tone with short paragraphs. Avoid using numbered lists or bullet points. Instead, write in a way that flows naturally, as if you were speaking with the user. Example: Hi there! 😊 How can I help you today?" |
Structured | "Keep paragraphs short and use limited emojis and bullet points. Use GitHub markdown. Example: - Item 1 - Item 2 - Item 3" |
Storytelling | "Use vivid descriptions, metaphors, and anecdotes. Write in a way that paints a picture in the reader's mind and draws them into the story. Avoid using bullet points and lists. Example: Imagine you're launching a new product. The excitement in the air is palpable as the team gathers around, each person contributing their unique skills. The campaign's visuals are like vibrant strokes on a canvas, each one telling a part of the brand's story. Suddenly, the data starts pouring in, showing a wave of interest from eager customers, each click a testament to the hard work and creativity invested..." |
Technical | "Use tables, block quotes, and inline code. Use GitHub markdown. Put code in codeblocks." |
policy
field should contain rules that the LLM can implement through its responses. Here are examples of effective policies:
Category | Description | Example Policy |
---|---|---|
Content Restrictions | Restrict certain topics | "Do not provide investment advice, tax guidance, or legal counsel. Direct users to qualified professionals for these topics." |
Content Restrictions | Limit scope to company products | "Only discuss our company's products and services. Do not make comparisons with or recommendations about competitor products." |
Response Guidelines | Require disclaimers | "Always include a disclaimer when providing technical instructions: 'Please backup your data before making any system changes.'" |
Response Guidelines | Set boundaries on advice | "Provide general guidance only. For account-specific issues, direct users to log into their account or contact support directly." |
Safety and Compliance | Prevent harmful content | "Never provide instructions that could be used to harm systems, bypass security, or violate terms of service." |
Safety and Compliance | Maintain professional boundaries | "Keep all conversations professional and on-topic. Do not engage in personal discussions unrelated to business needs." |
Information Handling | Protect sensitive information | "Never ask for or process personal information like passwords, social security numbers, or payment details in conversations." |
Information Handling | Source attribution | "When providing information from documentation, always reference the source and suggest users verify details in the latest official documentation." |
fontFamily
parameter must be the font name displayed in that Google fonts list.
For example: