Hippo Best Practices
Maximize answer quality while achieving 80% cost reduction with these proven strategies.Document Preparation
Upload High-Quality Documents
Use Text-Based PDFs
Use Text-Based PDFs
Prefer: Text-based PDFs (created from Word, Google Docs, etc.)
Avoid: Scanned/image PDFs (OCR quality varies)Impact: 30-40% better accuracy with text-based PDFs
Remove Unnecessary Content
Remove Unnecessary Content
Before uploading, remove:
- Cover pages and blank pages
- Table of contents (unless needed for answers)
- Advertisements and promotional material
- Appendices with irrelevant data
Ensure Proper Formatting
Ensure Proper Formatting
Good formatting:
- Clear headings and structure
- Proper paragraph breaks
- Readable fonts (not decorative)
- Logical document flow
- All-caps text
- Excessive formatting
- Broken layouts
- Mixed languages without context
Folder Organization
Strategic Document Grouping
Related Content Together
✅ Good: All product docs in one folderImpact: Better cross-document answers
Separate Unrelated Content
✅ Good: Separate folders for different products❌ Bad: Mix all products in one folderImpact: Reduced confusion, better precision
Folder Size Sweet Spot
Question Optimization
Write Clear, Specific Questions
- Factual Questions
- How-To Questions
- Comparison Questions
✅ Good:
- “What is the API rate limit for Pro plan users?”
- “What is the refund window for digital products?”
- “What authentication methods does the API support?”
- “Tell me about limits”
- “Refunds?”
- “Auth”
Leverage Follow-Up Questions
Performance Optimization
Use Async for Scale
Batch Related Questions
Cost Optimization
Maximize the 80% Savings
Upload Once, Query Many
Reuse Chats When Appropriate
Precision Retrieval Benefits
Hippo automatically retrieves only relevant chunks:Answer Quality
Verify with Confidence Scores
Use Source Citations
Maintenance & Monitoring
Regular Cleanup
Monitor Usage
Production Checklist
Security & Privacy
Security & Privacy
- Use environment variables for API keys
- Never commit API keys to version control
- Implement user-specific chat isolation
- Delete sensitive data when no longer needed
- Review uploaded documents for PII/sensitive data
Performance
Performance
- Use async API for production workloads
- Implement connection pooling
- Add retry logic for failed requests
- Cache frequently asked questions if appropriate
- Monitor response times
Error Handling
Error Handling
Monitoring
Monitoring
- Track answer confidence scores
- Monitor API usage and costs
- Log low-confidence answers for review
- Set up alerts for errors
- Review source citations quality
Documentation
Documentation
- Document folder organization strategy
- Keep inventory of uploaded documents
- Document common questions and answers
- Maintain change log for document updates
- Create runbooks for common operations
Common Pitfalls to Avoid
Don’t:
- Mix unrelated documents in one folder
- Use vague question phrasing
- Ignore confidence scores
- Upload scanned PDFs without OCR
- Create new chats for every question
- Forget to clean up test resources
- Share API keys or commit them to git
Do:
- Group related documents logically
- Ask specific, clear questions
- Verify low-confidence answers with sources
- Use text-based documents when possible
- Reuse chats for related conversations
- Regularly clean up unused resources
- Use environment variables for API keys

