@adminide-stack/yantra-help-browser 12.0.16-alpha.2 → 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 -85
- package/lib/components/HelpCenterFooter.js.map +1 -1
- package/lib/components/HelpCenterHeader.d.ts +1 -5
- package/lib/components/HelpCenterHeader.d.ts.map +1 -1
- package/lib/components/HelpCenterHeader.js +67 -69
- package/lib/components/HelpCenterHeader.js.map +1 -1
- package/lib/components/Logo.d.ts.map +1 -1
- package/lib/components/Logo.js +3 -2
- package/lib/components/Logo.js.map +1 -1
- package/lib/components/SearchBar.d.ts +8 -0
- package/lib/components/SearchBar.d.ts.map +1 -0
- package/lib/components/SearchBar.js +234 -0
- package/lib/components/SearchBar.js.map +1 -0
- package/lib/components/SidebarSearch.d.ts +8 -0
- package/lib/components/SidebarSearch.d.ts.map +1 -0
- package/lib/components/SidebarSearch.js +114 -0
- package/lib/components/SidebarSearch.js.map +1 -0
- package/lib/components/navbar/index.d.ts.map +1 -1
- package/lib/components/navbar/index.js +5 -4
- package/lib/components/navbar/index.js.map +1 -1
- package/lib/compute.d.ts.map +1 -1
- package/lib/compute.js +19 -1
- package/lib/compute.js.map +1 -1
- package/lib/pages/CategoryCollection/index.d.ts.map +1 -1
- package/lib/pages/CategoryCollection/index.js +5 -11
- package/lib/pages/CategoryCollection/index.js.map +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 +106 -37
- 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/pages/LandingPage/components/HeroSection.d.ts +0 -1
- package/lib/pages/LandingPage/components/HeroSection.d.ts.map +1 -1
- package/lib/pages/LandingPage/components/HeroSection.js +3 -6
- package/lib/pages/LandingPage/components/HeroSection.js.map +1 -1
- package/lib/pages/LandingPage/index.d.ts.map +1 -1
- package/lib/pages/LandingPage/index.js +1 -6
- package/lib/pages/LandingPage/index.js.map +1 -1
- package/lib/pages/Markdown/MarkdownPageLayout.d.ts +3 -0
- package/lib/pages/Markdown/MarkdownPageLayout.d.ts.map +1 -0
- package/lib/pages/Markdown/MarkdownPageLayout.js +314 -0
- package/lib/pages/Markdown/MarkdownPageLayout.js.map +1 -0
- package/lib/pages/Markdown/MarkdownPageWithParams.d.ts +9 -0
- package/lib/pages/Markdown/MarkdownPageWithParams.d.ts.map +1 -0
- package/lib/pages/Markdown/MarkdownPageWithParams.js +65 -0
- package/lib/pages/Markdown/MarkdownPageWithParams.js.map +1 -0
- package/lib/pages/Markdown/index.d.ts +3 -0
- package/lib/pages/Markdown/index.d.ts.map +1 -0
- package/lib/pages/Markdown/index.js +5 -0
- package/lib/pages/Markdown/index.js.map +1 -0
- package/lib/routes.json +28 -1
- package/lib/{content → templates/content}/account-management/account-setup.md +10 -0
- package/lib/{content → templates/content}/account-management/delete-account.md +10 -0
- package/lib/{content → templates/content}/account-management/preferences.md +10 -0
- package/lib/{content → templates/content}/account-management/privacy-settings.md +10 -0
- package/lib/{content → templates/content}/account-management/profile-settings.md +8 -0
- 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 +5670 -0
- package/lib/{content → templates/content}/data-privacy/data-collection.md +9 -0
- package/lib/{content → templates/content}/data-privacy/privacy-policy.md +10 -0
- package/lib/{content → templates/content}/data-subject-privacy/data-access.md +12 -0
- package/lib/{content → templates/content}/data-subject-privacy/data-portability.md +15 -0
- package/lib/{content → templates/content}/data-subject-privacy/privacy-requests.md +11 -0
- package/lib/{content → templates/content}/file-uploads/file-upload-overview.md +9 -0
- package/lib/{content → templates/content}/getting-started/getting-started-guide.md +9 -0
- 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/{content → templates/content}/product-features/ai-models.md +1 -1
- package/lib/{content → templates/content}/product-features/collaboration-tools.md +8 -0
- package/lib/{content → templates/content}/product-features/conversation-features.md +6 -0
- package/lib/{content → templates/content}/product-features/export-features.md +8 -0
- package/lib/{content → templates/content}/product-features/follow-up-questions.md +8 -0
- package/lib/{content → templates/content}/product-features/real-time-search.md +8 -0
- package/lib/{content → templates/content}/product-features/saved-searches.md +8 -0
- package/lib/{content → templates/content}/product-features/search-features.md +1 -1
- package/lib/{content → templates/content}/product-features/search-history.md +8 -0
- package/lib/{content → templates/content}/product-features/source-citations.md +8 -0
- package/lib/{content → templates/content}/scope-api/api-overview.md +8 -0
- package/lib/{content → templates/content}/search-modes/deep-research.md +8 -0
- package/lib/{content → templates/content}/search-modes/labs-features.md +10 -0
- package/lib/{content → templates/content}/search-modes/pro-search.md +8 -0
- package/lib/{content → templates/content}/search-modes/regular-search.md +8 -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/{content → templates/content}/spaces-library/spaces-overview.md +8 -0
- package/lib/{content → templates/content}/student-hub/academic-research.md +8 -0
- package/lib/{content → templates/content}/student-hub/student-discounts.md +10 -0
- package/lib/{content → templates/content}/student-hub/student-overview.md +8 -0
- package/lib/{content → templates/content}/student-hub/study-tools.md +8 -0
- package/lib/{content → templates/content}/subscription-billing/billing-cycle.md +8 -0
- package/lib/{content → templates/content}/subscription-billing/billing-overview.md +6 -0
- package/lib/{content → templates/content}/subscription-billing/billing-support.md +8 -0
- package/lib/{content → templates/content}/subscription-billing/currency-support.md +10 -0
- package/lib/{content → templates/content}/subscription-billing/enterprise-pricing.md +8 -0
- package/lib/{content → templates/content}/subscription-billing/invoice-management.md +8 -0
- package/lib/{content → templates/content}/subscription-billing/payment-methods.md +9 -0
- package/lib/{content → templates/content}/subscription-billing/promotional-offers.md +8 -0
- package/lib/{content → templates/content}/subscription-billing/refund-policy.md +10 -0
- package/lib/{content → templates/content}/subscription-billing/student-discounts.md +10 -0
- package/lib/{content → templates/content}/subscription-billing/tax-information.md +8 -0
- package/lib/{content → templates/content}/technical-questions/ai-models-technical.md +10 -0
- package/lib/{content → templates/content}/technical-questions/api-technical.md +10 -0
- package/lib/{content → templates/content}/technical-questions/data-processing.md +10 -0
- package/lib/{content → templates/content}/technical-questions/database-architecture.md +10 -0
- package/lib/{content → templates/content}/technical-questions/infrastructure.md +10 -0
- package/lib/{content → templates/content}/technical-questions/performance-optimization.md +10 -0
- package/lib/{content → templates/content}/technical-questions/search-algorithms.md +10 -0
- package/lib/{content → templates/content}/technical-questions/technical-overview.md +10 -0
- package/lib/{content → templates/content}/threads/conversation-management.md +8 -0
- package/lib/{content → templates/content}/threads/threads-overview.md +8 -0
- package/lib/{content → templates/content}/troubleshooting/common-issues.md +8 -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/lib/{content → templates/content}/what-is-yantra/getting-started-yantra.md +1 -1
- package/lib/{content → templates/content}/what-is-yantra/how-yantra-works.md +1 -1
- package/lib/{content → templates/content}/what-is-yantra/practical-tips-yantra.md +2 -1
- package/lib/{content → templates/content}/what-is-yantra/what-is-yantra-intro.md +1 -1
- package/lib/{content → templates/content}/what-is-yantra/yantra-discord-community.md +4 -1
- package/lib/{content → templates/content}/yantra-assistant/android-app.md +10 -0
- package/lib/{content → templates/content}/yantra-assistant/ios-app.md +10 -0
- package/lib/{content → templates/content}/yantra-assistant/mobile-app-overview.md +8 -0
- package/lib/{content → templates/content}/yantra-assistant/voice-assistant.md +10 -0
- package/lib/{content → templates/content}/yantra-enterprise/admin-dashboard.md +10 -0
- package/lib/{content → templates/content}/yantra-enterprise/custom-branding.md +10 -0
- package/lib/{content → templates/content}/yantra-enterprise/dedicated-support.md +10 -0
- package/lib/{content → templates/content}/yantra-enterprise/enterprise-overview.md +8 -0
- package/lib/{content → templates/content}/yantra-enterprise/sso-integration.md +10 -0
- package/lib/{content → templates/content}/yantra-enterprise/user-management.md +10 -0
- package/lib/{content → templates/content}/yantra-pro-max/billing-management.md +13 -0
- package/lib/{content → templates/content}/yantra-pro-max/cancellation-refund.md +13 -0
- package/lib/{content → templates/content}/yantra-pro-max/pro-pricing.md +13 -9
- package/lib/{content → templates/content}/yantra-pro-max/subscription-benefits.md +8 -0
- package/lib/{content → templates/content}/yantra-pro-max/upgrade-process.md +13 -0
- package/lib/{content → templates/content}/yantra-pro-max/yantra-max-features.md +8 -8
- package/lib/{content → templates/content}/yantra-pro-max/yantra-pro-overview.md +8 -8
- package/lib/utils/docsNavigation.d.ts +10 -0
- package/lib/utils/docsNavigation.d.ts.map +1 -0
- package/lib/utils/docsNavigation.js +151 -0
- package/lib/utils/docsNavigation.js.map +1 -0
- package/lib/utils/helpCenterUtils.d.ts.map +1 -1
- package/lib/utils/markdownLoader.d.ts +12 -4
- package/lib/utils/markdownLoader.d.ts.map +1 -1
- package/lib/utils/markdownLoader.js +362 -1163
- package/lib/utils/markdownLoader.js.map +1 -1
- package/package.json +23 -6
- package/lib/pages/ArticlePage/index.d.ts +0 -4
- package/lib/pages/ArticlePage/index.d.ts.map +0 -1
- package/lib/pages/ArticlePage/index.js +0 -190
- package/lib/pages/ArticlePage/index.js.map +0 -1
- package/lib/pages/HelpCenter/components/BookStack.js +0 -36
- package/lib/pages/HelpCenter/components/BookStack.js.map +0 -1
- package/lib/pages/LandingPage/components/SearchBar.d.ts +0 -8
- package/lib/pages/LandingPage/components/SearchBar.d.ts.map +0 -1
- package/lib/pages/LandingPage/components/SearchBar.js +0 -58
- package/lib/pages/LandingPage/components/SearchBar.js.map +0 -1
|
@@ -0,0 +1,120 @@
|
|
|
1
|
+
# Institutional Memory for Engineering
|
|
2
|
+
|
|
3
|
+
Yantra's AI employee acts as your team's permanent memory, capturing every technical decision, bug fix, workaround, and customer interaction so that knowledge is never lost.
|
|
4
|
+
|
|
5
|
+
## The Knowledge Loss Problem
|
|
6
|
+
|
|
7
|
+
Engineering teams face a critical knowledge management challenge:
|
|
8
|
+
|
|
9
|
+
- **67% of organizational context lives undocumented** — it exists only in people's heads
|
|
10
|
+
- When engineers leave or change teams, their knowledge goes with them
|
|
11
|
+
- Post-mortems are written but rarely referenced when similar issues recur
|
|
12
|
+
- Architectural decisions made 6 months ago have no discoverable rationale
|
|
13
|
+
- Customer-specific configurations and workarounds are tribal knowledge
|
|
14
|
+
|
|
15
|
+
## How Yantra Builds Institutional Memory
|
|
16
|
+
|
|
17
|
+
### Automatic Knowledge Capture
|
|
18
|
+
|
|
19
|
+
Your AI employee continuously indexes and correlates:
|
|
20
|
+
|
|
21
|
+
**From Slack/Teams**:
|
|
22
|
+
|
|
23
|
+
- Technical discussions and decisions
|
|
24
|
+
- Customer troubleshooting interactions
|
|
25
|
+
- Architecture debates and conclusions
|
|
26
|
+
- Workaround descriptions and temporary fixes
|
|
27
|
+
|
|
28
|
+
**From GitHub/GitLab**:
|
|
29
|
+
|
|
30
|
+
- PR descriptions and review comments explaining _why_ changes were made
|
|
31
|
+
- Commit messages linked to issue context
|
|
32
|
+
- Release notes and changelog entries
|
|
33
|
+
- Code ownership and expertise mapping
|
|
34
|
+
|
|
35
|
+
**From Issue Trackers**:
|
|
36
|
+
|
|
37
|
+
- Bug reports with full investigation trails
|
|
38
|
+
- Resolution steps and root cause analyses
|
|
39
|
+
- Customer impact assessments
|
|
40
|
+
- Priority decisions and escalation reasoning
|
|
41
|
+
|
|
42
|
+
**From Documents**:
|
|
43
|
+
|
|
44
|
+
- Architecture decision records (ADRs)
|
|
45
|
+
- Runbooks and operational procedures
|
|
46
|
+
- Post-mortems and incident reports
|
|
47
|
+
- Onboarding guides and training materials
|
|
48
|
+
|
|
49
|
+
### Knowledge Graph
|
|
50
|
+
|
|
51
|
+
All captured knowledge is organized into a **knowledge graph** that connects:
|
|
52
|
+
|
|
53
|
+
- **Issues** to the engineers who fixed them and the code that was changed
|
|
54
|
+
- **Customers** to their configurations, past issues, and special requirements
|
|
55
|
+
- **Services** to their owners, dependencies, and known failure modes
|
|
56
|
+
- **Decisions** to the reasoning, alternatives considered, and people involved
|
|
57
|
+
|
|
58
|
+
## Practical Applications
|
|
59
|
+
|
|
60
|
+
### Recurring Issue Detection
|
|
61
|
+
|
|
62
|
+
When a bug report matches a pattern seen before, the AI employee:
|
|
63
|
+
|
|
64
|
+
- Surfaces the previous incident and its resolution
|
|
65
|
+
- Identifies whether the original fix regressed or if this is a new variant
|
|
66
|
+
- Links to the relevant post-mortem or discussion thread
|
|
67
|
+
|
|
68
|
+
### Architecture Archaeology
|
|
69
|
+
|
|
70
|
+
When someone asks _"Why did we choose PostgreSQL for this service?"_ or _"What was the reasoning behind the microservice split?"_, the AI employee:
|
|
71
|
+
|
|
72
|
+
- Finds the original discussion (even if it happened in a Slack thread 18 months ago)
|
|
73
|
+
- Surfaces the alternatives that were considered
|
|
74
|
+
- Links to any benchmark results, ADRs, or design documents
|
|
75
|
+
|
|
76
|
+
### Customer Context Recall
|
|
77
|
+
|
|
78
|
+
When working on a customer-specific issue:
|
|
79
|
+
|
|
80
|
+
- Full history of that customer's interactions and issues
|
|
81
|
+
- Known configurations, customizations, and edge cases
|
|
82
|
+
- Previous workarounds applied and their outcomes
|
|
83
|
+
- Key contacts and their communication preferences
|
|
84
|
+
|
|
85
|
+
### Expertise Discovery
|
|
86
|
+
|
|
87
|
+
When facing an unfamiliar area of the codebase:
|
|
88
|
+
|
|
89
|
+
- Identifies the most active contributors for each module
|
|
90
|
+
- Surfaces who resolved similar issues in the past
|
|
91
|
+
- Recommends who to consult for specific technical domains
|
|
92
|
+
|
|
93
|
+
## Preventing Knowledge Silos
|
|
94
|
+
|
|
95
|
+
### Real-Time Cross-Pollination
|
|
96
|
+
|
|
97
|
+
When your AI employee detects that one team member has context relevant to another's work:
|
|
98
|
+
|
|
99
|
+
- Proactively shares the connection (e.g., _"Sarah fixed a similar auth issue for Globex last month — here's the thread"_)
|
|
100
|
+
- Suggests relevant documentation or past decisions
|
|
101
|
+
- Bridges communication gaps between team members working on related problems
|
|
102
|
+
|
|
103
|
+
### Departure Protection
|
|
104
|
+
|
|
105
|
+
When team members transition or leave:
|
|
106
|
+
|
|
107
|
+
- Their accumulated knowledge remains fully accessible through the AI employee
|
|
108
|
+
- No handoff documentation gap — the AI employee already has everything indexed
|
|
109
|
+
- New team members can query the AI employee for any context the departing engineer held
|
|
110
|
+
|
|
111
|
+
## Getting Started with Institutional Memory
|
|
112
|
+
|
|
113
|
+
Institutional memory builds automatically from the moment you connect your tools:
|
|
114
|
+
|
|
115
|
+
1. **Immediate**: Access to all content in connected tools (messages, issues, PRs)
|
|
116
|
+
2. **Within days**: Cross-tool correlations begin surfacing connections
|
|
117
|
+
3. **Within weeks**: Pattern recognition enables proactive knowledge surfacing
|
|
118
|
+
4. **Ongoing**: Knowledge graph deepens continuously, becoming more valuable over time
|
|
119
|
+
|
|
120
|
+
The longer Yantra is connected, the richer and more useful its institutional memory becomes.
|
|
@@ -0,0 +1,135 @@
|
|
|
1
|
+
# Brand Monitoring and Sentiment Tracking
|
|
2
|
+
|
|
3
|
+
Yantra's AI employee monitors your brand's presence across social media and the web, tracking mentions, analyzing sentiment, and surfacing opportunities for engagement.
|
|
4
|
+
|
|
5
|
+
## Why Brand Monitoring Matters
|
|
6
|
+
|
|
7
|
+
Your brand is being discussed whether you're listening or not:
|
|
8
|
+
|
|
9
|
+
- Customer feedback on social media that never reaches your support team
|
|
10
|
+
- Industry discussions where your product could be recommended
|
|
11
|
+
- Competitor comparisons that shape prospect perception
|
|
12
|
+
- Influencer mentions that create engagement opportunities and credibility
|
|
13
|
+
|
|
14
|
+
Without systematic monitoring, these conversations happen without your awareness or participation.
|
|
15
|
+
|
|
16
|
+
## How Yantra Monitors Your Brand
|
|
17
|
+
|
|
18
|
+
### Multi-Platform Tracking
|
|
19
|
+
|
|
20
|
+
Your AI employee monitors for brand-relevant activity across:
|
|
21
|
+
|
|
22
|
+
- **LinkedIn**: Posts mentioning your company, product, or key individuals
|
|
23
|
+
- **X/Twitter**: Tweets, replies, and threads referencing your brand
|
|
24
|
+
- **Web**: Blog posts, forum discussions, and review sites
|
|
25
|
+
- **Slack Communities**: Public Slack workspaces relevant to your industry
|
|
26
|
+
- **Reddit**: Subreddit discussions mentioning your product or category
|
|
27
|
+
|
|
28
|
+
### Mention Classification
|
|
29
|
+
|
|
30
|
+
Each detected mention is classified by:
|
|
31
|
+
|
|
32
|
+
| Category | Description | Action |
|
|
33
|
+
| -------------- | ----------------------------------------------- | ----------------------- |
|
|
34
|
+
| **Positive** | Praise, recommendations, success stories | Thank and amplify |
|
|
35
|
+
| **Neutral** | Informational references, comparisons | Monitor for opportunity |
|
|
36
|
+
| **Negative** | Complaints, criticism, issues | Address proactively |
|
|
37
|
+
| **Question** | Inquiries about your product or capabilities | Respond helpfully |
|
|
38
|
+
| **Competitor** | Comparison discussions, competitive positioning | Engage strategically |
|
|
39
|
+
|
|
40
|
+
### Sentiment Analysis
|
|
41
|
+
|
|
42
|
+
Beyond individual mentions, your AI employee tracks aggregate sentiment:
|
|
43
|
+
|
|
44
|
+
- Overall sentiment score trending over time
|
|
45
|
+
- Sentiment breakdown by topic (product quality, support, pricing, etc.)
|
|
46
|
+
- Sentiment shifts correlated with your activities (launches, outages, announcements)
|
|
47
|
+
- Comparative sentiment against competitors
|
|
48
|
+
|
|
49
|
+
## Proactive Engagement Opportunities
|
|
50
|
+
|
|
51
|
+
### Influencer Interaction
|
|
52
|
+
|
|
53
|
+
When someone with significant reach engages with your content or mentions your brand:
|
|
54
|
+
|
|
55
|
+
- Immediate notification with their profile context
|
|
56
|
+
- Draft response tailored to the interaction
|
|
57
|
+
- Priority flagging for rapid human review
|
|
58
|
+
|
|
59
|
+
### Thread Participation
|
|
60
|
+
|
|
61
|
+
When relevant discussions happen in your industry:
|
|
62
|
+
|
|
63
|
+
- AI employee identifies threads where your expertise adds value
|
|
64
|
+
- Drafts helpful, non-promotional responses
|
|
65
|
+
- Flags opportunities to demonstrate thought leadership
|
|
66
|
+
|
|
67
|
+
### Customer Feedback Routing
|
|
68
|
+
|
|
69
|
+
When customers share feedback publicly:
|
|
70
|
+
|
|
71
|
+
- Positive feedback is tagged for marketing amplification
|
|
72
|
+
- Feature requests are routed to product teams
|
|
73
|
+
- Issues are linked to support tickets and engineering context
|
|
74
|
+
- Response drafts address both the public conversation and internal follow-up
|
|
75
|
+
|
|
76
|
+
## Competitive Intelligence
|
|
77
|
+
|
|
78
|
+
### Competitor Monitoring
|
|
79
|
+
|
|
80
|
+
Your AI employee tracks competitor activity including:
|
|
81
|
+
|
|
82
|
+
- Product announcements and feature releases
|
|
83
|
+
- Pricing changes and promotional campaigns
|
|
84
|
+
- Social media strategy and engagement patterns
|
|
85
|
+
- Market positioning shifts and messaging changes
|
|
86
|
+
|
|
87
|
+
### Competitive Response Support
|
|
88
|
+
|
|
89
|
+
When competitor activity requires a response:
|
|
90
|
+
|
|
91
|
+
- Summary of what the competitor did and potential impact
|
|
92
|
+
- Analysis of how it affects your positioning
|
|
93
|
+
- Suggested messaging adjustments or content responses
|
|
94
|
+
- Historical context on competitive dynamics
|
|
95
|
+
|
|
96
|
+
## Reporting
|
|
97
|
+
|
|
98
|
+
### Weekly Brand Health Report
|
|
99
|
+
|
|
100
|
+
- Total mentions and trend direction
|
|
101
|
+
- Sentiment score and breakdown
|
|
102
|
+
- Top positive and negative mentions
|
|
103
|
+
- Engagement opportunities acted on or missed
|
|
104
|
+
- Competitive activity summary
|
|
105
|
+
|
|
106
|
+
### Real-Time Alerts
|
|
107
|
+
|
|
108
|
+
- Significant sentiment shifts (positive or negative)
|
|
109
|
+
- High-profile mentions requiring immediate attention
|
|
110
|
+
- Viral content referencing your brand
|
|
111
|
+
- Crisis indicators (sudden spike in negative mentions)
|
|
112
|
+
|
|
113
|
+
## Configuration
|
|
114
|
+
|
|
115
|
+
### Monitoring Scope
|
|
116
|
+
|
|
117
|
+
- Brand name variations and common misspellings
|
|
118
|
+
- Product names and features
|
|
119
|
+
- Key team members and executives
|
|
120
|
+
- Industry keywords and hashtags
|
|
121
|
+
- Competitor names and products
|
|
122
|
+
|
|
123
|
+
### Alert Thresholds
|
|
124
|
+
|
|
125
|
+
- Mention volume changes that trigger alerts
|
|
126
|
+
- Sentiment drop thresholds for immediate notification
|
|
127
|
+
- Influencer follower count minimum for priority flagging
|
|
128
|
+
- Geographic or language filters
|
|
129
|
+
|
|
130
|
+
### Response Guidelines
|
|
131
|
+
|
|
132
|
+
- Approved messaging for common mention types
|
|
133
|
+
- Escalation rules for sensitive topics
|
|
134
|
+
- Tone guidelines for different platforms
|
|
135
|
+
- Topics where human review is always required
|
|
@@ -0,0 +1,111 @@
|
|
|
1
|
+
# Content Automation
|
|
2
|
+
|
|
3
|
+
Yantra's AI employee transforms internal company activity into external-facing content, ensuring every product update, milestone, and insight is amplified without manual effort.
|
|
4
|
+
|
|
5
|
+
## From Internal Events to Published Content
|
|
6
|
+
|
|
7
|
+
### Automated Content Pipeline
|
|
8
|
+
|
|
9
|
+
Your AI employee watches for content-worthy events across your organization:
|
|
10
|
+
|
|
11
|
+
```
|
|
12
|
+
Internal Event → Content Draft → Review → Publish → Performance Tracking
|
|
13
|
+
```
|
|
14
|
+
|
|
15
|
+
**Event Types That Trigger Content**:
|
|
16
|
+
|
|
17
|
+
- New feature releases (detected from GitHub releases or Slack announcements)
|
|
18
|
+
- Product updates and improvements
|
|
19
|
+
- Team milestones and achievements
|
|
20
|
+
- Customer success stories shared in internal channels
|
|
21
|
+
- Industry conference participation
|
|
22
|
+
- Hiring milestones ("We're now 50 people!")
|
|
23
|
+
- Partnership announcements
|
|
24
|
+
|
|
25
|
+
### Content Transformation
|
|
26
|
+
|
|
27
|
+
For each detected event, your AI employee generates platform-appropriate content:
|
|
28
|
+
|
|
29
|
+
| Event | LinkedIn | X/Twitter |
|
|
30
|
+
| ------------------- | ------------------------------------------ | ------------------------------------ |
|
|
31
|
+
| Feature release | Detailed post explaining value proposition | Punchy announcement + feature thread |
|
|
32
|
+
| Customer milestone | Case study teaser with link | Quote + congratulatory mention |
|
|
33
|
+
| Blog post published | Summary with key takeaways | Thread breaking down main points |
|
|
34
|
+
| Company update | Professional announcement | Quick update with personality |
|
|
35
|
+
|
|
36
|
+
## Content Calendar Management
|
|
37
|
+
|
|
38
|
+
### Automated Scheduling
|
|
39
|
+
|
|
40
|
+
Your AI employee maintains a content calendar that:
|
|
41
|
+
|
|
42
|
+
- Balances content types (product, thought leadership, engagement, culture)
|
|
43
|
+
- Ensures consistent posting frequency
|
|
44
|
+
- Avoids scheduling conflicts and content fatigue
|
|
45
|
+
- Fills gaps with evergreen or repurposed content
|
|
46
|
+
|
|
47
|
+
### Editorial Awareness
|
|
48
|
+
|
|
49
|
+
The AI employee considers:
|
|
50
|
+
|
|
51
|
+
- Upcoming product launches (ramp up anticipation content)
|
|
52
|
+
- Industry events and conferences (pre, during, and post coverage)
|
|
53
|
+
- Seasonal trends relevant to your audience
|
|
54
|
+
- Current news cycle (avoid posting during sensitive events)
|
|
55
|
+
|
|
56
|
+
## Multi-Format Content Generation
|
|
57
|
+
|
|
58
|
+
### Short-Form Content
|
|
59
|
+
|
|
60
|
+
- Social media posts (LinkedIn, X/Twitter)
|
|
61
|
+
- Slack community updates
|
|
62
|
+
- Email newsletter snippets
|
|
63
|
+
- Release notification messages
|
|
64
|
+
|
|
65
|
+
### Long-Form Content Outlines
|
|
66
|
+
|
|
67
|
+
For significant updates, your AI employee can draft:
|
|
68
|
+
|
|
69
|
+
- Blog post outlines with key points and structure
|
|
70
|
+
- Case study frameworks with data points to fill in
|
|
71
|
+
- Product announcement templates
|
|
72
|
+
- Changelog entries with feature descriptions
|
|
73
|
+
|
|
74
|
+
### Visual Content Support
|
|
75
|
+
|
|
76
|
+
Your AI employee prepares supporting elements:
|
|
77
|
+
|
|
78
|
+
- Suggested headline and subheading copy
|
|
79
|
+
- Key statistics and data points formatted for graphics
|
|
80
|
+
- Quote snippets from customer conversations (with appropriate anonymization)
|
|
81
|
+
- Feature comparison tables for product-focused content
|
|
82
|
+
|
|
83
|
+
## Performance Feedback Loop
|
|
84
|
+
|
|
85
|
+
After content is published, your AI employee:
|
|
86
|
+
|
|
87
|
+
1. Tracks engagement metrics over 48 hours
|
|
88
|
+
2. Compares performance against your average benchmarks
|
|
89
|
+
3. Identifies what made high-performing content successful
|
|
90
|
+
4. Adjusts future content strategy based on patterns
|
|
91
|
+
5. Reports weekly content performance summaries
|
|
92
|
+
|
|
93
|
+
## Configuration
|
|
94
|
+
|
|
95
|
+
### Content Triggers
|
|
96
|
+
|
|
97
|
+
- Define which internal events should generate content
|
|
98
|
+
- Set sensitivity levels (major releases only, or every update)
|
|
99
|
+
- Configure which team channels to monitor for content-worthy events
|
|
100
|
+
|
|
101
|
+
### Voice and Style
|
|
102
|
+
|
|
103
|
+
- Upload brand guidelines or sample posts for voice calibration
|
|
104
|
+
- Define platform-specific style variations
|
|
105
|
+
- Set formatting preferences (emojis, hashtags, mention style)
|
|
106
|
+
|
|
107
|
+
### Approval Levels
|
|
108
|
+
|
|
109
|
+
- All content requires review (supervised)
|
|
110
|
+
- Routine content auto-publishes, novel content requires review (semi-autonomous)
|
|
111
|
+
- All content auto-publishes with post-publication reporting (autonomous)
|
|
@@ -0,0 +1,108 @@
|
|
|
1
|
+
# Marketing Solutions Overview
|
|
2
|
+
|
|
3
|
+
Yantra provides marketing teams with an AI employee that manages your social media presence, drafts content from product updates, monitors brand mentions, and maintains consistent engagement — all in your brand voice.
|
|
4
|
+
|
|
5
|
+
## The Marketing Challenge
|
|
6
|
+
|
|
7
|
+
Marketing teams are expected to maintain a consistent presence across multiple channels while also:
|
|
8
|
+
|
|
9
|
+
- Creating engaging content regularly
|
|
10
|
+
- Responding to audience engagement in a timely manner
|
|
11
|
+
- Tracking brand mentions and sentiment across the web
|
|
12
|
+
- Coordinating messaging with product launches and company updates
|
|
13
|
+
- Measuring performance and adjusting strategy
|
|
14
|
+
|
|
15
|
+
The result is that social media often falls off the priority list, engagement opportunities are missed, and product updates ship without marketing amplification.
|
|
16
|
+
|
|
17
|
+
## Key Capabilities for Marketing
|
|
18
|
+
|
|
19
|
+
### Content Automation
|
|
20
|
+
|
|
21
|
+
Your AI employee monitors internal channels for content opportunities:
|
|
22
|
+
|
|
23
|
+
- **Product launches**: Automatically drafts announcements when new features ship
|
|
24
|
+
- **Company updates**: Turns internal news into external-facing posts
|
|
25
|
+
- **Industry trends**: Surfaces relevant topics for thought leadership content
|
|
26
|
+
- **Repurposing**: Transforms long-form content into social-friendly formats
|
|
27
|
+
|
|
28
|
+
### Social Media Management
|
|
29
|
+
|
|
30
|
+
Maintain a consistent presence without constant manual effort:
|
|
31
|
+
|
|
32
|
+
- **Post drafting**: Creates platform-specific content (LinkedIn, X/Twitter) in your brand voice
|
|
33
|
+
- **Scheduling**: Posts at optimal engagement times based on your audience data
|
|
34
|
+
- **Thread creation**: Converts insights and updates into engaging multi-post threads
|
|
35
|
+
- **Hashtag optimization**: Selects relevant hashtags based on current trends and your niche
|
|
36
|
+
|
|
37
|
+
### Engagement Monitoring and Response
|
|
38
|
+
|
|
39
|
+
Never miss an engagement opportunity:
|
|
40
|
+
|
|
41
|
+
- **Real-time monitoring**: Watches for comments, mentions, and shares across platforms
|
|
42
|
+
- **Draft replies**: Creates contextually appropriate responses to engagement
|
|
43
|
+
- **Influencer flagging**: Identifies when high-value individuals interact with your content
|
|
44
|
+
- **Conversation surfacing**: Highlights discussions where your brand could add value
|
|
45
|
+
|
|
46
|
+
### Brand Monitoring
|
|
47
|
+
|
|
48
|
+
Stay aware of how your brand is perceived:
|
|
49
|
+
|
|
50
|
+
- **Mention tracking**: Monitors brand mentions across social media and web
|
|
51
|
+
- **Sentiment analysis**: Tracks whether mentions are positive, neutral, or negative
|
|
52
|
+
- **Competitor monitoring**: Watches competitor activity and positioning
|
|
53
|
+
- **Trend alerts**: Notifies you when sentiment shifts or mention volume changes
|
|
54
|
+
|
|
55
|
+
## Real-World Scenarios
|
|
56
|
+
|
|
57
|
+
### Scenario: Product Feature Ships Without Fanfare
|
|
58
|
+
|
|
59
|
+
**Without Yantra**:
|
|
60
|
+
Engineering shipped a great feature last week. You planned to write about it but got pulled into other priorities. Two weeks later, it's old news.
|
|
61
|
+
|
|
62
|
+
**With Yantra**:
|
|
63
|
+
Your AI employee detected the release in GitHub/Slack, drafted a LinkedIn post and X thread, and sent them for your review the same day. The content was published at peak engagement time.
|
|
64
|
+
|
|
65
|
+
### Scenario: Missed Engagement from an Industry Leader
|
|
66
|
+
|
|
67
|
+
**Without Yantra**:
|
|
68
|
+
An influential industry leader commented on your post. You saw it 3 days later. The conversation window had closed.
|
|
69
|
+
|
|
70
|
+
**With Yantra**:
|
|
71
|
+
Your AI employee flagged the interaction within minutes, drafted a thoughtful reply, and alerted you via Slack. You reviewed and posted within the hour.
|
|
72
|
+
|
|
73
|
+
### Scenario: Competitor Mentions After a Product Launch
|
|
74
|
+
|
|
75
|
+
**Without Yantra**:
|
|
76
|
+
A competitor launched a feature similar to yours. People are discussing it on social media, some comparing it unfavorably to your product. You find out from a coworker a week later.
|
|
77
|
+
|
|
78
|
+
**With Yantra**:
|
|
79
|
+
Your AI employee detected the competitor launch, tracked social media discussions, and sent you a summary with relevant conversation links and suggested responses.
|
|
80
|
+
|
|
81
|
+
### Scenario: Content Calendar Falls Behind
|
|
82
|
+
|
|
83
|
+
**Without Yantra**:
|
|
84
|
+
You meant to post regularly but your last LinkedIn update was 3 weeks ago. Engagement has dropped and followers have stalled.
|
|
85
|
+
|
|
86
|
+
**With Yantra**:
|
|
87
|
+
Your AI employee maintains a consistent posting cadence based on internal updates, industry news, and repurposed content — drafting posts for your review on a regular schedule.
|
|
88
|
+
|
|
89
|
+
## Marketing Tool Integrations
|
|
90
|
+
|
|
91
|
+
| Tool | Capabilities |
|
|
92
|
+
| -------------------- | --------------------------------------------------------------- |
|
|
93
|
+
| **LinkedIn** | Draft and schedule posts, respond to comments, track engagement |
|
|
94
|
+
| **X/Twitter** | Create threads, monitor mentions, manage replies |
|
|
95
|
+
| **Slack** | Surface marketing-relevant discussions, coordinate messaging |
|
|
96
|
+
| **Notion** | Pull content ideas from internal documentation and updates |
|
|
97
|
+
| **HubSpot** | Sync marketing contacts, campaign coordination |
|
|
98
|
+
| **Google Analytics** | Surface performance insights, track content impact |
|
|
99
|
+
|
|
100
|
+
## Getting Started
|
|
101
|
+
|
|
102
|
+
1. Connect your marketing tools via [Integrations](/help-center/integrations/integrations-overview)
|
|
103
|
+
2. Select "Marketing" as your AI employee type during setup
|
|
104
|
+
3. Define your brand voice guidelines and content preferences
|
|
105
|
+
4. Configure posting cadence and engagement monitoring rules
|
|
106
|
+
5. Start in supervised mode — review all content drafts before publishing
|
|
107
|
+
|
|
108
|
+
For setup details, see [Getting Started with AI Employees](/help-center/ai-employees/getting-started-ai-employees).
|
|
@@ -0,0 +1,108 @@
|
|
|
1
|
+
# Social Media Management
|
|
2
|
+
|
|
3
|
+
Yantra's AI employee maintains your organization's social media presence across LinkedIn and X/Twitter — drafting posts, scheduling content, and managing engagement so your brand stays active and visible.
|
|
4
|
+
|
|
5
|
+
## Consistent Publishing Without the Effort
|
|
6
|
+
|
|
7
|
+
### Content Drafting
|
|
8
|
+
|
|
9
|
+
Your AI employee generates social media content from multiple sources:
|
|
10
|
+
|
|
11
|
+
**Internal Updates**:
|
|
12
|
+
|
|
13
|
+
- Product releases detected in GitHub or Slack announcements
|
|
14
|
+
- Company milestones and team achievements
|
|
15
|
+
- Blog posts and documentation updates
|
|
16
|
+
- Customer success stories shared internally
|
|
17
|
+
|
|
18
|
+
**Industry Intelligence**:
|
|
19
|
+
|
|
20
|
+
- Trending topics in your space
|
|
21
|
+
- Relevant news and developments
|
|
22
|
+
- Thought leadership opportunities
|
|
23
|
+
- Event and conference coverage
|
|
24
|
+
|
|
25
|
+
**Content Repurposing**:
|
|
26
|
+
|
|
27
|
+
- Blog post summaries transformed into social posts
|
|
28
|
+
- Key statistics extracted and formatted as standalone content
|
|
29
|
+
- Long-form content broken into thread-friendly segments
|
|
30
|
+
- Customer testimonials adapted for social sharing
|
|
31
|
+
|
|
32
|
+
### Brand Voice Calibration
|
|
33
|
+
|
|
34
|
+
During setup, you define your brand voice parameters:
|
|
35
|
+
|
|
36
|
+
- **Tone**: Professional, conversational, technical, approachable
|
|
37
|
+
- **Vocabulary**: Preferred terms, industry-specific language, words to avoid
|
|
38
|
+
- **Style**: Post length preferences, emoji usage, formatting conventions
|
|
39
|
+
- **Personality**: How your brand "sounds" in social media interactions
|
|
40
|
+
|
|
41
|
+
Your AI employee learns from the posts you approve and edit, continuously refining its writing to match your voice.
|
|
42
|
+
|
|
43
|
+
### Optimal Scheduling
|
|
44
|
+
|
|
45
|
+
Posts are scheduled based on:
|
|
46
|
+
|
|
47
|
+
- Historical engagement data for your specific audience
|
|
48
|
+
- Platform-specific peak activity windows
|
|
49
|
+
- Content type and expected engagement patterns
|
|
50
|
+
- Calendar awareness (avoiding holidays, competitor events, or internal quiet periods)
|
|
51
|
+
|
|
52
|
+
## Platform-Specific Content
|
|
53
|
+
|
|
54
|
+
### LinkedIn
|
|
55
|
+
|
|
56
|
+
- Professional long-form posts with engaging hooks
|
|
57
|
+
- Article summaries with personal commentary
|
|
58
|
+
- Company update announcements
|
|
59
|
+
- Job posting amplification
|
|
60
|
+
- Industry thought leadership pieces
|
|
61
|
+
|
|
62
|
+
### X/Twitter
|
|
63
|
+
|
|
64
|
+
- Concise, punchy updates
|
|
65
|
+
- Multi-tweet threads for complex topics
|
|
66
|
+
- Quote tweets with added context
|
|
67
|
+
- Reply threads for community engagement
|
|
68
|
+
- Timely reactions to trending discussions
|
|
69
|
+
|
|
70
|
+
## Content Approval Workflow
|
|
71
|
+
|
|
72
|
+
1. AI employee drafts content based on triggers or calendar cadence
|
|
73
|
+
2. Draft is sent to your Slack or email for review
|
|
74
|
+
3. You can: **Approve**, **Edit and Approve**, **Reject**, or **Schedule for Later**
|
|
75
|
+
4. Approved content is published or queued for the optimal posting time
|
|
76
|
+
5. AI employee tracks performance and learns from engagement data
|
|
77
|
+
|
|
78
|
+
## Engagement Analytics
|
|
79
|
+
|
|
80
|
+
Track the impact of your social media activity:
|
|
81
|
+
|
|
82
|
+
- Post-by-post engagement metrics (likes, comments, shares, clicks)
|
|
83
|
+
- Follower growth trends correlated with content types
|
|
84
|
+
- Best-performing content formats and topics
|
|
85
|
+
- Optimal posting times for your audience
|
|
86
|
+
- Month-over-month engagement trends
|
|
87
|
+
|
|
88
|
+
## Configuration
|
|
89
|
+
|
|
90
|
+
### Posting Cadence
|
|
91
|
+
|
|
92
|
+
- Define minimum and maximum posts per week per platform
|
|
93
|
+
- Set preferred posting days and times
|
|
94
|
+
- Configure approval deadlines (auto-post if not reviewed by X hours)
|
|
95
|
+
|
|
96
|
+
### Content Sources
|
|
97
|
+
|
|
98
|
+
- Select which internal channels to monitor for content triggers
|
|
99
|
+
- Define keyword lists for industry trend monitoring
|
|
100
|
+
- Set up RSS feeds for news monitoring
|
|
101
|
+
- Configure content repurposing rules
|
|
102
|
+
|
|
103
|
+
### Quality Controls
|
|
104
|
+
|
|
105
|
+
- Minimum review requirements before publishing
|
|
106
|
+
- Compliance check rules (regulated industries)
|
|
107
|
+
- Link verification and preview validation
|
|
108
|
+
- Duplicate content detection
|
|
@@ -0,0 +1,106 @@
|
|
|
1
|
+
# Call Preparation and Pipeline Intelligence
|
|
2
|
+
|
|
3
|
+
Yantra's AI employee ensures you're never underprepared for a sales call and provides real-time pipeline intelligence for accurate forecasting.
|
|
4
|
+
|
|
5
|
+
## Pre-Call Preparation
|
|
6
|
+
|
|
7
|
+
### Automatic Call Briefs
|
|
8
|
+
|
|
9
|
+
Before every scheduled meeting, your AI employee delivers a comprehensive brief:
|
|
10
|
+
|
|
11
|
+
**Meeting Context**:
|
|
12
|
+
|
|
13
|
+
- Attendees and their roles, extracted from calendar and CRM
|
|
14
|
+
- LinkedIn summary and recent activity for new contacts
|
|
15
|
+
- Relationship map showing previous interactions across your organization
|
|
16
|
+
|
|
17
|
+
**Deal History**:
|
|
18
|
+
|
|
19
|
+
- Current deal stage and how long it's been at this stage
|
|
20
|
+
- Revenue amount and any changes since last discussion
|
|
21
|
+
- Full timeline of interactions: calls, emails, meetings, and internal discussions
|
|
22
|
+
|
|
23
|
+
**Key Points**:
|
|
24
|
+
|
|
25
|
+
- Summary of the last conversation and what was discussed
|
|
26
|
+
- Open action items and commitments from both sides
|
|
27
|
+
- Objections raised previously and how they were addressed
|
|
28
|
+
- Questions the prospect asked that remain unanswered
|
|
29
|
+
|
|
30
|
+
**Suggested Approach**:
|
|
31
|
+
|
|
32
|
+
- Recommended talking points based on deal stage and past interactions
|
|
33
|
+
- Potential objections to prepare for
|
|
34
|
+
- References to similar deals that closed successfully
|
|
35
|
+
- Relevant product updates or features since the last conversation
|
|
36
|
+
|
|
37
|
+
### Brief Delivery
|
|
38
|
+
|
|
39
|
+
- Delivered 30 minutes before the call to your preferred channel
|
|
40
|
+
- Available on demand by asking your AI employee about any contact or deal
|
|
41
|
+
- Formatted for quick scanning with linked details for deeper reading
|
|
42
|
+
|
|
43
|
+
## Pipeline Intelligence
|
|
44
|
+
|
|
45
|
+
### Real-Time Pipeline Health
|
|
46
|
+
|
|
47
|
+
With CRM data continuously updated by your AI employee, pipeline metrics are always accurate:
|
|
48
|
+
|
|
49
|
+
**Pipeline Dashboard Insights**:
|
|
50
|
+
|
|
51
|
+
- Total pipeline value by stage
|
|
52
|
+
- Average time in each stage vs. historical benchmarks
|
|
53
|
+
- Conversion rates between stages
|
|
54
|
+
- Velocity trends over time
|
|
55
|
+
|
|
56
|
+
### At-Risk Deal Detection
|
|
57
|
+
|
|
58
|
+
Your AI employee proactively identifies deals at risk based on:
|
|
59
|
+
|
|
60
|
+
- **Engagement decline**: Decreasing response rates or longer response times
|
|
61
|
+
- **Stalled progression**: Deals sitting in a stage longer than your average
|
|
62
|
+
- **Competitor signals**: Mentions of competitors in conversations
|
|
63
|
+
- **Champion changes**: Decision-maker turnover at the prospect's organization
|
|
64
|
+
- **Delayed commitments**: Promises that aren't being fulfilled on schedule
|
|
65
|
+
|
|
66
|
+
When a deal is flagged at-risk, you receive:
|
|
67
|
+
|
|
68
|
+
- The specific risk signals detected
|
|
69
|
+
- Suggested intervention actions
|
|
70
|
+
- Context from similar past deals (won and lost) for comparison
|
|
71
|
+
|
|
72
|
+
### Forecasting Support
|
|
73
|
+
|
|
74
|
+
Your AI employee contributes to more accurate forecasting by:
|
|
75
|
+
|
|
76
|
+
- Ensuring deal stages reflect actual progress (not wishful thinking)
|
|
77
|
+
- Providing confidence scores for each deal based on engagement patterns
|
|
78
|
+
- Identifying deals likely to slip from the current quarter
|
|
79
|
+
- Tracking verbal commitments and their follow-through rate
|
|
80
|
+
|
|
81
|
+
### Win/Loss Intelligence
|
|
82
|
+
|
|
83
|
+
After deals close (won or lost), your AI employee compiles insights:
|
|
84
|
+
|
|
85
|
+
- What worked well in won deals
|
|
86
|
+
- Where lost deals diverged from winners
|
|
87
|
+
- Competitive patterns and positioning effectiveness
|
|
88
|
+
- Pricing sensitivity data across segments
|
|
89
|
+
|
|
90
|
+
## Post-Call Automation
|
|
91
|
+
|
|
92
|
+
After a sales call ends, your AI employee handles the aftermath:
|
|
93
|
+
|
|
94
|
+
1. **Note capture**: From Zoom transcription or your manual notes
|
|
95
|
+
2. **CRM update**: Key points, outcomes, and next steps logged
|
|
96
|
+
3. **Action items**: Tasks created for promised follow-ups and deliverables
|
|
97
|
+
4. **Email draft**: Recap email drafted with meeting summary and next steps
|
|
98
|
+
5. **Internal update**: Summary shared in relevant Slack channels
|
|
99
|
+
|
|
100
|
+
## Getting Started
|
|
101
|
+
|
|
102
|
+
1. Connect calendar, CRM, and communication tools
|
|
103
|
+
2. Configure brief delivery timing and format preferences
|
|
104
|
+
3. Set at-risk deal thresholds and pipeline health criteria
|
|
105
|
+
4. Enable post-call automation in supervised mode
|
|
106
|
+
5. Review and expand as confidence builds
|