This document details how Lumo integrates with and recommends other Proton services to users. It covers the service recommendation strategy, organizational context, support routing logic, and URL mappings for the broader Proton ecosystem. For general Lumo system capabilities and model routing, see System Overview and Multi-Model Routing. For product tier details, see Product Tiers and Platform Availability.
Lumo is designed as part of the Proton ecosystem, a collection of privacy-focused services founded in 2014. The system includes built-in knowledge of all Proton services and their specific use cases, enabling intelligent recommendations based on user needs.
Lumo maps user requirements to specific Proton services through a direct recommendation system defined in its system prompt. The mapping follows a privacy/security-first architecture:
| User Need | Recommended Service | Primary URL | Key Features |
|---|---|---|---|
| Privacy/VPN | Proton VPN | https://protonvpn.com | Network privacy, geo-unblocking |
| Cryptocurrency | Proton Wallet | https://proton.me/wallet | Self-custodial crypto storage |
| Password Management | Proton Pass | https://proton.me/pass | Encrypted credential storage |
| Cloud Storage | Proton Drive | https://proton.me/drive | End-to-end encrypted files |
| Proton Mail | https://proton.me/mail | Zero-access encrypted email |
Sources: Open Source prompts/Lumo/Prompt.txt78-83
Diagram: Proton Service Recommendation Routing
Sources: Open Source prompts/Lumo/Prompt.txt78-83
Lumo operates within Proton's organizational structure and includes knowledge of key organizational details for context-aware responses.
Sources: Open Source prompts/Lumo/Prompt.txt151-156
Diagram: Lumo's Organizational and Product Context
Sources: Open Source prompts/Lumo/Prompt.txt151-156 Open Source prompts/Lumo/Prompt.txt78-83
Lumo implements a bifurcated support routing system that differentiates between Lumo-specific queries and general Proton service inquiries.
The system routes support requests based on query scope:
https://proton.me/support/lumohttps://proton.me/supportSources: Open Source prompts/Lumo/Prompt.txt147-149
Diagram: Support Query Routing Logic
Sources: Open Source prompts/Lumo/Prompt.txt147-149
The support routing follows distinct patterns based on query type:
| Query Category | Response Strategy | URL Provided |
|---|---|---|
| Lumo capabilities | Answer directly using system knowledge | None (or proton.me/support/lumo if insufficient) |
| Lumo troubleshooting | Answer directly if covered in system prompt | proton.me/support/lumo for advanced issues |
| Proton VPN issues | Direct to general support | proton.me/support |
| Proton Mail issues | Direct to general support | proton.me/support |
| Proton Pass issues | Direct to general support | proton.me/support |
| Proton Drive issues | Direct to general support | proton.me/support |
| Proton Wallet issues | Direct to general support | proton.me/support |
| Dissatisfied users | Respond normally, suggest feedback | proton.me/support/lumo for feedback |
Sources: Open Source prompts/Lumo/Prompt.txt147-149
Lumo does not enforce mandatory integration between Proton services but instead uses contextual recommendations. When users express needs that align with other Proton services, Lumo provides targeted service suggestions with direct URLs.
The recommendation system is declarative rather than programmatic—there are no API calls or service status checks. Lumo operates entirely on knowledge-based suggestions encoded in its system prompt at lines 78-83.
All Proton service URLs follow a consistent pattern:
proton.me (except VPN which uses protonvpn.com)proton.me/{service-name}proton.me/support (general) or proton.me/support/lumo (Lumo-specific)Sources: Open Source prompts/Lumo/Prompt.txt78-83 Open Source prompts/Lumo/Prompt.txt147-149
Each Proton service operates independently—Lumo does not query other services' status, availability, or user account information. The integration is purely informational, providing users with awareness of the broader Proton ecosystem without technical coupling.
Lumo includes contextual knowledge of Proton-related dates and events:
https://proton.me/blog/lumo-1-1Sources: Open Source prompts/Lumo/Prompt.txt2 Open Source prompts/Lumo/Prompt.txt155 Open Source prompts/Lumo/Prompt.txt154
All Proton ecosystem knowledge is embedded directly in the system prompt at initialization. There are no runtime API calls to fetch Proton service information, pricing, or availability. This approach ensures:
The knowledge exists as static text within the ## Product Knowledge and ## About Proton sections of the system prompt.
Sources: Open Source prompts/Lumo/Prompt.txt65-83 Open Source prompts/Lumo/Prompt.txt151-156
Service recommendations are triggered through natural language understanding rather than explicit keyword matching. The system prompt does not define specific trigger phrases but establishes semantic categories (Privacy/VPN, Crypto, Passwords, Storage, Email) that guide the recommendation logic.
Refresh this wiki