# BackEngine

> BackEngine gives the AI a team already uses (such as Claude) accurate, secure, and permissioned business context. It connects to the systems where customer communications already live — CRM, call recordings, email, Slack, and support tickets — reads and organizes everything in advance, and answers questions inside the AI with consistent, cited results. Setup takes about 15 minutes of authorization; teams are typically live within two days, with no change to how they work.

Key facts:
- BackEngine pre-processes and categorizes every data point (~150 categories) before questions are asked, so answers are deterministic: the same question returns the same answer for everyone, unlike a direct app-to-AI connection that samples and guesses.
- A robust permission model controls what each person can ask about and see. Data is encrypted at rest and in transit with per-customer keys, never pooled or sold. SOC 2 and HIPAA compliant; BAAs available.
- It reads only communications about the customer and prospect accounts a team designates — never internal or personal threads.
- Teams use it with one command (/backengine) inside their existing AI, or on a schedule (e.g., weekly account-risk summaries delivered to Slack).

## Pages

- [Home](https://backengine.com/): You deployed AI — why hasn't work changed? How BackEngine gives AI the context to do real work.
- [What is BackEngine?](https://backengine.com/what-is-backengine): The context layer between a team's tools and their AI — reads calls, email, Slack, tickets, and CRM once, so the AI they already use can answer real business questions with one command.
- [How BackEngine works](https://backengine.com/how-backengine-works): Connects to existing tools, joins everything per account, organizes it along many dimensions, and answers inside the AI a team already uses — same question, same answer, every time.
- [Security and privacy](https://backengine.com/security-and-privacy): Reads only designated customer communications; never used to train AI models (used solely to provide the Service); per-company encryption, role-based permissions, SOC 2, HIPAA, BAAs, trust center.
- [Connect and setup](https://backengine.com/connect-and-setup): Supported connections (Salesforce, HubSpot, Zoom, Zoom Phone, Gong, Fireflies, Google Meet, Gmail, Google Calendar, Google Drive, Microsoft Outlook, Microsoft Teams, Teams Recording, Slack, Granola, Fathom, Read AI, Clari Copilot, Aircall, Zendesk, Intercom, Jira, Gamma, Enterpret), ~15-minute authorization, live within two days, 90+ prompt library, white-glove onboarding.
- [Will my team change how they work?](https://backengine.com/will-my-team-change): No — it works inside the AI the team already uses, with no data entry; scheduled answers can arrive in Slack automatically.
- [Why not connect apps directly?](https://backengine.com/why-not-connect-directly): A direct connection gives AI a library and tells it to go read; BackEngine gives it the librarian who already has — full coverage, whole-team data, deterministic answers.
- [BackEngine in action](https://backengine.com/backengine-in-action): Live demos of Claude + /backengine workflows for Sales, Post-Sales, and Product teams — forecast dashboards, win walls, lost-deal battlecards, and more, running on your own data the day you connect.
- [Customer love](https://backengine.com/customers): Case studies with hard numbers (Tattle: 2x account coverage per CSM, 40% faster time-to-insight; Fossa: 60% faster customer response) and a wall of attributed customer testimonials.
- [Full FAQ](https://backengine.com/faq.md): A comprehensive markdown FAQ for buyers, champions, and security reviewers — covering MCP, joins, permissions, governance, build-vs-buy, delivery, and role-by-role outcomes.

## Contact

- Demo and sales: use the "Get a demo" or "Talk to us" links on any page.