Creating an Assistant
Configuration Options
- Name — A clear, descriptive name (e.g., “Customer Support Bot” or “Code Reviewer”)
- Description — A brief summary of what the assistant does, visible to workspace members
- System Prompt — The instructions that define how the assistant behaves
- Temperature — Controls creativity. Lower values produce more focused, deterministic responses. Higher values produce more creative, varied responses.
- Max Tokens — The maximum length of responses the assistant can generate
Writing Effective System Prompts
The system prompt is the most important part of your assistant’s configuration.Be specific about the role
Be specific about the role
Instead of “You are a helpful assistant,” try “You are a senior customer support agent for a SaaS company. You help users troubleshoot billing issues, account access problems, and feature questions.”
Define the tone and style
Define the tone and style
Specify whether the assistant should be formal or casual, concise or detailed. For example: “Respond in a friendly, professional tone. Keep answers under 200 words unless the user asks for more detail.”
Set boundaries
Set boundaries
Tell the assistant what it should and should not do. For example: “Never make up information. If you do not know the answer, say so and suggest the user contact support.”
Provide examples
Provide examples
Include example interactions in the system prompt to show the assistant exactly how you want it to respond.
Visibility Settings
Visibility controls who in your workspace can see and use the assistant.| Visibility | Who Can Access |
|---|---|
| Public | All workspace members |
| Workspace | Active workspace members only |
| Private | Creator, admins, and explicitly granted users |
Connecting to Knowledge
Assistants become much more useful with access to your organization’s knowledge:- Projects — Link one or more projects to give the assistant access to uploaded documents. The assistant searches these documents for relevant context when answering questions.
- Knowledge Bases — Connect external knowledge bases for broader document retrieval.
Tool Configuration
Assistants can use external tools through MCP (Model Context Protocol) integrations:- Notion — Search and retrieve pages from your Notion workspace
- GitHub — Search repositories, read issues and pull requests
- Atlassian — Access Jira issues and Confluence pages
- HubSpot — Look up contacts, deals, and CRM data
Testing Your Assistant
Use the built-in test panel to try out your assistant’s behavior without leaving the settings page.Open the test panel
From any assistant settings page, click the Test button in the navigation sidebar. A panel slides open on the right side of the screen.
Send messages
Type a message and press Enter (or click the send button) to chat with your assistant in real time. Responses stream in just like a normal conversation.
Test Panel Controls
| Control | Description |
|---|---|
| Refresh | Clears the conversation so you can start fresh with the current settings |
| Close | Closes the test panel and returns to the full settings view |
| Stop | Appears while the assistant is responding — click to cancel the current response |
Example Assistants
Customer Support Bot
Connect your FAQ documents and help articles. Set the system prompt to answer questions accurately and maintain a friendly tone.
Code Reviewer
Instruct the assistant to review code for bugs, security issues, and best practices. Use a lower temperature for consistent feedback.
Content Writer
Configure a higher temperature for creative responses. Provide brand guidelines in the system prompt.
Sales Assistant
Upload product documentation and pricing guides. The assistant can answer prospect questions and draft follow-up emails.
The number of assistants you can create may depend on your workspace plan.