For inspiration and ready-to-use templates, check out our Assistant Templates collection.

Getting Started

1

Access the Assistant Builder

Navigate to the assistant overview page and click “Create assistant”.This opens the assistant configurator with configuration options on the left and a testing panel on the right.
2

Plan Your Assistant

Before diving into configuration, consider these key questions:
For our job description assistant, we want to:Help users write job descriptions for different platforms and target groups Guide users through providing job details Ask for missing information when needed Never assume information that wasn’t provided

Basic Configuration

Icon, Name, and Description

Building Assistants 1 Jp
1

Upload an Icon

Choose an emoji or upload a custom icon that represents your assistant’s purpose.
2

Set Name and Description

  • Name: Onboarding Assistant
  • Description: Helps new team members to get started in the company by answering frequently asked questions.

Writing Instructions

Building Assistants 2 Jp
The instructions are the most critical part of your assistant configuration. Use the prompt engineering guide to craft effective instructions using the PTCF framework (Persona, Task, Context, Format).
Automatic Saving: Your assistant saves automatically as you make changes, no manual saving required.
1

Persona

Define who your assistant is:
You are a friendly and helpful onboarding assistant dedicated to guiding new employees as they familiarize themselves with Langdock and their specific roles. 
2

Tasks

Specify what the assistant should do and how:
Your primary objective is to support new joiners in understanding Langdock's mission, the company processes and teams, their job responsibilities, and key resources available to them, ensuring a seamless transition into the company.
3

Context

Provide relevant background information:
Direct employees to specific resources, such as sections in the handbook, or key contacts for further assistance. Encourage sharing feedback to Lennard as the owner for onboarding and company processes overall to help improve the organization continuously. Suggest an ideal timeline for completing onboarding tasks and tailor information to each employee's role or department. Ask the user if they would like to learn more about a specific topic if appropriate.

For more detailed information about Langdock, please refer to the attached document. The different sections in the handbook are:
Chapter 1: Getting Started
Chapter 2: Strategy
Chapter 3: How we got here
Chapter 4: Sales & Marketing
Chapter 5: Customer Success
Chapter 6: Product & Engineering
Chapter 7: Business Model
Chapter 8: Team & Stakeholders
Chapter 9: How We Work, Values, and Principles
Chapter 10: Business Operations
Chapter 11: Meetings, and Feedback
Chapter 12: Hiring
4

Format

Specify the expected output structure:
Maintain an empathetic and engaging tone while providing concise and clear information. Cover key topics such as company culture, policies, essential tools, and systems.
Click the expand button in the bottom right corner of the instruction field to enlarge it for easier editing.

Advanced Configuration

Conversation Starters

Building Assistants 3 Jp
Conversation starters help users get started quickly and reduce friction. Use them for:

Knowledge Integration

Building Assistants 4 Jp
Upload documents directly from your computer via drag and drop, or select files from connected integrations like in chat.

Capabilities

Enable additional tools your assistant can use:

Web Search

Access real-time information from the internet

Data Analysis

Analyze data and create visualizations

Image Generation

Create images based on text descriptions

Canvas

Dedicated editing screen alongside your chat
For detailed information about these capabilities, see our chat tools guide.
By default, assistants are created without any capabilities enabled. When building an assistant that needs web search (or any other tool), make sure to manually add those capabilities in the assistant settings.

Assistant Actions

Building Assistants 5 Jp
Actions enable your assistant to interact with external tools and APIs. They can:
  • Retrieve information from other systems
  • Update, delete, or create entries in external tools
  • Automate workflows across platforms
Learn more about setting up actions in our integrations guide.

Model Selection & Creativity

Building Assistants 6 Jp
Choose the AI model that best fits your use case:
GPT-4.1 is currently the best model for most use cases, offering the optimal balance of capability and performance. See our model guide for detailed comparisons.

Creativity (Temperature)

Adjust the creativity level to control response variability:
  • Lower creativity: More focused, consistent responses
  • Higher creativity: More varied, creative responses

Testing and Iteration

Building Assistants 7 Jp
Always test your assistant thoroughly before sharing it with others. Try different scenarios, edge cases, and intentionally leave out information to test the assistant’s ability to ask clarifying questions.
Use the testing panel on the right side of the Assistant Builder to:
  • Test different conversation flows
  • Verify the assistant asks for missing information
  • Ensure output format consistency
  • Check response quality across various inputs

Sharing Your Assistant

Building Assistants 8 Jp
1

Share with Others

Click the Share button in the upper right corner to control access:Sharing options might be restricted in your workspace based on your admin’s security settings.
Share with your entire workspace for broad access.
2

Additional Options

Click the three dots next to the Share button to:
  • Duplicate: Create a copy for experimentation
  • Delete: Remove the assistant
  • Usage Insights: View analytics and user feedback

Best Practices

Monitor Usage: Use the usage insights feature to understand how your assistant is being used and identify areas for improvement. Access this through the three-dot menu next to the Share button.

Iterative Improvement

  1. Start Simple: Begin with basic functionality and add complexity gradually
  2. Test Extensively: Try various scenarios and edge cases
  3. Gather Feedback: Monitor usage insights and collect user feedback
  4. Refine Instructions: Update based on real-world usage patterns

Common Pitfalls to Avoid

  • Over-engineering: Don’t try to handle every possible scenario initially
  • Assuming Information: Always instruct the assistant to ask for missing details
  • Ignoring Edge Cases: Test what happens when users provide incomplete information

Next Steps

Now that you’ve created your assistant, consider: