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

package/lib/templates/content/ai-employees/getting-started-ai-employees.md

@@ -0,0 +1,119 @@
+---
+title: 'Getting Started with AI Employees'
+---
+
+# Getting Started with AI Employees
+
+Setting up your first Yantra AI employee takes approximately 5 minutes. This guide walks you through the complete setup process from tool connection to your first proactive insight.
+
+## Prerequisites
+
+- A Yantra account (free trial available)
+- Admin or owner access to the tools you want to connect
+- A communication channel where you'd like to receive updates (Slack, WhatsApp, Telegram, or email)
+
+## Step 1: Connect Your Tools (2 minutes)
+
+### One-Click OAuth Setup
+
+From your Yantra dashboard, navigate to **Integrations** and connect your tools:
+
+1. Click the tool you want to connect (e.g., Slack, GitHub, HubSpot)
+2. Authorize access through the OAuth flow — same as adding any other app
+3. Select the specific resources to monitor (channels, repos, projects)
+4. Repeat for each tool your team uses
+
+### Supported Tools
+
+- **Communication**: Slack, Microsoft Teams, Gmail
+- **Development**: GitHub, GitLab, Bitbucket
+- **Error Tracking**: Sentry, Datadog, PagerDuty
+- **Project Management**: Linear, Jira, Asana
+- **CRM**: HubSpot, Salesforce
+- **Documentation**: Notion, Confluence
+- **Social**: LinkedIn, X/Twitter
+- **Calendar**: Google Calendar, Calendly
+- **Video**: Zoom (for call transcription)
+
+No coding or command-line setup is required. Your AI employee receives the same level of access as a regular team member.
+
+## Step 2: Configure Preferences (3 minutes)
+
+### Define What to Watch
+
+Tell your AI employee what matters most:
+
+- **Error monitoring**: Set severity thresholds (e.g., alert on 10+ occurrences per hour)
+- **Customer tracking**: Define high-priority accounts or customer tiers
+- **Deal tracking**: Specify pipeline stages that need attention
+- **Channel monitoring**: Select which Slack channels to watch actively
+
+### Set Notification Preferences
+
+- **Primary channel**: Where you want to receive most communications
+- **Urgent channel**: Where critical alerts get delivered (e.g., SMS, WhatsApp)
+- **Quiet hours**: Time windows where non-critical notifications are batched
+- **Daily briefing time**: When you'd like your morning summary
+
+### Choose Your AI Employee Type
+
+Select the focus area for your AI employee:
+
+- **Engineering**: Optimized for development workflows, error correlation, and deployment tracking
+- **Sales**: Optimized for CRM management, call preparation, and lead follow-up
+- **Marketing**: Optimized for content management, social media, and brand monitoring
+- **General**: Balanced across all areas for smaller teams
+
+## Step 3: Start Supervised (Ongoing)
+
+Your AI employee begins in **supervised mode** by default:
+
+1. **Observation begins immediately**: Your AI employee starts processing events from connected tools
+2. **First briefing**: Within hours, you'll receive your first contextualized summary
+3. **Action drafts**: When the AI employee identifies something actionable, it drafts the response and asks for approval
+4. **Review and approve**: Check the draft, edit if needed, and approve to execute
+
+### Example First Interactions
+
+- A morning briefing summarizing overnight activity across your tools
+- A contextual alert linking a customer complaint to a recent error spike
+- A drafted CRM update based on an email exchange it detected
+
+## Step 4: Expand Autonomy (When Ready)
+
+As you build trust with your AI employee:
+
+1. **Review the action log**: See all past actions, their outcomes, and your approval history
+2. **Identify routine actions**: Find action types you consistently approve without modification
+3. **Enable auto-execution**: For those routine actions, switch from "approval required" to "execute automatically"
+4. **Monitor and adjust**: Continue reviewing the daily summary to ensure quality
+
+### Autonomy Levels
+
+| Level               | Description                           | Best For                       |
+| ------------------- | ------------------------------------- | ------------------------------ |
+| **Supervised**      | All actions require approval          | Initial setup, first 1-2 weeks |
+| **Semi-Autonomous** | Routine actions auto-execute          | Established trust, weeks 2-4   |
+| **Autonomous**      | Independent operation with escalation | Mature setup, month 2+         |
+
+## Troubleshooting Setup
+
+### Tool Connection Issues
+
+- Ensure you have admin access to the tool you're connecting
+- Check that your organization allows third-party OAuth integrations
+- Verify your firewall isn't blocking Yantra's API endpoints
+
+### No Events Appearing
+
+- Confirm the correct channels, repos, or projects were selected during setup
+- Check that the connected tool has recent activity
+- Allow up to 5 minutes for initial event ingestion
+
+### Notification Not Received
+
+- Verify your notification channel preference is correctly set
+- Check Slack permissions if using Slack as your primary channel
+- Ensure notifications aren't being filtered by your device settings
+
+For additional help, contact support or visit the [Troubleshooting Guide](/help-center/troubleshooting/common-issues).

