sales-balto

Name: sales-balto
Author: sales-skills

86stars9forks

How to install sales-balto?

sales-skills/sales/sales-balto

$npx -y skills add sales-skills/sales --skill sales-balto

Installs into the current project.

Summary

Balto platform help — contact center real-time AI guidance with live call coaching, automated QA on 100% of calls, compliance monitoring, and automatic call summarization to CRM. Use when agents aren't following compliance scripts and you need real-time enforcement, QA team is on

Files · 1

View on GitHub

SKILL.md

1	# Balto Platform Help
2
3	## Step 1 — Gather context
4
5	If `references/learnings.md` exists, read it first for accumulated platform knowledge.
6
7	1. What do you need help with?
8	- A) Real-Time Guidance setup (dynamic prompts, checklists, objection handling)
9	- B) Real-Time QA configuration (automated scoring, compliance checks)
10	- C) Coaching workflows (coachable moments, manager alerts)
11	- D) Compliance monitoring (PCI, HIPAA, regulatory scanning)
12	- E) Integrations (CCaaS, CRM, softphone)
13	- F) Balto Notes (automatic call summarization to CRM)
14	- G) Comparing Balto to another tool
15	- H) Other
16
17	2. What's your current setup?
18	- A) New to Balto — evaluating or haven't started
19	- B) Purchased but in implementation (45-60 day window)
20	- C) Running but having issues
21	- D) Expanding to additional teams or modules
22
23	3. What's your CCaaS / telephony?
24	- A) Five9
25	- B) Genesys Cloud CX
26	- C) Amazon Connect
27	- D) Twilio Flex
28	- E) Talkdesk
29	- F) NICE CXone
30	- G) Cisco UCCE/PCCE (on-prem)
31	- H) Avaya Aura (on-prem)
32	- I) Microsoft Teams
33	- J) Other
34
35	4. Team size?
36	- A) 50-100 agents
37	- B) 100-500 agents
38	- C) 500+ agents
39
40	Skip-ahead rule: if the user's prompt already contains enough context, skip to Step 2.
41
42	## Step 2 — Route or answer directly
43
44	\| Problem domain \| Route to \|
45	\|---\|---\|
46	\| Building a coaching program or training cadence \| `/sales-coaching {user's question}` \|
47	\| Reviewing a specific call transcript for coaching \| `/sales-call-review {user's question}` \|
48	\| Choosing between note-taker/conversation intelligence platforms \| `/sales-note-taker {user's question}` \|
49	\| General CRM/tool integration patterns (Zapier, webhooks) \| `/sales-integration {user's question}` \|
50
51	Otherwise, answer directly using the platform reference below.
52
53	## Step 3 — Balto platform reference
54
55	Read `references/platform-guide.md` for the full platform reference — modules, pricing, integrations, compliance, workflows.
56
57	Answer the user's question using only the relevant section. Don't dump the full reference.
58
59	## Step 4 — Actionable guidance
60
61	You no longer need the platform guide — focus on the user's specific situation.
62
63	Implementation priority order:
64	1. Connect your CCaaS/telephony first — Balto must hook into the audio stream before anything works
65	2. Deploy the Balto desktop app or browser extension to agent workstations
66	3. Build your first playbook — start with one high-value use case (compliance checklist or objection handling)
67	4. Configure Real-Time QA scoring criteria aligned to your existing QA rubric
68	5. Set up coaching alerts so managers get notified of coachable moments in real time
69	6. Enable Balto Notes for automatic call summarization to CRM last — after guidance is stable
70
71	When comparing to Gong/enterprise CI tools: Balto's differentiator is real-time, in-call guidance — it coaches agents during the conversation, not after. Trade-off is that Balto focuses on contact centers (not field sales or deal intelligence) and requires 50+ agents minimum with enterprise pricing.
72
73	If you discover a gotcha, workaround, or tip not covered in `references/learnings.md`, append it there.
74
75	## Gotchas
76
77	> Best-effort from research — review these, especially items about plan-gated features and integration gotchas that may be outdated.
78
79	- No public API documentation. API access is customer-only behind login at balto.ai/docs. REST + webhooks with API key auth, but no self-service docs to evaluate before buying. Ask your account rep for API scope during evaluation.
80	- 50+ agent minimum typical. Balto targets mid-market to enterprise contact centers. Small teams under 50 agents are unlikely to get a contract or favorable pricing.
81	- 45-60 day implementation. Unlike lightweight tools that go live in hours, Balto requires CCaaS integration, desktop deployment, playbook configuration, and training. Plan for a 2-month rollout.
82	- *Pricing is quote-based and enterprise-level.

