What is Custom Context?
Custom Context lets you provide specific instructions that guide how the AI generates responses for a project. These instructions affect tone, format, confidentiality requirements, and other behavioral aspects of response generation.Why Use Custom Context?
- Consistency - Ensure all responses in a project follow the same style
- Compliance - Add required disclaimers or confidentiality statements
- Client fit - Match the tone expected by specific clients or industries
- Formatting - Control response length, structure, and detail level
What to Include
Tone and Style
| Directive | Effect |
|---|---|
| ”Use formal, professional language” | More corporate tone |
| ”Be concise and direct” | Shorter responses |
| ”Use technical terminology” | Industry-specific language |
| ”Write in first person plural (we)“ | Company voice |
Response Format
| Directive | Effect |
|---|---|
| ”Limit responses to 3 paragraphs” | Shorter answers |
| ”Use bullet points where appropriate” | Scannable format |
| ”Include specific metrics when available” | Data-driven responses |
| ”Avoid jargon and acronyms” | Accessible language |
Compliance Requirements
| Directive | Effect |
|---|---|
| ”Add confidentiality notice to each response” | Legal compliance |
| ”Do not mention competitor names” | Brand safety |
| ”Include certification references where relevant” | Credibility |
| ”Avoid making guarantees or promises” | Risk management |
Before & After Examples
See how Custom Context changes actual response output.Example 1: Adding Certification References
Question: “Describe your data encryption practices.”- Without Context
- With Context
We use AES-256 encryption for data at rest and TLS 1.3 for data in transit. All encryption keys are managed through a secure key management system.(42 words)
Example 2: Controlling Response Length
Question: “What is your company’s approach to customer support?”- Without Context
- With Context
Our customer support team provides assistance through multiple channels including email, phone, and live chat. We maintain a knowledge base for self-service support and offer dedicated account managers for enterprise clients. Our average response time is under 4 hours during business hours, with 24/7 support available for critical issues. We regularly collect feedback to improve our support processes and maintain a 95% customer satisfaction rating.(71 words)
Example 3: Formal vs Conversational Tone
Question: “How easy is your product to implement?”- Without Context
- With Context
Implementation is straightforward and typically takes 2-4 weeks. Our team guides you through setup, data migration, and training. Most clients are fully operational within a month.(28 words)
Example Configurations
Enterprise Client RFP
Tone: Formal and professional
- Use “we” when referring to our company
- Reference our SOC 2 Type II audit when discussing security
- Include specific metrics and case study data where available
- Keep responses between 100-300 words unless the question requires more detail
Technical Security Questionnaire
- Use precise technical terminology
- Reference specific compliance frameworks (SOC 2, ISO 27001, GDPR)
- Include architecture details when relevant
- Be specific about encryption standards and security controls
Startup/SMB Proposal
- Use conversational but professional tone
- Focus on ease of use and quick time-to-value
- Avoid excessive technical jargon
- Keep responses concise and focused on benefits
How to Configure
Effect on Response Generation
Once configured, your custom context:- Applies to all new responses generated in this project
- Works alongside your Custom Sources selection
- Affects both individual and bulk response generation
- Does not retroactively change existing responses
To update existing responses with new context settings, regenerate them after saving your changes.
Best Practices
Be specific, not vague
Be specific, not vague
Instead of “be professional”, specify what professional means: “Use formal language, avoid contractions, and reference specific credentials.”
Include examples when helpful
Include examples when helpful
If you want a specific phrase included, provide it: “End security-related responses with: ‘For more details, see our Trust Center.’”
Test before bulk generation
Test before bulk generation
Generate a few sample responses to verify your context produces the desired output before running bulk generation.
Keep it focused
Keep it focused
A few clear directives work better than a long list. Prioritize the most important requirements.
Combining with Custom Sources
Custom Context and Custom Sources work together:| Setting | What It Controls |
|---|---|
| Custom Sources | Which Library content the AI can reference |
| Custom Context | How the AI writes and formats responses |
Troubleshooting
Context not being followed
Context not being followed
Try making your instructions more explicit. Instead of “be brief”, say “limit responses to 100 words maximum.”
Responses too generic
Responses too generic
Add more specific guidance about tone, terminology, or format. Include example phrases if needed.
Conflicting instructions
Conflicting instructions
Review your context for contradictions. For example, “be detailed” and “keep responses under 50 words” conflict.