Skip to main content
Last updated: 22/08/2025

Best practices


Embedding an agent

1. Ensure responsiveness for mobile devices

To guarantee optimal responsiveness and prevent the agent UI text from appearing too small on mobile devices, include the following HTML tag within the <head> section of your webpage:
This meta tag ensures proper scaling and a good user experience across various devices.

2. Control embedded agent UI dimensions

You can manage the size and position of the agent UI by passing parameters to its style attribute. If necessary, you can also wrap the <mindset-agent> tag within a parent <div> container. For example:

3. Customize embedded agent UI appearance

The <mindset-agent> tag allows for customization of the following:
  • Agent UI Width
  • Agent UI Height
  • Agent UI Background Color: This is only visible for a few milliseconds while the UI loads completely.
Example with background color:
You can also apply additional standard CSS parameters as needed:

4. Agent UI responsiveness for Videos and Segments

The agent UI is designed to be responsive and will adjust content based on the viewer’s screen size. When video content is played, a “Segment” area allows users to navigate between video segments. The display of the segment area depends on the screen width:
  • Right of the video: If the screen width is greater than 1056px.
  • Below the video: If the screen width is less than 1056px.

5. Sample code for embedding an agent in a Single Page Application

Below, a sample React component that embeds a Mindset agent:

6. Embedding an agent in an IFRAME and voice to text feature

In case you embed the agent in an IFRAME, you will have to ensure that the IFRAME has the allow="microphone www.yourweburl.com" attribute set, so the voice to text feature works properly under SAFARI browser.

Agent access control

1. Agent access granted by Agent Sessions

If you embed your agents and provision the knowledge context through the agent Sessions mechanism and APIs, you have the full control over agents’ access. For example, as seen in the tutorial, when you create an AgentSession:
You then give access to the agentUid 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:
  • Open access - all app users
  • Restricted Access - only users with specified account membership
We recommend selecting the restricted access (without assigning any accounts) type because if the agent is restricted, then only users who have been granted access through an agent session will be able to communicate with it.

2. Agent access granted by Account membership

Without the agent sessions mechanism, agents access is managed via the SDK users API. When creating the user session (see authentication), you can specify the accountUids to which the user should be added. This is done by passing the accountUids array in the request body:
if accountUids are provided, the user will be granted to use the agent only if the agent settings are :
  • Open access - all app users
OR
  • Restricted Access with one of the account selected (accountUid1, accountUid2).
In most cases we recommend using agent sessions so you control the users permissions without managing accounts in your Mindset app admin area.

Agent creation

1. Provide clear purpose

✅ Good - specific and actionable purpose: “Answer questions about our e-commerce platform, help with order tracking, and provide product recommendations”❌ Avoid - a vague purpose: “Help customers”
When defining the agent’s purpose, be as specific as possible. A clear purpose helps guide the agent’s behavior and ensures it meets user expectations. Avoid vague descriptions that could lead to confusion or misalignment with user needs.

Why Agent Purpose Matters

The 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.
Characteristics of a Good Agent Purpose
  • Specific: Clearly states what the agent should do.
  • Measurable: Enables evaluation of whether the agent is fulfilling its role.
  • Actionable: Describes tasks or goals the agent can realistically achieve.
Examples of Good Agent Purposes

2. Define Personality Traits

✅ Good - specific personality traits personality: “Professional yet approachable, uses positive language, shows empathy for customer concerns”❌ Avoid - generic descriptions personality: “Nice and helpful”

Personality examples

Below are the available personality types you can use for your agent’s personality field:

3. Specify Clear Formatting Rules

✅ Good - detailed formatting instructions formatting: “Use numbered lists for multi-step processes, bullet points for options, and bold text for important warnings”❌ Avoid - vague formatting: “Be clear”

Formatting examples

Below are the available formatting types you can use for your agent’s formatting field:

4. Set Appropriate Policies

✅ Good - specific boundaries the LLM can implement policy: “Never provide medical advice or health recommendations. Always direct users to consult healthcare professionals.”✅ Good - content restrictions the LLM can follow policy: “Do not mention or compare with products from companies such as Google, Microsoft, or Amazon. Only discuss and provide information about our company’s (ACME Corp) solutions.”❌ Avoid - requires external actions the LLM cannot perform policy: “Escalate complex issues to human agents”

Effective Policy Examples

The policy field should contain rules that the LLM can implement through its responses. Here are examples of effective policies:
Effective Policy Examples

Limitations


1. Single agent per page

Our current implementation still limits the number of agents per page to one. We are working to remove this limitation and will let you know as soon as it is lifted.

2. Supported Google fonts

When using a google font for customizing the agent UI, we do not support 100% of the Google fonts available in that offical list: Google Fonts. We support most of them, but to ensure the font you want to use is supported, please check that Font list: Supported Google Fonts. The font name to use in the fontFamily parameter must be the font name displayed in that Google fonts list. For example:

3. Embed agent voice to text with Firefox browser

The voice to text feature in the embedded agent UI is not supported yet in the Firefox browser.