People who liked this also viewed

6 picks

Type

sales-balto

86stars9forks

View on GitHub

How to install sales-balto?

sales-skills/sales/sales-balto

$npx -y skills add sales-skills/sales --skill sales-balto

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Balto Platform Help
2
3	## Step 1 — Gather context
4
5	If `references/learnings.md` exists, read it first for accumulated platform knowledge.
6
7	1. What do you need help with?
8	- A) Real-Time Guidance setup (dynamic prompts, checklists, objection handling)
9	- B) Real-Time QA configuration (automated scoring, compliance checks)
10	- C) Coaching workflows (coachable moments, manager alerts)
11	- D) Compliance monitoring (PCI, HIPAA, regulatory scanning)
12	- E) Integrations (CCaaS, CRM, softphone)
13	- F) Balto Notes (automatic call summarization to CRM)
14	- G) Comparing Balto to another tool
15	- H) Other
16
17	2. What's your current setup?
18	- A) New to Balto — evaluating or haven't started
19	- B) Purchased but in implementation (45-60 day window)
20	- C) Running but having issues
21	- D) Expanding to additional teams or modules
22
23	3. What's your CCaaS / telephony?
24	- A) Five9
25	- B) Genesys Cloud CX
26	- C) Amazon Connect
27	- D) Twilio Flex
28	- E) Talkdesk
29	- F) NICE CXone
30	- G) Cisco UCCE/PCCE (on-prem)
31	- H) Avaya Aura (on-prem)
32	- I) Microsoft Teams
33	- J) Other
34
35	4. Team size?
36	- A) 50-100 agents
37	- B) 100-500 agents
38	- C) 500+ agents
39
40	Skip-ahead rule: if the user's prompt already contains enough context, skip to Step 2.
41
42	## Step 2 — Route or answer directly
43
44	\| Problem domain \| Route to \|
45	\|---\|---\|
46	\| Building a coaching program or training cadence \| `/sales-coaching {user's question}` \|
47	\| Reviewing a specific call transcript for coaching \| `/sales-call-review {user's question}` \|
48	\| Choosing between note-taker/conversation intelligence platforms \| `/sales-note-taker {user's question}` \|
49	\| General CRM/tool integration patterns (Zapier, webhooks) \| `/sales-integration {user's question}` \|
50
51	Otherwise, answer directly using the platform reference below.
52
53	## Step 3 — Balto platform reference
54
55	Read `references/platform-guide.md` for the full platform reference — modules, pricing, integrations, compliance, workflows.
56
57	Answer the user's question using only the relevant section. Don't dump the full reference.
58
59	## Step 4 — Actionable guidance
60
61	You no longer need the platform guide — focus on the user's specific situation.
62
63	Implementation priority order:
64	1. Connect your CCaaS/telephony first — Balto must hook into the audio stream before anything works
65	2. Deploy the Balto desktop app or browser extension to agent workstations
66	3. Build your first playbook — start with one high-value use case (compliance checklist or objection handling)
67	4. Configure Real-Time QA scoring criteria aligned to your existing QA rubric
68	5. Set up coaching alerts so managers get notified of coachable moments in real time
69	6. Enable Balto Notes for automatic call summarization to CRM last — after guidance is stable
70
71	When comparing to Gong/enterprise CI tools: Balto's differentiator is real-time, in-call guidance — it coaches agents during the conversation, not after. Trade-off is that Balto focuses on contact centers (not field sales or deal intelligence) and requires 50+ agents minimum with enterprise pricing.
72
73	If you discover a gotcha, workaround, or tip not covered in `references/learnings.md`, append it there.
74
75	## Gotchas
76
77	> Best-effort from research — review these, especially items about plan-gated features and integration gotchas that may be outdated.
78
79	- No public API documentation. API access is customer-only behind login at balto.ai/docs. REST + webhooks with API key auth, but no self-service docs to evaluate before buying. Ask your account rep for API scope during evaluation.
80	- 50+ agent minimum typical. Balto targets mid-market to enterprise contact centers. Small teams under 50 agents are unlikely to get a contract or favorable pricing.
81	- 45-60 day implementation. Unlike lightweight tools that go live in hours, Balto requires CCaaS integration, desktop deployment, playbook configuration, and training. Plan for a 2-month rollout.
82	- *Pricing is quote-based and enterprise-level.

People who liked this also viewed

6 picks

Type