Integration Patterns
How Torra fits into CRM, support, and internal product surfaces.
CRM and revenue tools
- Generate account updates, follow-up drafts, and meeting summaries
- Keep the surrounding workflow in the CRM while Torra handles grounded execution
- Return structured outputs so the host system can slot content into existing records
Support systems
- Summarize escalations and propose policy-aware replies
- Use SSE when queue or ticket views need progressive output
- Keep approvals and final send actions inside the support system
Internal tools
- Embed Torra as the governed AI layer inside existing company apps
- Pass workspace, pack, or source context from the host product
- Preserve citations so internal teams can verify outputs before action
Design rule
- Do not force every team into a new frontend.
- Let each system keep its local UI and workflow.
- Use one Torra runtime contract behind the scenes.
What to document next
- Host-specific auth patterns
- Recommended request payload shapes by surface
- Sync versus streaming guidance
- Examples for embedded assistant, bulk workflow, and operator review flows