package/lib/templates/content/ai-employees/how-ai-employees-work.md

@@ -0,0 +1,123 @@
+---
+title: 'How AI Employees Work'
+---
+
+# How AI Employees Work
+
+This guide explains the technical and operational mechanics behind Yantra AI employees — how they observe, reason, and act within your organization's toolchain.
+
+## Architecture Overview
+
+Each Yantra AI employee runs in a **dedicated, isolated environment** provisioned specifically for your organization. This ensures:
+
+- Your data is completely separated from other customers
+- Processing resources are dedicated to your workload
+- Custom configurations don't interfere with other environments
+
+### Event Pipeline
+
+```
+Your Tools → Yantra Gateway → Event Processor → Context Engine → Action Engine → Your Tools
+```
+
+1. **Yantra Gateway**: Secure API routing layer that receives events from all connected tools via OAuth 2.0 and API keys
+2. **Event Processor**: Normalizes and enriches raw events from different tool formats into a unified event stream
+3. **Context Engine**: Correlates events with historical data, customer profiles, and organizational knowledge
+4. **Action Engine**: Determines appropriate responses, drafts actions, and either executes or queues for approval
+
+## The Observation Layer
+
+### Event Collection
+
+Your AI employee receives real-time events through:
+
+- **Webhooks**: Instant notifications from tools like GitHub, Slack, and Sentry
+- **Polling**: Periodic checks for tools that don't support webhooks
+- **API subscriptions**: Real-time feeds from CRMs and project management tools
+
+### Event Types Processed
+
+- Messages and conversations
+- Code changes and deployments
+- Error logs and performance metrics
+- Customer interactions and deal updates
+- Calendar events and meeting recordings
+- Document changes and wiki updates
+
+## The Reasoning Layer
+
+### Context Graph
+
+Yantra maintains a **context graph** — a dynamic knowledge structure that maps relationships between:
+
+- **People**: Team members, customers, contacts
+- **Projects**: Repositories, deals, campaigns, tickets
+- **Events**: Incidents, deployments, meetings, decisions
+- **Artifacts**: Documents, code, configurations, policies
+
+When a new event arrives, the reasoning layer traverses this graph to understand:
+
+- Who is involved?
+- What systems or projects are related?
+- Has this happened before? How was it resolved?
+- Who should know about this?
+
+### Pattern Recognition
+
+Over time, the AI employee identifies patterns:
+
+- Recurring errors after specific types of deployments
+- Customer issues that correlate with feature releases
+- Sales cycles that follow predictable timelines
+- Marketing content that generates the most engagement
+
+## The Action Layer
+
+### Action Types
+
+| Action       | Description                   | Example                                    |
+| ------------ | ----------------------------- | ------------------------------------------ |
+| **Inform**   | Share a contextual update     | Morning briefing with overnight summary    |
+| **Alert**    | Notify someone about an issue | Critical Sentry error escalation           |
+| **Update**   | Modify a record in a tool     | Update HubSpot deal stage after a call     |
+| **Create**   | Generate a new item           | Create a Linear ticket for a reported bug  |
+| **Draft**    | Prepare content for review    | Draft a follow-up email after a sales call |
+| **Escalate** | Route to a human for decision | Novel issue requiring human judgment       |
+
+### Execution Modes
+
+**Supervised Mode**
+
+- All actions are drafted and presented for approval
+- You can edit, approve, or reject each action
+- Ideal for initial setup and building trust
+
+**Semi-Autonomous Mode**
+
+- Predefined routine actions execute automatically
+- Novel or high-impact actions require approval
+- Good for teams that want automation with oversight
+
+**Autonomous Mode**
+
+- All actions execute independently
+- Exceptions and anomalies are escalated
+- Best for mature setups with well-tuned configurations
+
+## Communication Channels
+
+Your AI employee communicates through the channels your team already uses:
+
+- **Slack**: Primary channel for most teams; supports threads, mentions, and rich messages
+- **WhatsApp**: Mobile-friendly for on-the-go updates and alerts
+- **Telegram**: Lightweight messaging for quick interactions
+- **Email**: Formal communications and detailed reports
+
+## Data Flow and Privacy
+
+- All data is encrypted in transit (TLS 1.2+) and at rest (AES-256)
+- Your AI employee only accesses tools and scopes you've explicitly authorized
+- Data from third-party APIs is never used to train AI models
+- Complete audit trail of every observation, decision, and action
+
+For detailed security information, see [Security Overview](/help-center/security-compliance/security-overview).

package/lib/templates/content/ai-employees/supervised-mode.md

