@adminide-stack/yantra-help-browser 12.0.16-alpha.6 → 12.0.16

package/lib/templates/content/threads/conversation-management.md

@@ -0,0 +1,103 @@
+# Conversation Management
+
+Tips and tools for keeping your Yantra conversations organized, productive, and easy to find.
+
+---
+
+## Organizing Conversations
+
+### Naming threads
+
+By default, threads are named after your first query. Rename them for better organization:
+
+1. Click the thread title in the sidebar or at the top of the conversation.
+2. Type a descriptive name (e.g., "React performance optimization research").
+3. Press Enter.
+
+### Pinning important threads
+
+Pin threads you reference frequently:
+
+- Click **⋯** > **Pin** on any thread.
+- Pinned threads stay at the top of the sidebar, regardless of age.
+- Unpin anytime via **⋯** > **Unpin**.
+
+### Tagging
+
+Add tags to threads for categorization:
+
+- Click the tag icon in the thread header.
+- Add tags like "work," "personal," "research," "client: Acme Corp."
+- Filter the thread list by tag.
+
+---
+
+## Thread Actions
+
+| Action         | Shortcut (Mac) | Shortcut (Windows) | Description                               |
+| -------------- | -------------- | ------------------ | ----------------------------------------- |
+| New thread     | ⌘ + N          | Ctrl + N           | Start a fresh conversation                |
+| Search threads | ⌘ + F          | Ctrl + F           | Find threads by keyword                   |
+| Pin/unpin      | —              | —                  | Keep threads accessible                   |
+| Archive        | —              | —                  | Move to archive (not deleted)             |
+| Delete         | —              | —                  | Permanently remove (30-day recovery)      |
+| Export         | —              | —                  | Download as Markdown, PDF, or text        |
+| Branch         | —              | —                  | Fork the conversation at a specific point |
+
+---
+
+## Branching Conversations
+
+When a conversation takes you in an unexpected direction, branch it instead of cluttering the original thread:
+
+1. Hover over any message in the thread.
+2. Click the **Branch** icon.
+3. A new thread is created with the conversation history up to that point.
+4. Continue the original thread and the branch independently.
+
+This is especially useful for:
+
+- Exploring "what if" scenarios
+- Separating sub-topics into their own threads
+- Trying different approaches without losing the original context
+
+---
+
+## Search and Filter
+
+### Full-text search
+
+Search across all your conversations:
+
+- Search by **keywords** in your messages or Yantra's responses.
+- Search by **date range** to find conversations from a specific period.
+- Search by **search mode** (Regular, Pro, Deep Research).
+
+### Filters
+
+| Filter | Options                                    |
+| ------ | ------------------------------------------ |
+| Date   | Today, this week, this month, custom range |
+| Mode   | Regular, Pro Search, Deep Research         |
+| Tags   | Your custom tags                           |
+| Shared | Only shared threads, only private          |
+
+---
+
+## Auto-Cleanup
+
+Configure automatic thread management:
+
+- **Auto-archive** — Threads with no activity for X days are archived (default: 90 days).
+- **Auto-delete** — Archived threads are deleted after X days (default: never).
+- **Configurable** — Adjust at **Settings > Preferences > Threads**.
+
+---
+
+## Best Practices
+
+1. **One topic per thread** — Keeps context clean and makes threads easier to find later.
+2. **Name your threads** — A good name saves time when searching later.
+3. **Use branches** — Don't let a tangent derail a focused research thread.
+4. **Pin active projects** — Keep your current focus areas at the top.
+5. **Archive regularly** — A clean sidebar helps you focus on what matters now.

package/lib/templates/content/threads/threads-overview.md

