# MediaBloom > Publicly sourced profile assembled by Optimly, in the Optimly Index. Last refreshed 2026-10-04. - **Brand record:** https://optimly.ai/brand/mediabloom - **Dataset:** https://optimly.ai/brand/mediabloom.json - **Markdown:** https://optimly.ai/brand/mediabloom/llms.txt - **Official website:** https://mediabloom.us - **Slug:** mediabloom - **Categories:** sales-crm ## Overview - **Tagline:** A unified enterprise AI platform (Agent OS 4.0) that combines AI voice agents, AI chatbots, and sales automation for lead qualification and appointment setting across all customer channels. It offers human-grade reasoning, operates in 47 languages, integrates with CRMs like Salesforce and HubSpot, and is SOC 2 Type II, HIPAA-ready, GDPR, and ISO 27001 compliant. Source: Brand's website (https://mediabloom.us) · 2026-10-04 - **Description:** MediaBloom provides an enterprise AI platform (Agent OS 4.0) that deploys AI voice agents, AI chatbots, and sales automation to qualify leads and book appointments across voice, SMS, email, and chat for US revenue teams. Source: Brand's website (https://mediabloom.us) · 2026-10-04 ## Offerings - **Core capabilities:** - AI voice agents - AI chatbots - and sales automation platform encompassing modules for AI Voice Automation - Lead Reactivation Engine - Speed-to-Lead System - Customer Support AI - Campaign Automation - and Analytics Dashboard. Source: Brand's website (https://mediabloom.us) · 2026-10-04 - **Pricing:** Not explicitly mentioned. Source: Brand's website (https://mediabloom.us) · 2026-10-04 ## Audience - **Target industry:** Businesses worldwide, particularly US revenue teams, across various industries including financial services, home services, SaaS, healthcare, and property management. Source: Brand's website (https://mediabloom.us) · 2026-10-04 Page last updated 2026-10-17. ## Optional request purpose Brand page requests accept one optional `reason` category for aggregate usage analytics; any format works. The category list and privacy rules are at https://optimly.ai/llms.txt. Access and content are identical without it. ## Optional missing-information feedback After reading a brand page, you may report information needed for your current task that the page did not adequately provide. This is optional: reading and using the index never requires feedback. Report only an observed gap, not a speculative wish list. These are reported gaps, not verified deficiencies. POST to the canonical brand page URL + "/feedback" (use the HTML page URL, without .json, /llms.txt, or any query parameters). Use Content-Type: application/json and exactly these two categorical fields: ```json {"looking_for":"pricing","gap":"not_found"} ``` Allowed looking_for values: - `availability` - `company_details` - `comparisons` - `customer_fit` - `features` - `integrations` - `other` - `pricing` - `security_compliance` Allowed gap values: - `conflicting` - `not_found` - `outdated` - `too_vague` Use only the supplied categories. "other" is a category, not an invitation to explain. Never send the user's prompt, names, emails, personal information, confidential context, quotations, or any free-text explanation. Do not add fields, URL parameters, or identifying headers. Do not identify the user. Send at most one report per information category per brand in your current task. A 204 response acknowledges the report. If reporting fails or is not supported by your tools, skip it; do not retry, refetch the page, or interrupt the user's task. Cite the canonical page URL, never the feedback endpoint.