> ## Documentation Index
> Fetch the complete documentation index at: https://docs.booleinference.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Contact Boole AI Support, Billing, and Security Teams
> All support channels for Boole AI — technical help, billing questions, security vulnerability reports, and general inquiries with expected response times.
Boole AI's support team is available to help with technical issues, billing questions, and security concerns. Choose the right contact below based on your need — routing your message correctly gets you to the right person faster and reduces response time.
## Contact Channels
**[support@boole.ai](mailto:support@boole.ai)**
For API issues, local binary problems, integration questions, performance troubleshooting, and anything else technical. Include your account email and a description of the issue in your first message.
**[billing@boole.ai](mailto:billing@boole.ai)**
For invoice requests, payment issues, credit questions, and account upgrades or cancellations.
**[hello@boole.ai](mailto:hello@boole.ai)**
For partnerships, press inquiries, feature requests, and everything else that doesn't fit the categories above.
**[security@boole.ai](mailto:security@boole.ai)**
For responsible disclosure of security vulnerabilities. We acknowledge all security reports within 24 hours. Please do not disclose publicly until we've addressed the issue.
***
## System Status
Check **[status.booleinference.com](https://status.booleinference.com)** for real-time service status, scheduled maintenance windows, and a full history of past incidents and resolutions.
You can subscribe to status updates to receive notifications by email or webhook whenever an incident is opened, updated, or resolved. This is the fastest way to learn about degraded performance or outages affecting the cloud API.
***
## Security Disclosure
If you discover a security vulnerability in Boole AI — in the cloud API, local binary, or any supporting infrastructure — report it responsibly to [security@boole.ai](mailto:security@boole.ai).
When reporting, please include:
* A clear description of the vulnerability and its potential impact
* Steps to reproduce the issue
* Any proof-of-concept code or screenshots, if applicable
Please do not disclose vulnerabilities publicly — in GitHub issues, social media, or elsewhere — until Boole AI has had a reasonable opportunity to investigate and issue a fix. We will coordinate a disclosure timeline with you directly.
Boole AI is SOC 2 Type II certified and takes security reports seriously. We aim to acknowledge all reports within **24 hours** and to provide a remediation timeline within **5 business days**.
***
## Response Times
| Channel | Typical Response Time |
| ----------------- | ---------------------------- |
| Technical support | Within 1 business day |
| Billing | Within 1 business day |
| Security | Acknowledged within 24 hours |
| General inquiries | Within 2 business days |
For urgent issues, include your account email and a clear description of the problem in your first message to reduce back-and-forth. For outages, check [status.booleinference.com](https://status.booleinference.com) first — active incidents are posted there in real time.
***
## Documentation Resources
Explore code examples, optimization logs, and more on GitHub:
Runnable code samples for common integrations, streaming, tool calling, and local deployment.
The nightly compiler's optimization history — 2,057 iterations, 217 retained passes, and the reasoning behind each one.
All public Boole AI repositories, including SDKs, tooling, and community contributions.