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

package/lib/{content → templates/content}/threads/threads-overview.md

@@ -5,12 +5,14 @@ Understanding Yantra's conversation threading system.
 ## What are Threads?
 
 ### Concept
+
 - **Conversation Organization**: Organize conversations
 - **Topic Threading**: Group related discussions
 - **Context Preservation**: Maintain conversation context
 - **Follow-up Management**: Manage follow-up questions
 
 ### Benefits
+
 - **Organization**: Keep conversations organized
 - **Context**: Maintain conversation context
 - **Efficiency**: More efficient conversations
@@ -19,12 +21,14 @@ Understanding Yantra's conversation threading system.
 ## Thread Features
 
 ### Conversation Management
+
 - **Thread Creation**: Create conversation threads
 - **Thread Organization**: Organize threads by topic
 - **Thread Search**: Search within threads
 - **Thread Archiving**: Archive old threads
 
 ### Context Preservation
+
 - **Conversation History**: Complete conversation history
 - **Context Awareness**: Maintain context across messages
 - **Reference Tracking**: Track references and citations
@@ -33,6 +37,7 @@ Understanding Yantra's conversation threading system.
 ## Thread Usage
 
 ### Creating Threads
+
 1. **Start Conversation**: Begin a new conversation
 2. **Create Thread**: Create a new thread
 3. **Add Context**: Add relevant context
@@ -40,6 +45,7 @@ Understanding Yantra's conversation threading system.
 5. **Begin Discussion**: Start the discussion
 
 ### Managing Threads
+
 - **Thread Settings**: Configure thread settings
 - **Member Management**: Manage thread members
 - **Permission Control**: Control thread permissions
@@ -48,12 +54,14 @@ Understanding Yantra's conversation threading system.
 ## Thread Organization
 
 ### Thread Structure
+
 - **Hierarchical Organization**: Organize threads hierarchically
 - **Topic Grouping**: Group threads by topic
 - **Priority Levels**: Set thread priority levels
 - **Status Tracking**: Track thread status
 
 ### Thread Collaboration
+
 - **Member Roles**: Assign member roles
 - **Participation Tracking**: Track participation
 - **Activity Monitoring**: Monitor thread activity

package/lib/{content → templates/content}/troubleshooting/common-issues.md

@@ -5,12 +5,14 @@ Solutions to frequently encountered problems.
 ## Search Problems
 
 ### Search Not Working
+
 - **Check Internet Connection**: Ensure stable internet
 - **Clear Browser Cache**: Clear browser data
 - **Try Different Browser**: Test in another browser
 - **Check Account Status**: Verify account is active
 
 ### Slow Search Results
+
 - **Check Server Status**: Verify Yantra server status
 - **Reduce Query Complexity**: Simplify your search
 - **Try Different Search Mode**: Switch search modes
@@ -19,12 +21,14 @@ Solutions to frequently encountered problems.
 ## Account Issues
 
 ### Login Problems
+
 - **Verify Credentials**: Check username/password
 - **Reset Password**: Use password reset option
 - **Check Email**: Verify email address
 - **Contact Support**: Get help from support team
 
 ### Subscription Issues
+
 - **Check Payment Method**: Verify payment details
 - **Review Billing**: Check billing history
 - **Update Payment Info**: Update payment method
@@ -33,12 +37,14 @@ Solutions to frequently encountered problems.
 ## Performance Issues
 
 ### Slow Loading
+
 - **Clear Browser Cache**: Remove cached data
 - **Disable Extensions**: Turn off browser extensions
 - **Check System Resources**: Monitor CPU/memory usage
 - **Update Browser**: Use latest browser version
 
 ### Crashes and Errors
+
 - **Restart Browser**: Close and reopen browser
 - **Check Error Messages**: Note specific error details
 - **Try Incognito Mode**: Test in private browsing
@@ -47,12 +53,14 @@ Solutions to frequently encountered problems.
 ## Mobile App Issues
 
 ### App Not Working
+
 - **Update App**: Install latest version
 - **Restart App**: Force close and reopen
 - **Check Permissions**: Verify app permissions
 - **Reinstall App**: Uninstall and reinstall
 
 ### Sync Problems
+
 - **Check Internet**: Ensure mobile internet connection
 - **Force Sync**: Manually trigger sync
 - **Clear App Data**: Clear app cache and data

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**

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

