BloomChat Case Study: connected account context for mid-market companies
Connected account context for an IT services provider and its clients
BloomChat connected account information and AI-supported workflows for an IT managed services provider and its mid-market clients. The provider's CEO led design and scope; Meru led core development.
Ticket history, email, CRM notes, proposals, and internal documentation were brought into a retrieval-backed system. Teams could assemble account context and prepare reports or proposal drafts from the work already recorded.
| Client profile | Managed IT services provider and client network, anonymized under NDA |
|---|---|
| Meru's role | Core development; the provider's CEO led design and scope |
| Engagement | Nine months |
| Workflows | Account context, reporting, proposal preparation, knowledge lookup, and operational follow-up |
| Client environments | Onboarded environments with their own systems, permissions, and workflows |
What made client decisions slower?
Before preparing an account review or proposal, employees had to reconstruct the relevant history across tickets, emails, CRM notes, and prior work. An answer in one system was not necessarily available to the next person.
The provider also needed a way to implement AI in different client environments. Their systems, permissions, and workflows were not interchangeable. A useful platform had to support those differences while making the source information inspectable.
What did BloomChat connect across client environments?
BloomChat connected ticket history, email records, CRM notes, proposal data, internal documentation, and client-specific workflows. Retrieval supplied context to account lookup, reporting, and drafting tasks.
- Account preparation
- Brought service history, prior proposals, and account records together before support, renewal, and commercial conversations.
- Reporting and proposals
- Prepared working reports and proposal drafts from linked account context, with employees reviewing the content, commercial assumptions, and next action.
- Client-specific workflows
- Adapted reporting, lookup, intake, and follow-up to each client's systems, permissions, and operating responsibilities.
The same service history could support an account review, inform a proposal, and carry context into follow-up. Employees worked from the information already recorded instead of assembling a fresh account history for each task.
How was the account intelligence layer built?
The account intelligence layer connected historical service and commercial records to retrieval and workflow actions. Source ingestion, search, and response preparation formed the information path behind account lookup, reporting, and drafting.
| Measure | Scale | What it means |
|---|---|---|
| Automation scope | 1,000+ automations | Automation routines across onboarded client workflows, not distinct full-scale implementations or client companies. |
| Internal use | 150+ internal users; roughly 10,000 daily queries | Users and query activity within the provider's internal operations. |
| Connected records | 100,000+ historical records | Tickets, CRM records, proposals, emails, and wiki entries connected for retrieval. |
About this engagement
This case study draws on Meru's core development work for the provider. The figures describe platform scale and activity, not measured productivity, answer accuracy, or financial return. Client identities and sensitive account records remain confidential.
Give the next person the context already available.
If preparing a report, proposal, or client conversation means rebuilding the same account history, start by tracing where that information lives and who needs it next.