Dispatches
Customer story

Enterprise knowledge search

Five thousand meetings and a hundred thousand emails became a searchable company brain in under a week.

5,000Meeting recordings sitting in storagePlus 100,000 emails across inboxesThe old wayNowSearch my inboxSearch your inboxAsk who was thereReplay three hoursGive upNo way to search across recordingsAsk the questionGet the timestampAgent searches the entire corpusNobody could search across recordings and inboxes01Ingest meetings5,000+ recordingswith timestamps02Ingest email100,000+ messages03InheritpermissionsFrom every sourcesystem04Index the corpusUnder a weekA searchable company brain with inherited permissionsAthena ingests the corpus and inherits permissionsSESSIONWhat did the customer say aboutpricing in 2024?Customer call, April 2024, — "we can'tgo above $ per unit this year"Meeting AprTimestamp 14:32Athena · searched 5,000+ meetingsAsk what a customer said, get the timestampNew hireWhat happened on every callCHECKED AGAINST THE SOURCEMeeting recordingsEmail inboxesCustomer callsShe sees what herpermissions allowThe corpus is only assearchable aspermissions allowPermissions inherited: if you couldn't see it beforeAccount leadCustomerAthenaCustomer asks for revised terms by FridayAccount lead commits to follow-up emailAFTER THE CALLDraft revised terms emailDone, 11:03Schedule Friday check-inDone, 11:04After every customer callAfter every call, the agent runs the follow-ups automaticallyA searchable company brainathenaintel.com
Fig. 02The story in 22 seconds, from the old way to “A searchable company brain.”
Before · what we did · after
  1. Before

    Four years of institutional knowledge in recordings and inboxes nobody could search across.

  2. What we did

    Ingested the corpus: 5,000+ meetings, 100,000+ emails, with permissions inherited from the source. Under a week.

  3. After

    Ask the agent what a customer said about pricing in 2024 and get the timestamp. A new hire asks what happened on every call before they joined; Athena has read them all. After every customer call now, the agent runs follow-up workflows (AOPs) automatically.

AthenaMeeting recordingsEmail inboxesCustomer callsPermissionsTimestampsFollow-upsAgent memoryThe corpus ingested: 5,000+ meetings, 100,000+ emails, permissions inherited
Fig. 01Four years of institutional knowledge connected under inherited permissions
How long it takes · what to plan for

The corpus is only as searchable as its permissions allow. If you could not see the email before, you cannot see it now.

Super smart, knows nothing about your business. Until you teach Athena.

Example workflow

From scattered recordings and inboxes to agent-queryable memory

SURFACES INWHAT COMES INTHE PLATFORMWHAT GOES OUTDELIVERED BACKWebMobile · voiceText (SMS)EmailSlack · TeamsChromeOffice add-inMeetingsWordPowerPointSheetsFiles · PDFsDataWorkflows (AOPs)AppsLibrarySessionsSpacesStudiosMeetingsSemantic modelsDatabaseDashboardsWordPowerPointSheetsDashboardsData · APIsWebMobile · voiceText (SMS)EmailSlack · TeamsChromeOffice add-inMeeting botMeeting bot1Lakehouse2Agents3Apps · portals41 IN5,000+ recorded meetingsand 100,000+ emails arrivewith source permissionsintact2 BUILDThe corpus is ingested inunder a week, permissionsinherited from everysource3 ANSWERAsk what a customer saidabout pricing in 2024; getthe timestamp andtranscript4 RUNAfter every customer call,the agent runs thefollow-ups automatically
Fig. 03The route on the system map: Meeting bot → Lakehouse → Agents → Apps · portals. Connectors: Meeting bots, email connectors, permissions API
What it runs on
What customers say
“He wrote the entire stuff. By itself. And I was there, and I was thinking, alright. If I had to write all this stuff, I mean, I would've spent days, days, days.”
Manufacturing analyst · A global manufacturer
“I send that to the programmer and he said, alright. I read your file. I copied the section of the code because he has the right interface, and it works. Wow. Just like magic.”
Manufacturing analyst · A global manufacturer
“Digital worker, it gets spun up, it gets given access to the toolkits that it needs. It gets given access to the data that it needs. Just exists for the period it needs to exist to perform the task. And then it gets torn back down again afterwards.”
Audit lead · A global professional services firm
“I like that direction, that concept of the agent is the agent. It becomes an entity in its own right with its own ownership and its own missioning, and you get rid of the gray area and the blurry lines.”
Audit lead · A global professional services firm
“This combination is a winning combination for us, and this is where we see maximum traction, which is how do you apply all the intelligence that you have within [our data platform] and not worry about how you render that output.”
Analytics lead · A global CPG provider
“A lot of people are telling us that, oh, I sold in this package because of this info... I secured this distribution because of the selling assistance help.”
Sales enablement lead · A global CPG provider
“I am not a programmer. I cannot read a line of program in SQL or anything... The only thing that I'm doing is just writing prompts.”
Manufacturing analyst · A global manufacturer
“I finally got a chance to play around with the computer asset and build out the chatbot you mentioned. It was really impressive.”
Marketing lead · An AmLaw 100 firm
“So we use the SDK, and we write that in Python, and it calls Athena majority by API. The results appear in the interface itself.”
Legal technology team · A global law firm
“You guys are functioning better because the harness is tested for a longer period of time against enterprise customers.”
Analytics lead · A Fortune 500 retailer

Verbatim from customer calls. Customers anonymized.

Related

Related products and stories

See this on your own work

Bring one recurring task, a sample input, and an example of work you would accept.