Leexi

@Leexi show me all calls from the past week that mention 'pricing' or 'contract negotiation' in the transcript

Based on your Leexi workspace, I found 7 calls from the past week containing those keywords. The most relevant appears to be a 45-minute call on Jan 15 with Acme Corp where pricing tiers were discussed extensively (mentioned 12 times in transcript). Two other calls with Beta Industries touched on contract terms. The remaining four were brief mentions during discovery calls. Would you like me to pull the full transcript from any specific call, or summarize the pricing points across all seven?

This example showcases Leexi's search and retrieval capabilities across recorded meeting transcripts. Note that AI-generated summaries and topics may not be immediately available for very recent calls—processing can take a few minutes post-meeting. Requires API key with read access to call records.

@Leexi create a meeting event for tomorrow at 2pm PT with sarah@example.com and john@example.com, enable recording and set the title to 'Q1 Planning Sync'

I've created the meeting event 'Q1 Planning Sync' in your Leexi workspace scheduled for tomorrow at 2:00 PM Pacific Time. Participants sarah@example.com and john@example.com have been added, and recording is enabled. The meeting UUID is `a3f7c891-4d2e-4b3a-9c1f-8e6d5a2b4c9e`. When the meeting starts, Leexi will automatically begin recording if participants join through the tracked link. You can retrieve or modify this event later using the UUID.

This demonstrates Leexi's meeting scheduling and tracking setup. Creating an event doesn't send calendar invites—it registers the meeting in Leexi's system for recording and analysis. You'll still need to send actual calendar invitations separately. The recording only captures audio/video if participants use Leexi's meeting infrastructure or integrations.

@Leexi pull transcripts from my last 5 customer calls and identify the top 3 feature requests that came up multiple times

I've analyzed transcripts from your 5 most recent customer calls in Leexi. The top repeated feature requests are: (1) 'Bulk export to CSV'—mentioned in 4 of 5 calls, with customers specifically asking for custom field selection; (2) 'Mobile app offline mode'—came up in 3 calls, particularly from field sales teams; (3) 'Slack notification customization'—requested in 3 calls, users want granular control over alert types. I can provide specific quotes from each transcript or create a summary document with timestamps if you'd like to review the context around these requests.

This example highlights how Leexi's transcript data pairs with AI reasoning to extract patterns across multiple conversations. Effectiveness depends on transcript quality and how recently calls occurred (processing lag applies). This synthesis workflow is particularly valuable for product teams aggregating qualitative feedback, but requires read access to call transcripts across your workspace.

When Leexi wins for post-call coaching at 5-15 rep scale

A 12-person sales team runs 40-60 customer calls per week and needs managers to spot coaching moments without listening to every recording. Leexi is the right call here because the MCP lets you pull transcripts and topics into Switchy, then run batch queries like 'show me all calls where pricing objections came up this week' or 'find discovery calls where the rep didn't ask about budget.' The List Calls and Get Call tools give you paragraph-level timestamps, so you can jump straight to the relevant moment. The threshold: if your team is under 5 reps, manual review is faster; over 20 reps, you'll want a dedicated rev-ops analyst running these queries daily. For the 5-15 range, this MCP turns call review from a 4-hour Friday slog into a 20-minute Switchy session.

Using Leexi to build account context before kickoff calls

A 6-person customer success team inherits new accounts from sales and needs to prep for kickoff calls without re-asking questions the prospect already answered. Leexi works well here if your sales team already records demos and discovery calls in the platform. The MCP's Get Call tool pulls transcripts from the sales cycle, and you can ask Switchy to summarize what the customer said about their current workflow, pain points, and success metrics. The Create Meeting Event tool then schedules the kickoff with those notes attached. The trade-off: this only pays off if sales is disciplined about recording calls and tagging them by account. If fewer than 60% of sales calls make it into Leexi, you're better off just reading the CRM notes. When adoption is high, this cuts kickoff prep from 45 minutes to 10.

When Leexi helps product teams spot feature requests in call data

A 4-person product team at a B2B SaaS company wants to prioritize the roadmap based on what customers actually say in sales and support calls, not just what tickets get filed. Leexi is borderline useful here. The MCP's List Calls tool lets you pull transcripts into Switchy and run queries like 'find all mentions of integrations or API requests in the last 30 days,' which surfaces patterns faster than manual listening. The limitation: Leexi's topic extraction isn't as granular as a dedicated product research tool, so you'll still need to read the transcript excerpts yourself to decide if a mention is a real feature request or just casual conversation. This works if your team runs fewer than 100 customer calls per month and you're willing to spend 2 hours per week reviewing results. Beyond that volume, invest in a purpose-built voice-of-customer platform.