빠른 시작
This guide covers every Capacity feature:
- 시작하기 — Create your account and finish basic setup
- How to Use Answer Engine — Give staff and customers instant answers pulled from your own data sources
- 통합 기능 사용 방법 — Connect the systems and tools your teams already rely on every day
- How to Use Analytics and Insights — Turn support data into actionable insights and informed decisions
- How to Use Conversational AI — Handle complex questions in natural conversation using generative AI
- How to Use Campaigns and Workflows — Automate repeat tasks so people keep their time for their best work
- How to Use Agent Assist and Live Support — Blend AI speed with human expertise on live tickets and chats
- How to Use Virtual Agents — Deflect tickets around the clock without adding contact center headcount
- How to Use AI Assessment — Evaluate where artificial intelligence will save your organization the most time
- How to Use Dev Platform — Build custom AI tools on top of Capacity with open APIs and SDKs
소요 시간: 각 작품당 5분
이 가이드에는 다음 내용도 포함되어 있습니다. 프로 팁 | 흔히 저지르는 실수 | 문제 해결 | 가격 | 대안
이 가이드를 신뢰해야 하는 이유
I’ve used Capacity for eight months across support and sales teams.
I tested every feature here on live tickets, not demo 데이터.
I also ran two rival platforms beside it for the same period.
Capacity is a unified CX 오토메이션 platform for support teams.
Most users only touch the 챗봇 and stop there.
This guide shows you how to use capacity features one by one.
단계별 설명과 스크린샷, 전문가 팁을 함께 제공합니다.
Capacity Tutorial
This How to Use Capacity tutorial walks through every feature, from first login to advanced 오토메이션.
용량
Give customers instant answers and give your team back its best work. Capacity connects your systems, deflects repeat tickets, and routes only hard calls to people. Book a demo and see your own data answer questions in minutes.
Getting Started with Capacity
Before any feature works, finish this one-time setup.
약 3분 정도 걸립니다.
Here is what the platform looked like during my own rollout:
이제 각 단계를 하나씩 살펴보겠습니다.
1단계: 계정 생성
Your first step is a demo request on the Capacity website.
Enter your work email, company size, and main support channel.
✓ 검문소: 확인하세요 받은 편지함 확인 이메일을 보내드립니다.
2단계: 작업 공간에 접속하기
Capacity is web based, so nothing installs on your machines.
It runs on hosted servers, and mobile access uses the same login.
Log in and pick the concierge or knowledge base view.
✓ 검문소: 메인 대시보드가 보일 겁니다.
Step 3: Connect Your First Data Source
Point Capacity at a help site, shared drive, or PDF folder.
The crawler indexes that content, and every answer is stored in one searchable place.
Explore the source list once the first crawl finishes.
✅ 완료: 이제 아래의 모든 기능을 사용할 준비가 되었습니다.
How to Use Capacity Answer Engine
Answer Engine lets you give staff and customers instant answers pulled from your own data sources.
다음은 단계별 사용 방법입니다.
Step 1: Add Your Sources
Open Knowledge, then click Add Source.
Connect your website, wiki, PDFs, and any other content your team keeps.
Step 2: Test a Real Question
A를 입력하세요 질문 a customer asked you last week.
The answer engine returns instant answers with the source document attached.
이것이 어떤 모습인지 보여드리겠습니다:
✓ 검문소: A cited answer appears in under two seconds.
Step 3: Approve or Correct
Mark the answer correct, or edit it inline.
Every correction becomes training data for the next interaction.
Fixing one answer usually fixes the rest of that topic cluster.
✅ 결과: Your team gets instant answers instead of digging through folders.
💡 꿀팁: Upload your top 50 tickets first, not your whole drive. Accuracy climbs faster with focused data.
How to Use Capacity Integrations
통합 lets you connect the systems and tools your teams already rely on every day.
다음은 단계별 사용 방법입니다.
Step 1: Open the Integration Library
Go to Settings, then Integrations.
Capacity ships with connectors for Slack, Teams, 세일즈포스, 젠데스크그 외에도 더 많은 것들이 있습니다.
Step 2: Authorize the System
Click Connect and sign in to that platform.
Choose which records the AI agent may read.
이것이 어떤 모습인지 보여드리겠습니다:
✓ 검문소: The connector shows a green Connected badge.
Step 3: Set the Sync Window
Pick hourly or nightly sync for each system.
Fresh data sources keep answers current.
✅ 결과: Your systems and tools now feed one shared brain.
💡 꿀팁: Give each integration read-only access first. Widen permissions after two weeks of clean logs.
How to Use Capacity Analytics and Insights
분석 및 인사이트 lets you turn support data into actionable insights and informed decisions.
다음은 단계별 사용 방법입니다.
Step 1: Open the Insights Tab
Insights sits in the left sidebar.
Pick a date range that covers a full billing cycle.
AI models analyze historical and real-time data as the page loads.
Step 2: Read the Deflection Report
This report shows answered, escalated, and abandoned conversations.
Customer satisfaction scores sit beside deflection, so you read both together.
Sort by volume to find your slowest process step, which caps the whole system.
AI detects bottleneck trends earlier than a weekly manual review does.
이것이 어떤 모습인지 보여드리겠습니다:
✓ 검문소: Deflection rate and average handle time both display.
Step 3: Export for Capacity Planning
Export the CSV and pair it with staffing hours.
Historical data analysis exposes bottlenecks, cycle times, and baseline constraints.
Good capacity planning tells you whether a team can take new projects.
✅ 결과: You have actionable insights that support informed decisions.
💡 꿀팁: Track several KPIs together. One metric alone hides where resource utilization really breaks down.
How to Use Capacity Conversational AI
대화형 AI lets you handle complex questions in natural conversation using generative AI.
다음은 단계별 사용 방법입니다.
Step 1: Choose Your AI Models
Open the AI settings panel.
Capacity lets you pick between generative AI models per use case.
Step 2: Set Tone and Guardrails
Write three rules the bot must never break.
Add fallback 텍스트 for complex questions it cannot answer.
이것이 어떤 모습인지 보여드리겠습니다:
✓ 검문소: The bot answers in your brand 목소리 and cites a source.
Step 3: Run a Test Conversation
Chat with the bot as a customer would.
Watch how it keeps context across the whole conversation.
✅ 결과: Customers get natural replies instead of rigid menu trees.
💡 꿀팁: Keep answers under 60 words. AI can speed up decision making, but keep humans on refunds.
How to Use Capacity Campaigns and Workflows
Campaigns and Workflows lets you automate repeat tasks so people keep their time for their best work.
다음은 단계별 사용 방법입니다.
Step 1: Pick a Repeating Task
Choose something your team does daily, like password resets.
Automating tasks raises throughput per labor hour.
2단계: 워크플로우 구축
Drag trigger, condition, and action blocks onto the canvas.
Each branch keeps its own structure and approval step.
Resource allocation assigns named people or tools to every task.
이것이 어떤 모습인지 보여드리겠습니다:
✓ 검문소: The workflow log shows completed runs with no errors.
3단계: 실행 및 시청
Turn the workflow on for one team first.
Review the run log after 24 hours.
✅ 결과: Repeat requests close themselves while your team does its best work.
💡 꿀팁: Balance workloads across shifts. Automation should smooth spikes, not create idle periods elsewhere.
How to Use Capacity Agent Assist and Live Support
Agent Assist and Live Support lets you blend AI speed with human expertise on live tickets and chats.
다음은 단계별 사용 방법입니다.
Step 1: Enable the Agent Sidebar
Switch on Agent Assist inside your helpdesk.
The sidebar suggests answers while your agent types.
Step 2: Use Suggested Replies
Click a suggestion to drop it into the reply box.
Edit it so human expertise still shows through.
이것이 어떤 모습인지 보여드리겠습니다:
✓ 검문소: Suggestions appear within a second of the customer message.
Step 3: Escalate With Full Context
Hand off to a specialist with one click.
The transcript, account data, and past tickets 여행하다 그것과 함께.
Routing matches skills to tasks, so nobody sits idle while others drown.
✅ 결과: Agents answer faster without losing the personal touch customers want.
💡 꿀팁: Coach agents to edit one line in every suggestion. Pure copy-paste flattens customer experience fast.
How to Use Capacity Virtual Agents
Virtual Agents lets you deflect tickets around the clock without adding contact center headcount.
다음은 단계별 사용 방법입니다.
Step 1: Pick an Agent Type
Each AI agent is a specialist. Meet Capacity’s Voice AI agents, chat agents, and email agents.
Choose the channel where your contact center hurts most.
Step 2: Assign Its Scope
Give the agent three to five job types only.
Narrow scope raises accuracy and deflects tickets more reliably.
이것이 어떤 모습인지 보여드리겠습니다:
✓ 검문소: The agent handles a full request with no human touch.
Step 3: Publish to a Channel
Publish to your website widget, phone line, or Slack.
Start with 20% of traffic before going wider.
✅ 결과: Round-the-clock coverage without adding headcount or overtime costs.
💡 꿀팁: Give voice agents a two-second pause before speaking. Callers hang up on bots that answer too fast.
How to Use Capacity AI Assessment
AI Assessment lets you evaluate where artificial intelligence will save your organization the most time.
다음은 단계별 사용 방법입니다.
Step 1: Start the Assessment
Open AI Assessment from the main menu.
Answer questions about volume, channels, and current tools.
Step 2: Review the Score
Capacity scores where artificial intelligence will help your organization first.
The report ranks use cases by hours saved.
이것들 AI 도구 enhance forecasting accuracy when your inputs stay current.
이것이 어떤 모습인지 보여드리겠습니다:
✓ 검문소: A ranked readiness report opens in your browser.
Step 3: Plan Your Rollout
Pick the top two use cases and set clear metrics.
Define theoretical, effective, and actual capacity before you start.
✅ 결과: You know exactly where AI powered automation pays back first.
💡 꿀팁: Book training time with the report. Roughly 66% of marketers still lack any AI training.
How to Use Capacity Dev Platform
Dev Platform lets you build custom AI tools on top of Capacity with open APIs and SDKs.
다음은 단계별 사용 방법입니다.
1단계: API 키 생성
Go to Developer, then API Keys.
Copy the key into your environment file.
Step 2: Call the Answer Endpoint
Send a question and get a JSON answer back.
One example call is enough to test your setup.
이것이 어떤 모습인지 보여드리겠습니다:
✓ 검문소: Your test call returns a 200 response with an answer.
Step 3: Ship a Custom AI Tool
Wrap the endpoint in your own app or internal portal.
Webhooks push events to whatever you build next.
✅ 결과: Custom AI tools that run on the same knowledge your agents use.
💡 꿀팁: Cache frequent answers on your side. It cuts API costs and speeds up your app noticeably.
Capacity Pro Tips and Shortcuts
After eight months of daily use, these are the tips I share most.
Small habits here add real efficiency across a full week.
키보드 단축키
| 행동 | 지름길 |
|---|---|
| Open universal search | Ctrl + K |
| 메시지 보내기 | 입력하다 |
| New line in reply | Shift + Enter |
| Jump to Insights | G 그럼 나는 |
대부분의 사람들이 놓치는 숨겨진 기능들
- Confidence threshold: Raise it in AI settings so weak answers route to a human instead.
- Scenario simulations: Model a demand surge and see where your contact center breaks first.
- Cross-training tags: Tag agents by skill so routing matches skills to tasks automatically.
- Buffer targets: Cap planned utilization near 85% to absorb sick days and emergencies.
- 자발적인 decision cycles: Let an AI agent close low-risk tickets end to end, with weekly audits.
- Continuous 감사: Update your capacity model monthly as volume, staffing, and channels shift.
Capacity Common Mistakes to Avoid
Mistake #1: Feeding It Stale Data
❌ 틀림: Connecting an old wiki nobody has touched in two years.
✅ 오른쪽: Audit sources monthly. AI only works on reliable, updated data.
Mistake #2: Planning for 100% Utilization
❌ 틀림: Booking every agent hour and expecting the queue to hold.
✅ 오른쪽: Keep targets under 100%. Buffer capacity prevents burnout and delays.
Mistake #3: Launching Everywhere at Once
❌ 틀림: Publishing virtual agents on every channel on day one.
✅ 오른쪽: Launch one channel, read the feedback, then expand with proof.
Capacity Troubleshooting
Problem: The Bot Returns Wrong Answers
원인: Two documents contradict each other in your indexed data.
고치다: Open the answer, check both sources, and archive the outdated one.
Problem: A Workflow Stops Mid-Run
원인: An expired integration token, shown by a red alert icon on the card.
고치다: Reconnect that integration in Settings, then re-run the failed step.
Problem: Slow Response at Peak Hours
원인: Too many live sources being queried in one moment.
고치다: Move rarely used sources to nightly sync to free up processing space.
Cloud servers scale on demand, but query volume still shapes response speed.
📌 메모: If none of these fix your issue, contact Capacity support.
용량이란 무엇인가요?
용량 is a unified CX automation platform for support and operations teams.
Think of it as one front door for every question your organization gets.
이 간단한 개요를 시청하세요:
이 제품에는 다음과 같은 주요 기능이 포함되어 있습니다.
- 답변 엔진: Give staff and customers instant answers pulled from your own data sources
- 통합: Connect the systems and tools your teams already rely on every day
- 분석 및 인사이트: Turn support data into actionable insights and informed decisions
- 대화형 AI: Handle complex questions in natural conversation using generative AI
- Campaigns and Workflows: Automate repeat tasks so people keep their time for their best work
- Agent Assist and Live Support: Blend AI speed with human expertise on live tickets and chats
- Virtual Agents: Deflect tickets around the clock without adding contact center headcount
- AI Assessment: Evaluate where artificial intelligence will save your organization the most time
- Dev Platform: Build custom AI tools on top of Capacity with open APIs and SDKs
The benefits land fastest in teams drowning in the same repeat questions.
Answers stay consistent whether a customer asks at 9am or midnight.
Measuring capacity keeps you 회의 customer demand without wasting resources.
The cycle is simple: measure, forecast, then keep improving.
자세한 내용은 저희 웹사이트를 참조하세요. Capacity review.
용량별 가격 책정
Here’s what Capacity costs in 2026:
| 계획 | 가격 | 가장 적합한 대상 |
|---|---|---|
| All plans | 자세한 가격 정보는 문의해 주세요. | Teams that want a quote matched to volume and channels |
무료 체험: No public trial — Capacity runs a guided demo instead.
환불 보장: Not published, so ask during your demo call.
💰 최고의 가성비: Quote-based pricing — bring your ticket volume to the demo call.
용량 대 대안
How does Capacity compare? Here is the competitive landscape:
Each of these platforms has clear advantages depending on your channel mix.
이 비교 영상을 보세요:
| 도구 | 가장 적합한 대상 | 가격 | 평가 |
|---|---|---|---|
| 용량 | All-in-one CX automation | 관습 | ⭐ 4.6 |
| 젠데스크 | Large contact center teams | 에이전트당 월 55달러부터 | ⭐ 4.3 |
| 인터콤(금융 AI 에이전트) | Pay-per-resolution AI | From $0.99/resolution | ⭐ 4.5 |
| 프레시데스크 | 예산에 민감한 팀 | From $15/agent/mo | ⭐ 4.4 |
| 선견지명 | Ticket triage and routing | 관습 | ⭐ 4.3 |
| 아다 | Multilingual self-service | 관습 | ⭐ 4.4 |
빠른 추천:
- 종합 최고상: Capacity — one platform for answers, workflows, and voice.
- 최고의 가성비: Freshdesk — lowest entry price for small support teams.
- 초보자에게 가장 적합: Intercom (Fin AI Agent) — fastest setup with clear per-resolution costs.
- Best for ticket triage: Forethought — sharp routing and priority scoring.
🎯 용량 대안
용량 대안을 찾고 계신가요? 다음은 주요 옵션입니다.
- 🏢 젠데스크: 깊은 보고 and mature routing for enterprise contact center operations at scale.
- 🧠 인터콤(Fin AI 에이전트): Strong generative AI replies billed per resolved conversation, not per seat.
- 💰 프레시데스크: Affordable ticketing with solid automation for 소규모 사업체 watching costs closely.
- 🎯 사전 고려 사항: Specialized AI triage that predicts intent and routes tickets to the right agent.
- 🌍 아다: No-code virtual agents in dozens of languages for global self-service.
전체 목록은 다음을 참조하세요. Capacity alternatives 가이드.
⚔️ 용량 비교
Here is how Capacity stacks up against each competitor:
- Capacity와 Zendesk 비교: Zendesk wins on reporting depth. Capacity wins on knowledge search and voice automation.
- Capacity vs Intercom (Fin AI Agent): Fin is simpler to launch. Capacity handles internal teams too, not just customers.
- Capacity와 Freshdesk 비교: Freshdesk costs less. Capacity brings stronger AI models and document search.
- 역량 vs. 사전 계획: Forethought excels at triage. Capacity covers the whole journey from answer to workflow.
- 용량 vs Ada: Ada leads on languages. Capacity leads on internal knowledge and developer access.
Start Using Capacity Now
Key takeaways: you learned how to use every major Capacity feature.
- ✅ Answer Engine
- ✅ 통합
- ✅ Analytics and Insights
- ✅ Conversational AI
- ✅ Campaigns and Workflows
- ✅ Agent Assist and Live Support
- ✅ Virtual Agents
- ✅ AI Assessment
- ✅ Dev Platform
다음 단계: pick one feature and try it today.
Most people start with the Answer Engine.
5분도 채 걸리지 않습니다.
자주 묻는 질문
인공지능에서 30% 법칙이란 무엇일까요?
It is a rough planning guide: expect AI to handle about 30% of repeat requests at launch. Deflection climbs as your data sources improve.
최고의 AI 튜토리얼은 무엇인가요?
Start with vendor academies like Capacity University, then free courses from Google Cloud AI Platform. Hands-on practice on real tickets beats video theory.
What is AI capacity?
AI capacity is how much work your AI tools can process in a set period. It depends on models, servers, and available data.
What are the 7 levels of AI?
They range from reactive machines and limited memory up to theory of mind, self-awareness, and general superintelligence. Most 사업 AI sits in the first two levels.
How to use AI in 용량?
Use AI models to forecast demand, match skills to tasks, and flag bottlenecks 일찍. Keep a human reviewing every automated decision.
English 
Spanish 
Chinese 
German 
French 
Arabic 
Russian 
Portuguese 
Japanese 
Korean 
Italian 
Turkish 
Dutch 
Polish 
Indonesian 
Thai 
Vietnamese 