@@ -0,0 +1,92 @@
+# Threads Overview
+
+Threads are persistent conversation sessions with Yantra's AI. Every search can become a thread, and every thread is saved automatically for future reference.
+
+---
+
+## What Is a Thread?
+
+A thread is a multi-turn conversation with Yantra that maintains context across messages. When you ask a follow-up question, Yantra remembers everything discussed earlier in the thread — entities, preferences, and the flow of the conversation.
+
+---
+
+## Creating Threads
+
+Threads are created automatically:
+
+| Action                                 | Result                                  |
+| -------------------------------------- | --------------------------------------- |
+| Start a new search                     | A new thread is created                 |
+| Click **New Thread** in the sidebar    | An empty thread is created              |
+| Press ⌘ + N (Mac) / Ctrl + N (Windows) | New thread with focus on the search bar |
+
+---
+
+## Thread Lifecycle
+
+### Active threads
+
+Threads you're currently working in. They appear at the top of the sidebar under **Recent**.
+
+### Archived threads
+
+Older threads move to the archive automatically based on your retention settings. You can also manually archive a thread via **⋯** > **Archive**.
+
+### Deleted threads
+
+Delete a thread via **⋯** > **Delete**. Deleted threads are permanently removed after 30 days. During that window, you can recover them from **Settings > Privacy > Recently Deleted**.
+
+---
+
+## Thread Features
+
+| Feature           | Description                                                                      |
+| ----------------- | -------------------------------------------------------------------------------- |
+| **Rename**        | Click the thread title to give it a meaningful name                              |
+| **Pin**           | Pin important threads to the top of the sidebar                                  |
+| **Share**         | Share a thread link with team members (read-only)                                |
+| **Branch**        | Create a copy of the thread at a specific point to explore a different direction |
+| **Export**        | Download as Markdown, PDF, or plain text                                         |
+| **Save to Space** | Add the thread to a Space for organized research                                 |
+
+---
+
+## Thread Context
+
+### What Yantra remembers within a thread
+
+- All previous messages (yours and Yantra's)
+- Entities and topics discussed
+- Preferences you've expressed ("only show academic sources")
+- Referenced sources and results
+
+### Context limits
+
+| Mode           | Context window                     |
+| -------------- | ---------------------------------- |
+| Regular Search | ~50,000 tokens (last 10 exchanges) |
+| Pro Search     | ~100,000 tokens                    |
+| Deep Research  | Full session history               |
+
+When a thread exceeds the context limit, the oldest messages are summarized to make room for new context.
+
+---
+
+## Managing Threads
+
+### Sidebar
+
+The sidebar shows:
+
+- **Pinned** threads at the top
+- **Recent** threads sorted by last activity
+- **Search** bar to find threads by keywords
+
+### Bulk actions
+
+Select multiple threads to:
+
+- Archive in bulk
+- Delete in bulk
+- Export all selected threads
+- Move to a Space

package/lib/templates/content/troubleshooting/common-issues.md

@@ -0,0 +1,115 @@
+# Common Issues & Solutions
+
+Running into a problem? You're in the right place. Below are the most frequently reported issues and step-by-step solutions to get you back on track.
+
+---
+
+## Search Problems
+
+### Search returns no results
+
+If your searches aren't returning any results, try these steps in order:
+
+1. **Check your internet connection** — Open another website to confirm you're online.
+2. **Clear your browser cache** — Stale cached data can interfere with search requests. Go to your browser settings, then Privacy, then Clear browsing data.
+3. **Simplify your query** — Remove special characters, shorten the query, or try different keywords.
+4. **Switch browsers** — Test in Chrome, Firefox, or Safari to rule out a browser-specific bug.
+5. **Verify your account** — Make sure your subscription is active under **Settings > Billing**.
+
+> **Still stuck?** Contact our support team with the exact search query you used and any error messages you saw.
+
+### Search results are slow
+
+Slow results are usually caused by network conditions or complex queries:
+
+- **Check Yantra's status page** — Visit our status page to confirm all systems are operational.
+- **Reduce query complexity** — Broad or multi-clause queries take longer to process. Break them into simpler searches.
+- **Disable browser extensions** — Ad blockers and privacy extensions can throttle API requests.
+- **Test your connection speed** — Run a quick speed test; Yantra works best with at least 5 Mbps download.
+
+---
+
+## Account & Login Issues
+
+### Can't log in
+
+| Symptom                   | Solution                                                                                          |
+| ------------------------- | ------------------------------------------------------------------------------------------------- |
+| Invalid credentials error | Double-check your email and password. Passwords are case-sensitive.                               |
+| Forgot your password      | Click **Forgot Password** on the login page. Check your inbox and spam folder for the reset link. |
+| Account locked            | After 5 failed attempts, accounts are temporarily locked for 15 minutes. Wait and try again.      |
+| SSO not working           | Confirm with your IT admin that your SSO provider is configured correctly.                        |
+
+### Subscription or billing problems
+
+- **Payment declined** — Update your card under **Settings > Billing > Payment Methods**. Ensure the card has not expired and has sufficient funds.
+- **Wrong plan showing** — Plan changes take up to 60 seconds to propagate. Refresh the page or log out and back in.
+- **Missing invoice** — Invoices are emailed to the account owner. Check **Settings > Billing > Invoice History** to download PDFs directly.
+- **Unexpected charges** — Review your billing cycle dates. Upgrades mid-cycle are pro-rated automatically.
+
+---
+
+## Performance Issues
+
+### Pages load slowly
+
+Try these optimizations:
+
+1. **Clear browser cache and cookies** — This resolves most loading issues.
+2. **Disable unnecessary browser extensions** — Extensions inject extra scripts that slow down page rendering.
+3. **Check your system resources** — Open Task Manager (Windows) or Activity Monitor (Mac) to check if CPU or memory is maxed out.
+4. **Update your browser** — Yantra is optimized for the latest versions of Chrome, Firefox, Safari, and Edge.
+5. **Try a wired connection** — Wi-Fi can introduce latency; a wired Ethernet connection is more stable.
+
+### Application crashes or freezes
+
+If Yantra becomes unresponsive:
+
+1. **Hard refresh the page** — Press Ctrl+Shift+R (Windows) or Cmd+Shift+R (Mac).
+2. **Try incognito/private mode** — This disables extensions and uses a clean session.
+3. **Check for browser updates** — Outdated browsers may have compatibility issues.
+4. **Note the error** — If you see an error code or stack trace, screenshot it before refreshing. It helps our engineers diagnose faster.
+
+> **Pro tip:** Open the browser developer console (F12, then Console tab) and copy any red error messages when filing a bug report.
+
+---
+
+## Mobile App Issues
+
+### App won't open or crashes on launch
+
+1. **Update to the latest version** — Open the App Store (iOS) or Google Play Store (Android) and check for updates.
+2. **Force close and reopen** — Swipe the app away from your recent apps, then relaunch.
+3. **Check device storage** — The app needs at least 100 MB of free space to operate.
+4. **Reinstall the app** — Uninstall, restart your device, then reinstall from the store.
+
+### Data isn't syncing across devices
+
+- **Confirm you're signed in** with the same account on all devices.
+- **Check your connection** — Sync requires an active internet connection.
+- **Pull to refresh** — On mobile, swipe down on the main screen to force a sync.
+- **Check sync settings** — Go to **App Settings > Sync** and make sure background sync is enabled.
+
+---
+
+## Integration Issues
+
+### Third-party integration not connecting
+
+If a connected service (Slack, GitHub, Jira, etc.) stops working:
+
+1. **Re-authenticate** — Go to **Settings > Integrations**, disconnect the service, and reconnect it.
+2. **Check the service's status** — The third-party service may be experiencing downtime.
+3. **Verify permissions** — Ensure Yantra has the required OAuth scopes. Some organizations restrict third-party app access.
+4. **Check webhook URLs** — If you configured webhooks manually, verify the endpoint URL is correct and accessible.
+
+---
+
+## General Tips
+
+- **Keep your browser updated** for the best experience.
+- **Bookmark our status page** to check for outages before troubleshooting.
+- **Enable notifications** in your account settings to receive proactive alerts about issues affecting your account.
+- **Check the Help Center** — many common questions are answered in our guides.
+
+> **Need more help?** Reach out to support via the chat widget (bottom-right corner) or email **support@yantra.ai**. We typically respond within 2 minutes.

package/lib/templates/content/use-cases/engineering-use-cases.md

@@ -0,0 +1,123 @@
+# Engineering Use Cases
+
+Detailed examples of how engineering teams leverage Yantra AI employees to accelerate debugging, preserve knowledge, and keep teams aligned.
+
+## Use Case 1: Customer Bug Report Triage
+
+### The Situation
+
+A customer posts in your #support Slack channel: _"We can't log in to the dashboard. It's been broken since this morning."_
+
+### Without Yantra
+
+1. An engineer sees the message (eventually)
+2. Opens Sentry, searches for auth-related errors
+3. Switches to Linear, looks for existing tickets
+4. Checks GitHub for recent auth-service deployments
+5. Asks around on Slack if anyone has seen this before
+6. Pieces together a theory after 45 minutes of investigation
+7. Posts a response to the customer
+
+**Time spent: 45 minutes to 2 hours**
+
+### With Yantra
+
+1. AI employee detects the report immediately
+2. Within 30 seconds, cross-references:
+    - Sentry: `AuthTokenExpired` exception spiked 47× after deploy #892 (deployed 35 min ago)
+    - Linear: Ticket #1234 exists — Marcus deployed a related fix yesterday
+    - GitHub: Deploy #892 touched `auth-service/token-handler.ts`
+    - History: Similar issue occurred on Jan 14, resolved by adjusting token cache TTL
+3. Posts a structured summary in the thread
+4. Drafts a customer response with accurate status information
+5. Suggests creating a P0 ticket and notifying Marcus
+
+**Time spent: 30 seconds for the AI employee; 2 minutes for human review and approval**
+
+## Use Case 2: 3 AM Error Spike
+
+### The Situation
+
+A code deployment rolls out at 11 PM after an engineer pushes a hotfix. By 3 AM, Sentry shows 47 new error alerts.
+
+### Without Yantra
+
+- On-call engineer wakes up to a noisy PagerDuty alert storm
+- Spends 45 minutes triaging: most alerts are variations of the same issue
+- Discovers 2 genuinely new errors buried in the noise
+- One is critical (affecting payment processing), one is minor (cosmetic UI regression)
+
+### With Yantra
+
+- AI employee correlates all 47 alerts automatically overnight
+- Groups them into 3 clusters: 44 related to the same root cause, 2 new, 1 pre-existing
+- Identifies the critical payment processing error
+- Correlates it with the 11 PM hotfix deployment
+- Sends a single, clear escalation to the on-call engineer:
+
+> _"Critical: PaymentProcessor null pointer affecting checkout since deploy #905 at 11:02 PM. 12 affected transactions. Linear ticket created (#1567). Related code change: PR #234 by Alex. Suggest rollback or hotfix."_
+
+**Result: On-call engineer deals with one actionable alert instead of 47 noisy ones**
+
+## Use Case 3: New Engineer Onboarding
+
+### The Situation
+
+A new backend engineer, Priya, joins the team and is assigned to the billing service.
+
+### Without Yantra
+
+- Priya asks her manager about the billing service architecture (30-minute conversation)
+- She reads through scattered Notion docs (some outdated)
+- She asks colleagues about specific customer configurations throughout her first two weeks
+- Each question interrupts a senior engineer for 10-15 minutes
+
+### With Yantra
+
+Day 1, Priya asks the AI employee:
+
+- _"What's the architecture of the billing service?"_ → Full technical overview with links to design docs, ADRs, and dependency diagrams
+- _"What are the known issues with billing?"_ → List of open tickets, past incidents, and recurring patterns
+- _"What's special about Customer X's billing setup?"_ → Complete history of their custom configurations, past issues, and workarounds
+- _"Who should I talk to about the payment gateway integration?"_ → Identifies Marcus as the most active contributor with links to his relevant PRs and discussions
+
+**Result: Priya is productive from day one without repeatedly interrupting senior engineers**
+
+## Use Case 4: Context Preservation After Team Changes
+
+### The Situation
+
+Sarah, a senior engineer with 3 years of context, transfers to a different team. She was the primary point of contact for several major customers and had deep knowledge of the auth system.
+
+### Without Yantra
+
+- Sarah writes a 10-page handoff document that covers maybe 30% of what she knows
+- Months later, teams discover gaps when customer-specific issues arise
+- Workarounds Sarah knew about are rediscovered the hard way
+- New team members spend hours debugging issues Sarah could have diagnosed instantly
+
+### With Yantra
+
+- Every conversation Sarah had, every fix she made, every decision she was involved in is already indexed
+- When a customer issue arises that Sarah would have known about, the AI employee surfaces relevant history
+- Architecture decisions Sarah participated in are fully documented with discussion context
+- The team operates as if Sarah's knowledge never left
+
+## Use Case 5: Code Review Context
+
+### The Situation
+
+A pull request touches a critical module that was last modified 8 months ago. The reviewer doesn't have context on why the existing code was written that way.
+
+### Without Yantra
+
+- Reviewer reads through git blame and commit messages
+- Some commits reference ticket numbers that require switching to Linear
+- The original discussion about the architecture choice happened in a Slack thread that's hard to find
+- Review takes longer than necessary due to missing context
+
+### With Yantra
+
+- Reviewer asks the AI employee: _"Why was the token refresh logic implemented this way?"_
+- AI employee surfaces: the original Slack discussion, the performance benchmarks that drove the decision, the 3 subsequent bug fixes, and the customer that triggered the original implementation
+- Review proceeds with full context in minutes

package/lib/templates/content/use-cases/marketing-use-cases.md

@@ -0,0 +1,128 @@
+# Marketing Use Cases
+
+Detailed examples of how marketing teams leverage Yantra AI employees to maintain a consistent brand presence, amplify product launches, and never miss engagement opportunities.
+
+## Use Case 1: Product Launch Amplification
+
+### The Situation
+
+Engineering just shipped a major feature: real-time collaborative dashboards.
+
+### Without Yantra
+
+- Marketing planned to write about it, but campaign work took priority
+- Five days later, someone drafts a quick LinkedIn post
+- The post gets modest engagement because the news is already stale
+- No X/Twitter thread was created
+- The blog post is still in the backlog
+
+### With Yantra
+
+- AI employee detects the release from GitHub and the #engineering Slack announcement
+- Within an hour, drafts are ready:
+    - LinkedIn post: Professional announcement highlighting customer value
+    - X/Twitter thread: 5-tweet thread breaking down the feature with visuals (copy suggested)
+    - Internal Slack update: Suggested messaging for the sales team
+- Marketing reviews and approves with minor edits
+- Posts scheduled for optimal engagement times across platforms
+
+**Result: Feature launch amplified across all channels on the same day**
+
+## Use Case 2: Consistent Social Presence
+
+### The Situation
+
+The marketing lead knows they should post 3-4 times per week on LinkedIn, but last month they managed only 2 posts total.
+
+### Without Yantra
+
+- Content ideas feel forced and require dedicated brainstorming time
+- Writing each post takes 30-60 minutes with editing and formatting
+- Scheduling is manual and often forgotten
+- The company's social presence appears inactive
+
+### With Yantra
+
+- AI employee maintains a steady content pipeline sourced from:
+    - Product updates and changelog entries
+    - Industry news relevant to the target audience
+    - Internal thought leadership ideas shared in Slack
+    - Repurposed blog content and webinar takeaways
+- Drafts are delivered for review on a consistent schedule
+- Marketing reviews, edits, and approves — taking 5-10 minutes per post
+- Posts are scheduled at peak engagement times
+
+**Result: 4 LinkedIn posts and 6 X/Twitter updates published per week with minimal effort**
+
+## Use Case 3: Real-Time Engagement Response
+
+### The Situation
+
+A well-known industry thought leader comments on one of your LinkedIn posts with a thoughtful question about your approach.
+
+### Without Yantra
+
+- The comment is noticed 2 days later during a social media check
+- The thought leader has moved on to other conversations
+- The engagement opportunity and potential relationship building are lost
+
+### With Yantra
+
+- AI employee detects the high-profile interaction within minutes
+- Sends an immediate Slack alert: _"Sarah Chen (VP Product at TechGiant, 15K followers) commented on your cloud migration post. Draft reply ready."_
+- Marketing reviews the drafted reply (contextually appropriate, professional, engaging)
+- Response posted within the hour
+
+**Result: Meaningful engagement with an influential industry voice**
+
+## Use Case 4: Competitor Launch Response
+
+### The Situation
+
+Your main competitor announces a new feature that overlaps with your core functionality.
+
+### Without Yantra
+
+- Marketing finds out from a coworker a few days later
+- Scrambles to draft a positioning response
+- The social media conversation has already moved on
+- No proactive content was created during the peak attention window
+
+### With Yantra
+
+- AI employee detects the competitor announcement through brand monitoring
+- Within 30 minutes, delivers:
+    - Summary of the competitor's announcement and market reaction
+    - Social media sentiment analysis around the announcement
+    - Draft response content: thought leadership post positioning your approach differently
+    - Suggested talking points for the sales team
+- Marketing reviews and publishes a well-crafted response while the topic is still trending
+
+**Result: Proactive competitive positioning instead of reactive scrambling**
+
+## Use Case 5: Customer Success Content
+
+### The Situation
+
+A customer shares a great result in your community Slack: _"We reduced our response time by 80% using Yantra's automation features!"_
+
+### Without Yantra
+
+- The message is seen by a few team members who react with emoji
+- Nobody follows up to ask if it can be shared publicly
+- A great testimonial opportunity is lost
+
+### With Yantra
+
+- AI employee detects the customer success signal
+- Flags it to marketing with context:
+    - Customer details: Company name, tier, industry
+    - Their usage patterns and features they've adopted
+    - Relationship history: How long they've been a customer
+- Suggests:
+    - Ask permission to share as a testimonial
+    - Draft LinkedIn post featuring their success
+    - Case study outline based on their journey
+- Marketing coordinates with the customer success team to follow up
+
+**Result: Organic customer success turned into marketing content**

package/lib/templates/content/use-cases/sales-use-cases.md

@@ -0,0 +1,123 @@
+# Sales Use Cases
+
+Detailed examples of how sales teams leverage Yantra AI employees to close more deals, maintain perfect CRM hygiene, and never miss a follow-up.
+
+## Use Case 1: Post-Call CRM Automation
+
+### The Situation
+
+Alex just finished a 45-minute discovery call with a prospective enterprise customer.
+
+### Without Yantra
+
+- Alex opens HubSpot and tries to capture the key points before forgetting
+- Types abbreviated notes that will make little sense in 2 weeks
+- Updates the deal stage from "Discovery" to "Proposal"
+- Creates a follow-up task for next week
+- Drafts a recap email
+- Total admin time: 20+ minutes
+
+### With Yantra
+
+- AI employee transcribes the Zoom call and extracts key points:
+    - Customer's primary pain points: manual reporting and data silos
+    - Budget range discussed: $50-75K annually
+    - Decision maker: VP of Operations (was on the call)
+    - Timeline: Decision by end of Q2
+    - Next step: Send pricing proposal by Friday
+- HubSpot updated automatically: deal stage, revenue estimate, close date, detailed notes
+- Follow-up task created for Thursday
+- Recap email drafted and sent for Alex's review
+
+**Total admin time: 2 minutes to review and approve**
+
+## Use Case 2: Never Lose a Lead
+
+### The Situation
+
+Lisa has 47 active opportunities in her pipeline. Three weeks ago, she had a great initial call with DataFlow Inc.
+
+### Without Yantra
+
+- Lisa forgot about DataFlow — it's buried among 46 other deals
+- DataFlow's prospect got a call from a competitor and signed with them
+- Lisa discovers the lost deal during the next pipeline review
+
+### With Yantra
+
+- Day 5: AI employee sends a reminder: _"DataFlow hasn't received follow-up since your initial call. Draft check-in email ready for review."_
+- Day 12: AI employee detects DataFlow visited the pricing page (via HubSpot tracking): _"DataFlow is showing buying signals. Conference call notes from Aug 3 attached. Suggested approach: reference their reporting pain points."_
+- Lisa sends the check-in and schedules a demo
+
+**Result: Lead stays warm, pipeline stays clean**
+
+## Use Case 3: Pre-Meeting Preparation
+
+### The Situation
+
+Jordan has a renewal meeting with Enterprise Customer ABC in 15 minutes. The last conversation was 3 months ago.
+
+### Without Yantra
+
+- Jordan scrambles through HubSpot's activity log
+- Searches email for the last exchange
+- Checks Slack for any mentions of ABC
+- Goes into the meeting with partial context
+
+### With Yantra
+
+- 30 minutes before the call, AI employee delivers:
+    - Last meeting summary: Discussed expansion to the marketing team, Jordan promised a custom demo
+    - Open support tickets: One P2 ticket about API rate limits (resolved last week)
+    - Product updates: Three features shipped since last conversation, two relevant to ABC's use case
+    - Relationship note: ABC's champion (Maria, VP Engineering) recently promoted to SVP
+    - Suggested talking points: Congratulate Maria on promotion, share relevant product updates, revisit expansion discussion
+
+**Result: Jordan walks in fully prepared and makes a great impression**
+
+## Use Case 4: Pipeline Accuracy and Forecasting
+
+### The Situation
+
+The VP of Sales needs an accurate Q1 forecast for the board meeting on Monday.
+
+### Without Yantra
+
+- Pipeline review reveals deal stages are 2-4 weeks stale
+- Several deals marked "Negotiation" haven't had contact in 3 weeks
+- One deal marked "Discovery" actually received a signed contract last week
+- The forecast requires significant manual adjustment and is still unreliable
+
+### With Yantra
+
+- Every deal stage reflects actual interactions (calls, emails, contract status)
+- Stale deals are already flagged with specific risk reasons
+- Signed deals are moved to "Closed Won" the day documents are received
+- AI employee provides a confidence-weighted forecast: $2.4M committed, $800K likely, $1.2M at risk
+- Specific reasoning for each category is available on demand
+
+**Result: Board gets an accurate, trustworthy forecast backed by real data**
+
+## Use Case 5: Competitive Intelligence During Deals
+
+### The Situation
+
+During a call, a prospect mentions they're also evaluating a competitor's product.
+
+### Without Yantra
+
+- The sales rep makes a note to research the competitor
+- Forgets to do it before the next call
+- Goes into the follow-up without a competitive response strategy
+
+### With Yantra
+
+- AI employee detects the competitor mention from call transcription
+- Within minutes, provides:
+    - Recent competitive intel from other deals
+    - Messaging that worked against this competitor in past wins
+    - Feature comparison highlighting Yantra's advantages
+    - Relevant customer success stories for similar objections
+- Suggested response strategy included in the follow-up prep brief
+
+**Result: Every competitive encounter is handled with data-backed positioning**