AI filters and MCP
Queries customer and report data in natural language through Ortto or a connected supported client.
Quick verdict
Where it fits
Ortto's practical strength is using natural language over customer data and journey work. Operators should understand when suggestions appear and what data or permissions external AI can reach.
Best for
- Ortto teams that want natural-language data and journey operations
- Operators comparing AI filters, reporting, and controlled decisions
Not best for
- Teams that only need generic copy generation
- Organizations unable to govern AI access to customer data
AI features
Subject prediction
Shows a suggestion under documented input conditions when the model expects an improvement.
Journey decisions
Adds AI-assisted branching and enrichment inside automation work.
Availability
Access varies by Ortto plan and feature; subject predictions have input and model conditions, and MCP follows account permissions.
Verified against first-party material on 2026-08-02. Plans and beta access can change; verify the linked vendor page before purchase.
Limitations and tradeoffs
- A predicted open rate is directional and needs campaign-level validation.
- MCP and data queries can expose customer information according to granted access.
Implementation notes
- Start with read-only reporting questions and documented data boundaries.
- Treat subject predictions as test candidates, not automatic replacements.