@@ -0,0 +1,120 @@
+# Support Use Cases
+
+Detailed examples of how support teams leverage Yantra AI employees to resolve issues faster, route requests intelligently, and deliver proactive customer care.
+
+## Use Case 1: Proactive Issue Detection
+
+### The Situation
+
+A deployment creates a subtle bug affecting a subset of customers. Customers start experiencing issues but haven't reported them yet.
+
+### Without Yantra
+
+- Support waits for customer reports to come in
+- First report comes 3 hours after the issue started
+- By then, 15 customers are affected
+- Triage begins from scratch with each new report
+
+### With Yantra
+
+- AI employee detects the error spike in Sentry within minutes of the deployment
+- Cross-references affected tenants with CRM data to identify impacted customers
+- Proactively alerts the support team: _"Deploy #892 introduced an auth error affecting 8 enterprise accounts. Draft customer communications ready. Engineering already notified."_
+- Support sends proactive "we're aware and working on it" messages before customers report
+
+**Result: Customers receive proactive communication instead of discovering issues on their own**
+
+## Use Case 2: Intelligent Ticket Routing
+
+### The Situation
+
+A customer submits a support request: _"Our API integration keeps timing out during peak hours."_
+
+### Without Yantra
+
+- Ticket goes to the general support queue
+- First-line support spends time understanding the issue
+- Escalated to engineering after 30 minutes
+- Engineering spends another 30 minutes gathering context
+
+### With Yantra
+
+- AI employee analyzes the request and immediately:
+    - Checks the customer's API usage patterns and recent error logs
+    - Identifies related Sentry errors in the API service
+    - Finds a similar issue from another customer resolved last month
+    - Links to the relevant Linear ticket and resolution
+- Routes directly to the appropriate engineering team with full context
+- Suggests a workaround based on the previous resolution
+
+**Result: Resolution path identified in seconds instead of hours of back-and-forth**
+
+## Use Case 3: Customer Context for Support Agents
+
+### The Situation
+
+A support agent receives a call from a frustrated enterprise customer who's had three previous issues this quarter.
+
+### Without Yantra
+
+- Agent searches CRM for the customer while on the call
+- Can see basic ticket history but not the full context
+- Customer has to re-explain their situation and history
+- Frustration increases for both parties
+
+### With Yantra
+
+- When the call starts, AI employee already has the customer brief ready:
+    - Previous 3 issues with resolutions and root causes
+    - Current open tickets and their status
+    - Customer's account tier, renewal date, and relationship health
+    - Preferred communication style and escalation contacts
+    - Product features they use most heavily
+- Agent starts the conversation with full context
+
+**Result: Empathetic, informed support from the first moment**
+
+## Use Case 4: SLA Compliance Monitoring
+
+### The Situation
+
+Your enterprise support SLA guarantees first response within 1 hour and resolution within 8 hours for P1 issues.
+
+### Without Yantra
+
+- SLA tracking depends on manual agent updates to ticket status
+- Tickets occasionally breach SLA because nobody noticed the clock
+- Monthly SLA reports are assembled manually from incomplete data
+- Escalation happens after breaches, not before
+
+### With Yantra
+
+- AI employee tracks every ticket against SLA targets in real time
+- 15-minute warning before approaching first response deadline
+- Auto-escalation if a P1 ticket is unacknowledged after 30 minutes
+- Real-time dashboard showing SLA compliance and at-risk tickets
+- Proactive reassignment if the assigned agent is unavailable
+
+**Result: SLA compliance improves from 85% to 98%+**
+
+## Use Case 5: Knowledge Base from Support Interactions
+
+### The Situation
+
+Support agents repeatedly answer the same questions about a specific feature. The knowledge base article for it is outdated.
+
+### Without Yantra
+
+- Each agent writes a slightly different response
+- Quality varies significantly between agents
+- Nobody has time to update the knowledge base
+- New agents struggle with the topic
+
+### With Yantra
+
+- AI employee identifies the recurring question pattern
+- Suggests a knowledge base update with the most accurate and complete response compiled from multiple agent interactions
+- Flags the outdated article to the documentation team
+- In the meantime, suggests the best response automatically when similar tickets come in
+
+**Result: Consistent, high-quality responses and an ever-improving knowledge base**