How configuration works
When you describe the assistant you want, Gainable’s Copilot Planner analyzes your request and the Copilot Builder creates it. The Copilot stays synced with your app. As you add data models or features, you can update the Copilot to work with them.1
Describe your Copilot
Tell Gainable what kind of assistant you want, what it should know, and how it should behave.
2
Planner analyzes
The planner determines the Copilot’s name, instructions, data access, and configuration.
3
Builder creates
The builder sets up the Copilot with all its properties and connects it to your app.
4
Stays synced
As your app changes, you can update the Copilot through follow-up prompts.
Properties
Writing good prompts
Be specific about what the Copilot should do, who it helps, and what data it needs.Writing effective instructions
The Copilot’s instructions act as its system prompt. They define how it behaves in every conversation. Good instructions include:- Role definition. Who the Copilot is and what it specializes in.
- Tone and personality. How it should communicate.
- Rules and boundaries. What it should and shouldn’t do.
- Data awareness. What data it has access to.
Example instructions
Conversation starters
Conversation starters are pre-defined prompts displayed as clickable buttons when the Copilot opens. They help users discover what the Copilot can do.Best practices
- Keep them short. 3 to 8 words per starter.
- Make them varied. Cover different capabilities.
- Be domain-specific. Match your Copilot’s purpose.
- Use action language. Start with verbs.
Web search
Enabling web search lets the Copilot look up external information during conversations. When to enable:- The Copilot needs current information (news, market data, company details)
- Users might ask questions beyond your app data and documents
- The Copilot only works with internal data
- You want to keep responses focused on your content
- Sensitive contexts where external information could be misleading
Updating a Copilot
You can update Copilots through follow-up prompts at any time:Tips
Be specific about the domain
Be specific about the domain
A Copilot that “helps with everything” is less useful than one focused on a specific area like sales, support, or HR.
Define tone and personality
Define tone and personality
Copilots feel more natural when they have a consistent personality. Specify whether it should be formal, casual, encouraging, or direct.
Mention data access explicitly
Mention data access explicitly
Tell the Copilot what data models it should use. “Give it access to deals and contacts” is much clearer than “let it see the data.”
Test with real questions
Test with real questions
After creating a Copilot, try asking it the kinds of questions your users would ask. Refine instructions based on the results.
Learn more
Data access
Connect your Copilot to app data via MCP
Knowledge bases
Upload documents for your Copilot
Embedding
Place the Copilot chat in your app
Overview
Back to Gaia Copilot overview
Gaia Autopilot
Looking for the autonomous side? Agents run on their own