@@ -0,0 +1,141 @@
+---
+title: 'AI Employee Supervised Mode'
+---
+
+# Supervised and Autonomous Modes
+
+Yantra AI employees support a spectrum of operational modes, from fully supervised to fully autonomous. This guide explains each mode, when to use it, and how to transition between them.
+
+## The Trust Spectrum
+
+Yantra's design philosophy centers on **progressive trust**. You start with full oversight and gradually delegate more responsibility as your AI employee proves its reliability.
+
+```
+Supervised → Semi-Autonomous → Autonomous
+(You approve everything)  (Routine auto-executes)  (AI works independently)
+```
+
+## Supervised Mode
+
+### How It Works
+
+In supervised mode, your AI employee:
+
+- **Observes** all events across connected tools freely
+- **Analyzes** and correlates data without restriction
+- **Drafts** all proposed actions (messages, CRM updates, ticket creation, etc.)
+- **Waits** for your explicit approval before executing any action
+
+### When to Use
+
+- During initial setup (first 1-2 weeks)
+- When connecting new tools or expanding scope
+- For high-stakes actions regardless of overall trust level
+- When training the AI employee on new processes
+
+### Approval Workflow
+
+1. AI employee identifies an actionable situation
+2. A draft action appears in your notification channel
+3. You review the draft with full context
+4. Options: **Approve**, **Edit and Approve**, **Reject**, or **Reject with Feedback**
+5. The AI employee learns from every decision
+
+### Example
+
+```
+[Yantra AI Employee - Draft Action]
+
+Situation: Marcus closed deal with TechStart via email 2 hours ago.
+Proposed Action: Update HubSpot deal stage from "Negotiation" to "Closed Won"
+Additional: Log email exchange as activity, set revenue to $48,000/yr
+
+[Approve] [Edit] [Reject]
+```
+
+## Semi-Autonomous Mode
+
+### How It Works
+
+In semi-autonomous mode, you define **action categories** and their trust levels:
+
+| Category                | Trust Level       | Behavior                           |
+| ----------------------- | ----------------- | ---------------------------------- |
+| CRM field updates       | Auto-execute      | Updates happen automatically       |
+| Ticket creation         | Auto-execute      | Tickets created without approval   |
+| Email drafts            | Requires approval | Drafts presented for review        |
+| Customer communications | Requires approval | Always human-approved              |
+| Alert escalation        | Auto-execute      | Alerts sent immediately            |
+| Financial actions       | Requires approval | Budget/pricing changes need review |
+
+### When to Use
+
+- After 1-2 weeks of supervised operation
+- When you've identified actions you consistently approve unchanged
+- For teams that want operational speed with selective oversight
+
+### Configuring Semi-Autonomous Rules
+
+1. Navigate to **AI Employee Settings → Autonomy Rules**
+2. Review the action log for your most common action types
+3. Set trust levels for each action category
+4. Define exceptions (e.g., "auto-update CRM except for Enterprise deals")
+
+## Autonomous Mode
+
+### How It Works
+
+In autonomous mode, your AI employee operates independently:
+
+- Executes all routine actions without approval
+- Handles standard workflows end-to-end
+- Escalates only **anomalies** and **genuinely novel situations** for human review
+- Provides a daily summary of all actions taken
+
+### When to Use
+
+- After 4+ weeks of reliable semi-autonomous operation
+- For well-defined, repetitive workflows
+- When the AI employee has sufficient training data and feedback
+
+### Safeguards
+
+Even in autonomous mode, important safeguards remain:
+
+- **Action limits**: Maximum number of actions per hour before requiring human confirmation
+- **Scope boundaries**: AI employee only acts within explicitly granted permissions
+- **Anomaly detection**: Unusual patterns trigger automatic escalation
+- **Kill switch**: Instantly revert to supervised mode at any time
+- **Audit trail**: Every autonomous action is logged with full context
+
+## Transitioning Between Modes
+
+### Moving to More Autonomy
+
+1. Review your **approval statistics** — look for action types with 95%+ unmodified approval rates
+2. Promote those action types to auto-execute
+3. Monitor the **action quality dashboard** for the first week
+4. Repeat for additional action types as confidence grows
+
+### Reverting to Less Autonomy
+
+- Click **Pause Autonomy** in the AI employee dashboard to immediately switch to supervised mode
+- Individual action categories can be demoted independently
+- No data or configuration is lost during transitions
+
+## Best Practices
+
+1. **Start narrow**: Begin with a small set of connected tools and expand gradually
+2. **Provide feedback**: When rejecting or editing actions, include reasons — this helps the AI improve
+3. **Review weekly**: Check the action summary to ensure quality matches expectations
+4. **Trust but verify**: Even in autonomous mode, regularly review the audit trail
+5. **Set clear boundaries**: Define which actions should never be automated (e.g., customer-facing communications for sensitive accounts)
+
+## Monitoring AI Employee Performance
+
+Track these metrics to guide your trust decisions:
+
+- **Action accuracy**: Percentage of actions approved without modification
+- **False positive rate**: Alerts that were dismissed as irrelevant
+- **Time saved**: Estimated hours saved per week through automation
+- **Escalation quality**: Whether escalated items genuinely required human judgment