@adminide-stack/yantra-help-browser 12.0.16-alpha.20 → 12.0.16-alpha.21
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/lib/components/HelpCenterFooter.d.ts.map +1 -1
- package/lib/components/HelpCenterFooter.js +93 -73
- package/lib/components/HelpCenterFooter.js.map +1 -1
- package/lib/components/HelpCenterHeader.d.ts.map +1 -1
- package/lib/components/HelpCenterHeader.js +57 -12
- package/lib/components/HelpCenterHeader.js.map +1 -1
- package/lib/components/SearchBar.js +1 -1
- package/lib/pages/HelpCenter/components/HelpCategoryCard.d.ts +2 -0
- package/lib/pages/HelpCenter/components/HelpCategoryCard.d.ts.map +1 -1
- package/lib/pages/HelpCenter/components/HelpCategoryCard.js +135 -50
- package/lib/pages/HelpCenter/components/HelpCategoryCard.js.map +1 -1
- package/lib/pages/HelpCenter/components/Icons.d.ts +10 -0
- package/lib/pages/HelpCenter/components/Icons.d.ts.map +1 -1
- package/lib/pages/HelpCenter/components/Icons.js +211 -1
- package/lib/pages/HelpCenter/components/Icons.js.map +1 -1
- package/lib/pages/HelpCenter/components/PopularArticle.d.ts.map +1 -1
- package/lib/pages/HelpCenter/components/PopularArticle.js +17 -23
- package/lib/pages/HelpCenter/components/PopularArticle.js.map +1 -1
- package/lib/pages/HelpCenter/index.d.ts.map +1 -1
- package/lib/pages/HelpCenter/index.js +105 -30
- package/lib/pages/HelpCenter/index.js.map +1 -1
- package/lib/pages/HelpCenter/mockData.d.ts.map +1 -1
- package/lib/pages/HelpCenter/mockData.js +14 -6
- package/lib/pages/HelpCenter/mockData.js.map +1 -1
- package/lib/templates/content/ai-employees/ai-employees-overview.md +97 -0
- package/lib/templates/content/ai-employees/getting-started-ai-employees.md +119 -0
- package/lib/templates/content/ai-employees/how-ai-employees-work.md +123 -0
- package/lib/templates/content/ai-employees/supervised-mode.md +141 -0
- package/lib/templates/content/content-manifest.json +2082 -93
- package/lib/templates/content/integrations/crm-integrations.md +130 -0
- package/lib/templates/content/integrations/github-integration.md +95 -0
- package/lib/templates/content/integrations/integrations-overview.md +142 -0
- package/lib/templates/content/integrations/monitoring-integrations.md +109 -0
- package/lib/templates/content/integrations/productivity-integrations.md +129 -0
- package/lib/templates/content/integrations/slack-integration.md +79 -0
- package/lib/templates/content/openclaw/openclaw-architecture.md +202 -0
- package/lib/templates/content/openclaw/openclaw-contribution.md +107 -0
- package/lib/templates/content/openclaw/openclaw-overview.md +152 -0
- package/lib/templates/content/platform-features/always-watching.md +63 -0
- package/lib/templates/content/platform-features/instant-context.md +67 -0
- package/lib/templates/content/platform-features/instant-onboarding.md +80 -0
- package/lib/templates/content/platform-features/platform-overview.md +58 -0
- package/lib/templates/content/platform-features/proactive-alerts.md +88 -0
- package/lib/templates/content/platform-features/smart-escalation.md +93 -0
- package/lib/templates/content/security-compliance/audit-trail.md +112 -0
- package/lib/templates/content/security-compliance/compliance.md +120 -0
- package/lib/templates/content/security-compliance/data-encryption.md +94 -0
- package/lib/templates/content/security-compliance/security-overview.md +186 -0
- package/lib/templates/content/security-compliance/vm-isolation.md +126 -0
- package/lib/templates/content/solutions-engineering/bug-tracking-context.md +126 -0
- package/lib/templates/content/solutions-engineering/engineering-overview.md +107 -0
- package/lib/templates/content/solutions-engineering/error-monitoring.md +120 -0
- package/lib/templates/content/solutions-engineering/institutional-memory.md +120 -0
- package/lib/templates/content/solutions-marketing/brand-monitoring.md +135 -0
- package/lib/templates/content/solutions-marketing/content-automation.md +111 -0
- package/lib/templates/content/solutions-marketing/marketing-overview.md +108 -0
- package/lib/templates/content/solutions-marketing/social-media-management.md +108 -0
- package/lib/templates/content/solutions-sales/call-preparation.md +106 -0
- package/lib/templates/content/solutions-sales/crm-automation.md +119 -0
- package/lib/templates/content/solutions-sales/lead-management.md +108 -0
- package/lib/templates/content/solutions-sales/sales-overview.md +120 -0
- package/lib/templates/content/use-cases/engineering-use-cases.md +123 -0
- package/lib/templates/content/use-cases/marketing-use-cases.md +128 -0
- package/lib/templates/content/use-cases/sales-use-cases.md +123 -0
- package/lib/templates/content/use-cases/support-use-cases.md +120 -0
- package/lib/templates/content/use-cases/use-cases-overview.md +115 -0
- package/package.json +2 -2
- package/lib/pages/HelpCenter/components/BookStack.js +0 -36
- package/lib/pages/HelpCenter/components/BookStack.js.map +0 -1
|
@@ -0,0 +1,123 @@
|
|
|
1
|
+
# Sales Use Cases
|
|
2
|
+
|
|
3
|
+
Detailed examples of how sales teams leverage Yantra AI employees to close more deals, maintain perfect CRM hygiene, and never miss a follow-up.
|
|
4
|
+
|
|
5
|
+
## Use Case 1: Post-Call CRM Automation
|
|
6
|
+
|
|
7
|
+
### The Situation
|
|
8
|
+
|
|
9
|
+
Alex just finished a 45-minute discovery call with a prospective enterprise customer.
|
|
10
|
+
|
|
11
|
+
### Without Yantra
|
|
12
|
+
|
|
13
|
+
- Alex opens HubSpot and tries to capture the key points before forgetting
|
|
14
|
+
- Types abbreviated notes that will make little sense in 2 weeks
|
|
15
|
+
- Updates the deal stage from "Discovery" to "Proposal"
|
|
16
|
+
- Creates a follow-up task for next week
|
|
17
|
+
- Drafts a recap email
|
|
18
|
+
- Total admin time: 20+ minutes
|
|
19
|
+
|
|
20
|
+
### With Yantra
|
|
21
|
+
|
|
22
|
+
- AI employee transcribes the Zoom call and extracts key points:
|
|
23
|
+
- Customer's primary pain points: manual reporting and data silos
|
|
24
|
+
- Budget range discussed: $50-75K annually
|
|
25
|
+
- Decision maker: VP of Operations (was on the call)
|
|
26
|
+
- Timeline: Decision by end of Q2
|
|
27
|
+
- Next step: Send pricing proposal by Friday
|
|
28
|
+
- HubSpot updated automatically: deal stage, revenue estimate, close date, detailed notes
|
|
29
|
+
- Follow-up task created for Thursday
|
|
30
|
+
- Recap email drafted and sent for Alex's review
|
|
31
|
+
|
|
32
|
+
**Total admin time: 2 minutes to review and approve**
|
|
33
|
+
|
|
34
|
+
## Use Case 2: Never Lose a Lead
|
|
35
|
+
|
|
36
|
+
### The Situation
|
|
37
|
+
|
|
38
|
+
Lisa has 47 active opportunities in her pipeline. Three weeks ago, she had a great initial call with DataFlow Inc.
|
|
39
|
+
|
|
40
|
+
### Without Yantra
|
|
41
|
+
|
|
42
|
+
- Lisa forgot about DataFlow — it's buried among 46 other deals
|
|
43
|
+
- DataFlow's prospect got a call from a competitor and signed with them
|
|
44
|
+
- Lisa discovers the lost deal during the next pipeline review
|
|
45
|
+
|
|
46
|
+
### With Yantra
|
|
47
|
+
|
|
48
|
+
- Day 5: AI employee sends a reminder: _"DataFlow hasn't received follow-up since your initial call. Draft check-in email ready for review."_
|
|
49
|
+
- 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."_
|
|
50
|
+
- Lisa sends the check-in and schedules a demo
|
|
51
|
+
|
|
52
|
+
**Result: Lead stays warm, pipeline stays clean**
|
|
53
|
+
|
|
54
|
+
## Use Case 3: Pre-Meeting Preparation
|
|
55
|
+
|
|
56
|
+
### The Situation
|
|
57
|
+
|
|
58
|
+
Jordan has a renewal meeting with Enterprise Customer ABC in 15 minutes. The last conversation was 3 months ago.
|
|
59
|
+
|
|
60
|
+
### Without Yantra
|
|
61
|
+
|
|
62
|
+
- Jordan scrambles through HubSpot's activity log
|
|
63
|
+
- Searches email for the last exchange
|
|
64
|
+
- Checks Slack for any mentions of ABC
|
|
65
|
+
- Goes into the meeting with partial context
|
|
66
|
+
|
|
67
|
+
### With Yantra
|
|
68
|
+
|
|
69
|
+
- 30 minutes before the call, AI employee delivers:
|
|
70
|
+
- Last meeting summary: Discussed expansion to the marketing team, Jordan promised a custom demo
|
|
71
|
+
- Open support tickets: One P2 ticket about API rate limits (resolved last week)
|
|
72
|
+
- Product updates: Three features shipped since last conversation, two relevant to ABC's use case
|
|
73
|
+
- Relationship note: ABC's champion (Maria, VP Engineering) recently promoted to SVP
|
|
74
|
+
- Suggested talking points: Congratulate Maria on promotion, share relevant product updates, revisit expansion discussion
|
|
75
|
+
|
|
76
|
+
**Result: Jordan walks in fully prepared and makes a great impression**
|
|
77
|
+
|
|
78
|
+
## Use Case 4: Pipeline Accuracy and Forecasting
|
|
79
|
+
|
|
80
|
+
### The Situation
|
|
81
|
+
|
|
82
|
+
The VP of Sales needs an accurate Q1 forecast for the board meeting on Monday.
|
|
83
|
+
|
|
84
|
+
### Without Yantra
|
|
85
|
+
|
|
86
|
+
- Pipeline review reveals deal stages are 2-4 weeks stale
|
|
87
|
+
- Several deals marked "Negotiation" haven't had contact in 3 weeks
|
|
88
|
+
- One deal marked "Discovery" actually received a signed contract last week
|
|
89
|
+
- The forecast requires significant manual adjustment and is still unreliable
|
|
90
|
+
|
|
91
|
+
### With Yantra
|
|
92
|
+
|
|
93
|
+
- Every deal stage reflects actual interactions (calls, emails, contract status)
|
|
94
|
+
- Stale deals are already flagged with specific risk reasons
|
|
95
|
+
- Signed deals are moved to "Closed Won" the day documents are received
|
|
96
|
+
- AI employee provides a confidence-weighted forecast: $2.4M committed, $800K likely, $1.2M at risk
|
|
97
|
+
- Specific reasoning for each category is available on demand
|
|
98
|
+
|
|
99
|
+
**Result: Board gets an accurate, trustworthy forecast backed by real data**
|
|
100
|
+
|
|
101
|
+
## Use Case 5: Competitive Intelligence During Deals
|
|
102
|
+
|
|
103
|
+
### The Situation
|
|
104
|
+
|
|
105
|
+
During a call, a prospect mentions they're also evaluating a competitor's product.
|
|
106
|
+
|
|
107
|
+
### Without Yantra
|
|
108
|
+
|
|
109
|
+
- The sales rep makes a note to research the competitor
|
|
110
|
+
- Forgets to do it before the next call
|
|
111
|
+
- Goes into the follow-up without a competitive response strategy
|
|
112
|
+
|
|
113
|
+
### With Yantra
|
|
114
|
+
|
|
115
|
+
- AI employee detects the competitor mention from call transcription
|
|
116
|
+
- Within minutes, provides:
|
|
117
|
+
- Recent competitive intel from other deals
|
|
118
|
+
- Messaging that worked against this competitor in past wins
|
|
119
|
+
- Feature comparison highlighting Yantra's advantages
|
|
120
|
+
- Relevant customer success stories for similar objections
|
|
121
|
+
- Suggested response strategy included in the follow-up prep brief
|
|
122
|
+
|
|
123
|
+
**Result: Every competitive encounter is handled with data-backed positioning**
|
|
@@ -0,0 +1,120 @@
|
|
|
1
|
+
# Support Use Cases
|
|
2
|
+
|
|
3
|
+
Detailed examples of how support teams leverage Yantra AI employees to resolve issues faster, route requests intelligently, and deliver proactive customer care.
|
|
4
|
+
|
|
5
|
+
## Use Case 1: Proactive Issue Detection
|
|
6
|
+
|
|
7
|
+
### The Situation
|
|
8
|
+
|
|
9
|
+
A deployment creates a subtle bug affecting a subset of customers. Customers start experiencing issues but haven't reported them yet.
|
|
10
|
+
|
|
11
|
+
### Without Yantra
|
|
12
|
+
|
|
13
|
+
- Support waits for customer reports to come in
|
|
14
|
+
- First report comes 3 hours after the issue started
|
|
15
|
+
- By then, 15 customers are affected
|
|
16
|
+
- Triage begins from scratch with each new report
|
|
17
|
+
|
|
18
|
+
### With Yantra
|
|
19
|
+
|
|
20
|
+
- AI employee detects the error spike in Sentry within minutes of the deployment
|
|
21
|
+
- Cross-references affected tenants with CRM data to identify impacted customers
|
|
22
|
+
- Proactively alerts the support team: _"Deploy #892 introduced an auth error affecting 8 enterprise accounts. Draft customer communications ready. Engineering already notified."_
|
|
23
|
+
- Support sends proactive "we're aware and working on it" messages before customers report
|
|
24
|
+
|
|
25
|
+
**Result: Customers receive proactive communication instead of discovering issues on their own**
|
|
26
|
+
|
|
27
|
+
## Use Case 2: Intelligent Ticket Routing
|
|
28
|
+
|
|
29
|
+
### The Situation
|
|
30
|
+
|
|
31
|
+
A customer submits a support request: _"Our API integration keeps timing out during peak hours."_
|
|
32
|
+
|
|
33
|
+
### Without Yantra
|
|
34
|
+
|
|
35
|
+
- Ticket goes to the general support queue
|
|
36
|
+
- First-line support spends time understanding the issue
|
|
37
|
+
- Escalated to engineering after 30 minutes
|
|
38
|
+
- Engineering spends another 30 minutes gathering context
|
|
39
|
+
|
|
40
|
+
### With Yantra
|
|
41
|
+
|
|
42
|
+
- AI employee analyzes the request and immediately:
|
|
43
|
+
- Checks the customer's API usage patterns and recent error logs
|
|
44
|
+
- Identifies related Sentry errors in the API service
|
|
45
|
+
- Finds a similar issue from another customer resolved last month
|
|
46
|
+
- Links to the relevant Linear ticket and resolution
|
|
47
|
+
- Routes directly to the appropriate engineering team with full context
|
|
48
|
+
- Suggests a workaround based on the previous resolution
|
|
49
|
+
|
|
50
|
+
**Result: Resolution path identified in seconds instead of hours of back-and-forth**
|
|
51
|
+
|
|
52
|
+
## Use Case 3: Customer Context for Support Agents
|
|
53
|
+
|
|
54
|
+
### The Situation
|
|
55
|
+
|
|
56
|
+
A support agent receives a call from a frustrated enterprise customer who's had three previous issues this quarter.
|
|
57
|
+
|
|
58
|
+
### Without Yantra
|
|
59
|
+
|
|
60
|
+
- Agent searches CRM for the customer while on the call
|
|
61
|
+
- Can see basic ticket history but not the full context
|
|
62
|
+
- Customer has to re-explain their situation and history
|
|
63
|
+
- Frustration increases for both parties
|
|
64
|
+
|
|
65
|
+
### With Yantra
|
|
66
|
+
|
|
67
|
+
- When the call starts, AI employee already has the customer brief ready:
|
|
68
|
+
- Previous 3 issues with resolutions and root causes
|
|
69
|
+
- Current open tickets and their status
|
|
70
|
+
- Customer's account tier, renewal date, and relationship health
|
|
71
|
+
- Preferred communication style and escalation contacts
|
|
72
|
+
- Product features they use most heavily
|
|
73
|
+
- Agent starts the conversation with full context
|
|
74
|
+
|
|
75
|
+
**Result: Empathetic, informed support from the first moment**
|
|
76
|
+
|
|
77
|
+
## Use Case 4: SLA Compliance Monitoring
|
|
78
|
+
|
|
79
|
+
### The Situation
|
|
80
|
+
|
|
81
|
+
Your enterprise support SLA guarantees first response within 1 hour and resolution within 8 hours for P1 issues.
|
|
82
|
+
|
|
83
|
+
### Without Yantra
|
|
84
|
+
|
|
85
|
+
- SLA tracking depends on manual agent updates to ticket status
|
|
86
|
+
- Tickets occasionally breach SLA because nobody noticed the clock
|
|
87
|
+
- Monthly SLA reports are assembled manually from incomplete data
|
|
88
|
+
- Escalation happens after breaches, not before
|
|
89
|
+
|
|
90
|
+
### With Yantra
|
|
91
|
+
|
|
92
|
+
- AI employee tracks every ticket against SLA targets in real time
|
|
93
|
+
- 15-minute warning before approaching first response deadline
|
|
94
|
+
- Auto-escalation if a P1 ticket is unacknowledged after 30 minutes
|
|
95
|
+
- Real-time dashboard showing SLA compliance and at-risk tickets
|
|
96
|
+
- Proactive reassignment if the assigned agent is unavailable
|
|
97
|
+
|
|
98
|
+
**Result: SLA compliance improves from 85% to 98%+**
|
|
99
|
+
|
|
100
|
+
## Use Case 5: Knowledge Base from Support Interactions
|
|
101
|
+
|
|
102
|
+
### The Situation
|
|
103
|
+
|
|
104
|
+
Support agents repeatedly answer the same questions about a specific feature. The knowledge base article for it is outdated.
|
|
105
|
+
|
|
106
|
+
### Without Yantra
|
|
107
|
+
|
|
108
|
+
- Each agent writes a slightly different response
|
|
109
|
+
- Quality varies significantly between agents
|
|
110
|
+
- Nobody has time to update the knowledge base
|
|
111
|
+
- New agents struggle with the topic
|
|
112
|
+
|
|
113
|
+
### With Yantra
|
|
114
|
+
|
|
115
|
+
- AI employee identifies the recurring question pattern
|
|
116
|
+
- Suggests a knowledge base update with the most accurate and complete response compiled from multiple agent interactions
|
|
117
|
+
- Flags the outdated article to the documentation team
|
|
118
|
+
- In the meantime, suggests the best response automatically when similar tickets come in
|
|
119
|
+
|
|
120
|
+
**Result: Consistent, high-quality responses and an ever-improving knowledge base**
|
|
@@ -0,0 +1,115 @@
|
|
|
1
|
+
# Use Cases Overview
|
|
2
|
+
|
|
3
|
+
Yantra AI employees serve teams across every function. This guide covers the most common use cases and how organizations deploy AI employees to eliminate busywork, preserve knowledge, and keep teams in sync.
|
|
4
|
+
|
|
5
|
+
## Use Cases by Team
|
|
6
|
+
|
|
7
|
+
### Engineering Use Cases
|
|
8
|
+
|
|
9
|
+
| Use Case | Description | Impact |
|
|
10
|
+
| -------------------------- | ------------------------------------------------------------------------------------ | ----------------------------------- |
|
|
11
|
+
| **Bug Triage Automation** | Correlate customer reports with error logs, existing tickets, and recent deployments | Hours saved per incident |
|
|
12
|
+
| **Deploy Monitoring** | Automatic error-to-deploy correlation with rollback recommendations | Faster incident response |
|
|
13
|
+
| **Knowledge Preservation** | Every fix, decision, and workaround indexed and searchable | Eliminates knowledge silos |
|
|
14
|
+
| **Engineer Onboarding** | New team members get instant access to organizational context | Days-to-productive reduced to hours |
|
|
15
|
+
| **Alert Deduplication** | Group related errors and surface only genuinely new issues | Reduced alert fatigue |
|
|
16
|
+
|
|
17
|
+
[Detailed Engineering Solutions →](/help-center/solutions-engineering/engineering-overview)
|
|
18
|
+
|
|
19
|
+
### Sales Use Cases
|
|
20
|
+
|
|
21
|
+
| Use Case | Description | Impact |
|
|
22
|
+
| ------------------------- | ------------------------------------------------------------ | ------------------------- |
|
|
23
|
+
| **CRM Auto-Update** | Automatically log calls, emails, and update deal stages | Pipeline accuracy to 95%+ |
|
|
24
|
+
| **Pre-Call Briefing** | Context package delivered before every meeting | Always prepared |
|
|
25
|
+
| **Follow-Up Assurance** | Every lead gets timely follow-up with personalized messaging | 100% follow-up rate |
|
|
26
|
+
| **Pipeline Intelligence** | Real-time deal health scoring and at-risk identification | Better forecasting |
|
|
27
|
+
| **Lead Re-Engagement** | Dormant lead identification and reactivation campaigns | Recovered revenue |
|
|
28
|
+
|
|
29
|
+
[Detailed Sales Solutions →](/help-center/solutions-sales/sales-overview)
|
|
30
|
+
|
|
31
|
+
### Marketing Use Cases
|
|
32
|
+
|
|
33
|
+
| Use Case | Description | Impact |
|
|
34
|
+
| ------------------------ | -------------------------------------------------------- | ----------------------- |
|
|
35
|
+
| **Social Publishing** | Consistent content across LinkedIn and X/Twitter | Active social presence |
|
|
36
|
+
| **Content from Updates** | Product releases auto-transformed into marketing content | Every update amplified |
|
|
37
|
+
| **Engagement Response** | Real-time monitoring and response to social interactions | No missed opportunities |
|
|
38
|
+
| **Brand Tracking** | Continuous monitoring of brand mentions and sentiment | Full brand awareness |
|
|
39
|
+
| **Competitor Watch** | Track competitor activity and market positioning | Strategic advantage |
|
|
40
|
+
|
|
41
|
+
[Detailed Marketing Solutions →](/help-center/solutions-marketing/marketing-overview)
|
|
42
|
+
|
|
43
|
+
### Support Use Cases
|
|
44
|
+
|
|
45
|
+
| Use Case | Description | Impact |
|
|
46
|
+
| ----------------------- | -------------------------------------------------------------- | ---------------------- |
|
|
47
|
+
| **Issue Routing** | Auto-route customer issues to the right team with full context | Faster resolution |
|
|
48
|
+
| **Context Retrieval** | Instant access to customer history across all tools | Better support quality |
|
|
49
|
+
| **Proactive Outreach** | Detect issues before customers report them | Improved satisfaction |
|
|
50
|
+
| **Resolution Patterns** | Surface past resolutions for similar issues | Consistent quality |
|
|
51
|
+
| **SLA Monitoring** | Track response and resolution times against targets | SLA compliance |
|
|
52
|
+
|
|
53
|
+
## Cross-Functional Use Cases
|
|
54
|
+
|
|
55
|
+
### Morning Briefings
|
|
56
|
+
|
|
57
|
+
Every team member starts the day with a personalized summary of:
|
|
58
|
+
|
|
59
|
+
- What happened overnight across their relevant tools
|
|
60
|
+
- Critical items requiring immediate attention
|
|
61
|
+
- Updates on items they're tracking
|
|
62
|
+
- Upcoming meetings with prepared context
|
|
63
|
+
|
|
64
|
+
### Institutional Memory
|
|
65
|
+
|
|
66
|
+
Across all departments, Yantra maintains a living knowledge base:
|
|
67
|
+
|
|
68
|
+
- Every conversation, decision, and action is indexed
|
|
69
|
+
- Historical patterns are identified and surfaced when relevant
|
|
70
|
+
- New team members access the full context of their role from day one
|
|
71
|
+
- No knowledge is lost when people change roles
|
|
72
|
+
|
|
73
|
+
### Cross-Team Coordination
|
|
74
|
+
|
|
75
|
+
When activity in one team affects another:
|
|
76
|
+
|
|
77
|
+
- Engineering deploys that affect sales demos get flagged
|
|
78
|
+
- Customer complaints that indicate product bugs are routed to engineering
|
|
79
|
+
- Marketing campaigns that generate leads are tracked through to sales outcomes
|
|
80
|
+
- Support patterns that suggest product improvements reach the product team
|
|
81
|
+
|
|
82
|
+
## Industry-Specific Use Cases
|
|
83
|
+
|
|
84
|
+
### SaaS Companies
|
|
85
|
+
|
|
86
|
+
- Customer health scoring from multi-signal analysis
|
|
87
|
+
- Feature adoption tracking across accounts
|
|
88
|
+
- Churn risk detection from engagement patterns
|
|
89
|
+
- Upsell opportunity identification from usage data
|
|
90
|
+
|
|
91
|
+
### Professional Services
|
|
92
|
+
|
|
93
|
+
- Client relationship management across partner handoffs
|
|
94
|
+
- Project status tracking across distributed teams
|
|
95
|
+
- Resource utilization monitoring and optimization
|
|
96
|
+
- Proposal preparation with relevant case studies
|
|
97
|
+
|
|
98
|
+
### E-Commerce
|
|
99
|
+
|
|
100
|
+
- Checkout issue detection and resolution
|
|
101
|
+
- Inventory alert correlation with customer impact
|
|
102
|
+
- Marketing campaign performance tracking
|
|
103
|
+
- Customer journey analytics across touchpoints
|
|
104
|
+
|
|
105
|
+
## Measuring ROI
|
|
106
|
+
|
|
107
|
+
Track the business impact of your AI employees:
|
|
108
|
+
|
|
109
|
+
| Metric | How to Measure |
|
|
110
|
+
| -------------------- | -------------------------------------------------------- |
|
|
111
|
+
| **Time saved** | Hours previously spent on manual tasks now handled by AI |
|
|
112
|
+
| **Response time** | Time from event to response before and after Yantra |
|
|
113
|
+
| **Data accuracy** | CRM/pipeline accuracy improvement |
|
|
114
|
+
| **Knowledge access** | Reduction in "who knows about X?" interruptions |
|
|
115
|
+
| **Onboarding speed** | Time to productivity for new team members |
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@adminide-stack/yantra-help-browser",
|
|
3
|
-
"version": "12.0.16-alpha.
|
|
3
|
+
"version": "12.0.16-alpha.21",
|
|
4
4
|
"description": "Sample core for higher packages to depend on",
|
|
5
5
|
"license": "ISC",
|
|
6
6
|
"author": "Yantra App",
|
|
@@ -71,5 +71,5 @@
|
|
|
71
71
|
"typescript": {
|
|
72
72
|
"definition": "lib/index.d.ts"
|
|
73
73
|
},
|
|
74
|
-
"gitHead": "
|
|
74
|
+
"gitHead": "17e0eba5eda351704669460020b4024d29e30585"
|
|
75
75
|
}
|
|
@@ -1,36 +0,0 @@
|
|
|
1
|
-
import {jsx,jsxs}from'react/jsx-runtime';const BookStack = () => {
|
|
2
|
-
return jsx("div", {
|
|
3
|
-
className: "transform w-full p-20",
|
|
4
|
-
children: jsxs("div", {
|
|
5
|
-
className: "relative h-full w-full",
|
|
6
|
-
children: [jsx("img", {
|
|
7
|
-
src: "https://images.unsplash.com/photo-1495446815901-a7297e633e8d?auto=format&fit=crop&q=80&w=1000",
|
|
8
|
-
alt: "Stack of books",
|
|
9
|
-
className: "h-full w-full rounded-lg object-cover",
|
|
10
|
-
style: {
|
|
11
|
-
clipPath: "polygon(0 0, 100% 0, 100% 100%, 0 100%)",
|
|
12
|
-
transform: "perspective(1200px) rotateY(-15deg) rotateX(5deg)",
|
|
13
|
-
boxShadow: "0 25px 50px -12px rgba(0, 0, 0, 0.25)"
|
|
14
|
-
}
|
|
15
|
-
}), jsx("div", {
|
|
16
|
-
className: "absolute -right-0 -top-0 h-full w-full rounded-lg bg-teal-400 opacity-20",
|
|
17
|
-
style: {
|
|
18
|
-
transform: "perspective(1200px) rotateY(-15deg) rotateX(5deg) translateZ(-20px)",
|
|
19
|
-
boxShadow: "0 25px 50px -12px rgba(0, 0, 0, 0.25)"
|
|
20
|
-
}
|
|
21
|
-
}), jsx("div", {
|
|
22
|
-
className: "absolute -right-6 -top-6 h-full w-full rounded-lg bg-teal-500 opacity-10",
|
|
23
|
-
style: {
|
|
24
|
-
transform: "perspective(1200px) rotateY(-15deg) rotateX(5deg) translateZ(-40px)",
|
|
25
|
-
boxShadow: "0 25px 50px -12px rgba(0, 0, 0, 0.25)"
|
|
26
|
-
}
|
|
27
|
-
}), jsx("div", {
|
|
28
|
-
className: "absolute -right-12 -top-12 h-full w-full rounded-lg bg-teal-500 opacity-10",
|
|
29
|
-
style: {
|
|
30
|
-
transform: "perspective(1200px) rotateY(-15deg) rotateX(5deg) translateZ(-40px)",
|
|
31
|
-
boxShadow: "0 25px 50px -12px rgba(0, 0, 0, 0.25)"
|
|
32
|
-
}
|
|
33
|
-
})]
|
|
34
|
-
})
|
|
35
|
-
});
|
|
36
|
-
};export{BookStack};//# sourceMappingURL=BookStack.js.map
|
|
@@ -1 +0,0 @@
|
|
|
1
|
-
{"version":3,"file":"BookStack.js","sources":["../../../../src/pages/HelpCenter/components/BookStack.tsx"],"sourcesContent":[null],"names":["_jsx","_jsxs"],"mappings":"yCAEO,MAAM,SAAS,GAAa,MAAK;SAC/BA,GACA,CAAA,KAAA,EAAA;AAQG,IAAA,SAAA,EAAA,uBAAmD;AACnD,IAAA,QAAA,EAAAC,IAAA,CAAA,KAAA,EAAA;AACA,MAAA,SAAA,EAAA,wBAAkD;AACnD,MAAA,QAAA,EAAA,CAAAD,GAAA,CAAA,KAKD,EAAA;AAEE,QAAA,GAAA,EAAA,+FAAgF;AAChF,QAAA,GAAA,EAAA,gBAAA;AACD,QAAA,SAAA,EAAA,uCAImF;AAElF,QAAA,KAAA,EAAA;AACA,UAAA,QAAA,EAAA,yCAAkD;AACnD,UAAA,SAAA,EAAA,mDAGqF;AAEpF,UAAA,SAAA,EAAA;AACA;qBAEG;AAIf,QAAE,SAAA,EAAA,0EAAA;;;;;;;;;;;;;;;;;;;;"}
|