기본 콘텐츠로 건너뛰기

Dify Playbook: Turn Your Help Docs Into a Support Chatbot

Summary: Dify is an open-source platform for building AI apps, and one of its most practical uses is a support chatbot that answers only from your own help docs. This playbook walks through the whole path on Dify Cloud: load your docs into a knowledge base, test what it finds, wire a Chatflow that refuses off-topic questions, and embed the bot on your site. The free Sandbox plan is enough to build and test a small version, but its 200 message credits and 10 knowledge requests per minute run out quickly once real visitors arrive.

Who this playbook is for

Picture a small software shop, an online course, or a freelancer with a product FAQ. The same twenty questions arrive by email every week, and the answers already exist in a help center or a folder of PDFs. A generic chatbot would make things up; what you want is a bot that looks up the right passage first and then answers from it. That pattern is usually called retrieval-augmented generation, and Dify packages it as a "knowledge base" you can attach to an app without writing code.

If you would rather host a private chat interface for your team than a public support bot, our Open WebUI playbook for small teams is the better fit. This one is about a customer-facing assistant.

Step 1: Create a workspace and pick your models

Sign up at cloud.dify.ai. New workspaces start on the free Sandbox plan. Before you build anything, check two settings, because a missing model is the most common reason a first bot does nothing.

  1. Model provider. Go to Integrations > Model Provider and install one of the providers that Dify's built-in AI credits support. Dify's docs say each AI response is one model call and counts as one response no matter how many tokens it uses, but larger models cost more credits per response than smaller ones. If you already have an OpenAI, Anthropic or similar key, click Setup on the provider card and add it; your own key bills to your provider account instead of using Dify's credits.
  2. Default models. Click Default Models at the top right of the model page and make sure an Embedding Model is set. That model turns your documents into searchable vectors. Dify's docs warn that when a default is empty, the features relying on it stop working.

Tip: the provider card has a Usage Priority setting, so you can let Dify's credits run first and have your own key take over when they are gone.

Step 2: Build the knowledge base from your help docs

Choose the kind of knowledge base

Dify now offers two kinds. An Agent Knowledge Base organizes and indexes content on its own, lets you choose a retrieval depth (Fast, Deep or Research), keeps connected sources in sync on a schedule, and includes quality tools such as golden questions. A Classic Knowledge Base lets you set chunking, index method and search method yourself. Dify's docs recommend the agent kind for new projects, with one important exception: the simple Chatbot app type can only use classic knowledge bases. Chatflow apps, which this playbook uses, can use either.

Add content

Go to Knowledge, switch to Agent, and click Create. Give it a name and a description, then add content in one of two ways:

  • Upload files for standalone documents such as a PDF manual. Files can be up to 15 MB each on an agent knowledge base. Batch uploads are a Professional and Team feature.
  • Connect a source when your docs live on a website or in Notion or Google Drive. Website crawling goes through a data source integration such as Firecrawl, which you set up in Integrations > Data Source with its own API key. You then paste the URL, click Crawl & preview, and pick which pages to import. The sync policy can be a preset, a custom interval from 1 hour to 30 days, or manual.

Start with ten or so of your most-asked help articles, not the whole site. Dify's own docs give the same advice: changing the embedding or reasoning model later re-indexes every document, which is cheaper while the knowledge base is small. On the free plan it also protects your 50-document quota.

Step 3: Test retrieval before any customer sees it

This is the step most tutorials skip, and it is where a support bot is won or lost. A model can only answer well if the right passage comes back first.

  1. Open the knowledge base's Retrieval Test page and type real customer questions in full sentences, the way people actually write them, such as "I was charged twice this month, how do I get a refund?" rather than "refund".
  2. Run the same question at each retrieval depth and keep the one that returns the right chunk most reliably as your default.
  3. When a result is right, click Keep golden question and tick the chunks that must come back. These become a regression test: after any later change, run Quality > Evaluations to confirm they still pass.
  4. When the right chunk is missing, click Make bad case. Dify's docs suggest first checking how the document was indexed, then widening the search with a higher Top K or a lower score threshold. If the chunk comes back but ranks too low, try a different rerank model.

If you use a classic knowledge base instead, you can pick hybrid search and set a weight between meaning-based and keyword matching; the official docs screenshot shows 0.7 semantic and 0.3 keyword. Product names, error codes and plan names are exactly the kind of words where keyword matching helps.

Step 4: Wire the Chatflow

In Dify, choose Create from Blank > Chatflow. Dify's customer service tutorial builds the bot from four kinds of nodes, and the layout is worth copying:

  1. Question Classifier. Sort each incoming message into categories such as "question about our product", "asking for a human", and "off-topic". Make the categories specific and clearly different from each other; the docs note that a stronger model classifies more accurately.
  2. Answer node for off-topic and handoff. These branches do not need a model at all. Reply with fixed text, for example a link to your help center or your support email. That saves credits and stops the bot from chatting about the weather.
  3. Knowledge Retrieval node on the product-question branch, pointing at the knowledge base you built.
  4. LLM node after retrieval. Set the retrieval output as its context and write a system prompt along the lines of: "Answer the customer's question using only the context. If the context does not contain the answer, say you are not sure and share the support email." You can insert variables by typing / or { in the prompt editor.

Turn on memory in the LLM node if you want follow-up questions like "and what about the yearly plan?" to make sense. Before publishing, run the same questions you tested in Step 3 through the finished flow.

Step 5: Publish and embed it on your site

Click Publish. Your app gets a web app URL you can share as-is. To place it on your own site, open the app's Access Point tab and choose Embed Into Site on the Web App card. Dify offers three ways to embed it:

  • A chat bubble, a floating button that opens the bot in an overlay. It is configured through a window.difyChatbotConfig object that holds your app token, plus optional styling and pre-filled inputs.
  • An iframe that keeps the chat always visible in the page.
  • JavaScript control for custom styling and behavior.

All three use the same published app, so later edits apply everywhere it is embedded. If you want the bot to hand conversations to another tool, such as logging unanswered questions into a spreadsheet, an automation tool like n8n can sit behind it; our n8n AI agent troubleshooting guide covers the usual errors there.

What the free plan really covers

The table below compares the three Dify Cloud plans using the figures on the official pricing page with monthly billing selected. Annual billing lowers the price (the page shows $590 and $1,590 per workspace per year).

Item Sandbox Professional Team
Price Free $59 per workspace / month $159 per workspace / month
Message credits 200 (no monthly refill) 5,000 / month 10,000 / month
Team members 1 3 50
Apps 5 50 200
Knowledge documents 50 500 1,000
Knowledge data storage 50 MB 5 GB 20 GB
Knowledge requests per minute 10 100 1,000
Log history 30 days Unlimited Unlimited
Dify API rate limit 5,000 / month No limit No limit

Prices exclude tax. The self-hosted Community edition is also free under the Dify Open Source License, but then hosting, updates and model keys are on you.

Editor's note

Good fit: small businesses and solo founders with a stable help center or product manual who want a bot that stays on topic, and who are fine adding their own model API key once free credits run out.

Not a fit: anyone expecting the free plan to serve live traffic. With 200 one-time credits, and every model call in your flow costing at least one response, a two-model Chatflow (classifier plus answer) uses credits roughly twice as fast as a single call per message.

Gotchas we found in the docs:

  • "Too many requests" while testing. On Sandbox, the 10-per-minute knowledge limit counts each retrieval test, each file upload (twice: when added and when processing starts), and on classic knowledge bases each Knowledge Retrieval node run. Refused requests count too, so wait a full minute instead of clicking again. Over the Service API this shows up as a 403 with the code forbidden.
  • Document quota fills up mysteriously. Disabled, archived and failed documents all still count toward the 50-document limit. Delete what you do not need.
  • Upload shows "Error". On a classic knowledge base, Dify may refuse a document if indexing it would exceed your storage. Free space or upgrade, then click Retry. Usage numbers can take several minutes to update.
  • Bot answers with nothing useful. Check that an embedding model is set under Default Models and that the documents show Ready.

FAQ

Can I keep using Dify after the 200 free credits are gone?

Yes. Dify's docs say that when the credits run out you can configure your own model provider API keys and keep going. The bot then costs whatever your provider charges per call. If you want cheap or free models to start with, see our OpenRouter free models breakdown.

Is there a discount for students or teachers?

Dify for Education lets verified current students, teachers and school staff use the Yearly Professional plan for free, re-verified each year. It needs a school-issued email, applies only to the yearly plan, and keeps AI credits at the Sandbox level of 200 one-time credits, so you will still want your own API key.

If I downgrade, do I lose my knowledge base?

No. According to Dify's docs, if a downgrade leaves your data above the new plan's limits, nothing is deleted and your apps can still search it, but adding content stays blocked until usage fits or you upgrade again. A downgrade takes effect at the start of your next billing cycle.

Build it small, test it with real questions, and only then put it in front of customers.

Image credits: Dify documentation (hybrid search settings), plus our own screenshots of the public Dify pricing page and Dify docs; see the official screenshots at the end of this post.

Last verified: 2026-10-29

Sources:

Uploaded Image Uploaded Image Uploaded Image Uploaded Image

댓글

이 블로그의 인기 게시물

브루(Vrew) 요금제 정리: 무료 200크레딧으로 어디까지 쓸 수 있나

요약: 영상 자막 편집기 브루(Vrew)는 2026년 4월 22일부터 기능별 사용량 대신 '통합 크레딧' 하나로 요금을 매겨요. 무료 플랜은 매달 200크레딧이 들어오는데, 음성 분석(자동 자막)만 쓰면 최대 200분 분량이라 짧은 영상 몇 편은 충분하지만, 영상 초반의 Vrew 마크를 지우려면 유료 플랜이 필요해요. 이 글은 브루 공식 가격 페이지와 고객센터 공지를 2026년 10월 23일에 다시 확인해, 크레딧 계산법과 플랜 고르는 기준을 정리했어요. 목차 브루 요금 구조: 통합 크레딧이란 1크레딧으로 할 수 있는 일 무료 플랜으로 되는 것과 안 되는 것 유료 플랜 4종 비교표 월 구독·연 구독·기간 이용권, 무엇이 이득일까 상황별 추천: 학생·직장인·유튜버 크레딧이 모자랄 때: 사용 기록 지우개 업그레이드·환불 전에 알아둘 규칙 운영자 메모, 자주 묻는 질문 1. 브루 요금 구조: 통합 크레딧이란 예전 브루는 플랜마다 음성 분석 몇 분, AI 목소리 몇 자, 번역 몇 자처럼 기능별 한도를 따로 줬어요. 그런데 보이저엑스(브루 운영사)가 실제 이용 데이터를 보니 한두 가지 기능만 집중해서 쓰는 사람이 훨씬 많았다고 해요. 그래서 2026년 4월 22일 업데이트부터는 플랜마다 정해진 크레딧을 받고, 어떤 기능에 쓸지는 내가 정하는 방식으로 바뀌었어요. 플랜별 매달 지급량은 Free 200 · Light 2,000 · Standard 10,000 · Business 12,000크레딧 이에요. 공식 공지에 따르면 무료 사용자는 매달 1일에, 유료 사용자는 매월 결제일에 충전되고, 남은 크레딧은 다음 달로 넘어가지 않아요. 바뀐 뒤 무엇이 좋아졌나 공지에 나온 예시가 이해하기 쉬워요. Standard 플랜에서 AI 목소리만 쓰면 예전에는 최대 50만 자였지만, 지금은 1만 크레딧을 모두 AI 목소리에 몰아 쓸 수 있어 최대 100만 자가 돼요. 반대로 여러 기능을 골고루 쓰는 사람은 크레딧이 기능끼리 ...

에이닷 전화 vs 익시오: 통화 녹음·AI 요약, 내 통신사·폰에 맞는 앱 고르기

요약: 통화 녹음과 AI 요약을 쓰고 싶다면 먼저 내 통신사와 휴대폰 종류부터 확인해야 해요. LG유플러스 고객은 무료 앱 익시오, SKT 고객은 에이닷 전화가 가장 기능이 많고, 다른 통신사의 아이폰 사용자는 iOS에 들어 있는 기본 통화 녹음·전사 기능이 현실적인 선택이에요. 이 글은 2026-10-30에 SKT·LG유플러스·Apple 공식 페이지와 도움말을 직접 확인해 세 가지를 비교했어요. 왜 '앱 기능'보다 '내 조건'을 먼저 봐야 할까요 통화 요약 앱 비교 글을 보면 기능 목록부터 나열하는 경우가 많아요. 그런데 실제로 써 보려는 사람에게 가장 먼저 걸리는 건 기능이 아니라 이용 조건 이에요. 익시오는 LG유플러스 고객 전용이고, 에이닷 전화는 누구나 설치할 수 있지만 통역콜·baro 같은 기능은 SKT 고객에게만 열려 있어요. 아이폰은 운영체제 구조상 앱이 통화를 마음대로 녹음하기 어려워서, 통신사 앱이 안 되면 iOS 기본 기능에 기대야 해요. 그래서 이 글은 "어떤 앱이 제일 좋은가"보다 "내 통신사·내 폰에서 무엇을 쓸 수 있나" 순서로 정리했어요. 기능 차이는 그다음이에요. 한눈에 비교: 에이닷 전화 vs 익시오 vs 아이폰 기본 통화 녹음 구분 에이닷 전화 (SKT) 익시오 ixi-O (LG유플러스) 아이폰 기본 통화 녹음 (Apple) 누가 쓸 수 있나 통신사 구분 없이 앱 설치 가능. 단, 통역콜·baro·그룹통화 발신 등은 SKT 고객 전용 U+ 모바일 고객. 타 통신사, 만 14세 미만, 선불요금제 고객은 제한 (공식 사이트 FAQ상 알뜰폰 중 KB리브엠은 예외) 지원 국가·언어의 iPhone 사용자. 1명과 통화할 때만 녹음 가능 지원 OS·기기 Android 10 이상, iOS 16 이상 iOS 17 이상 iPhone 12 이상 / Android...

타입캐스트 vs 클로바더빙: 수익 나는 채널에 쓸 때 무료·유료 조건 비교

요약 타입캐스트와 클로바더빙은 둘 다 글만 입력하면 한국어 AI 목소리를 만들어 주는 서비스지만, 무료로 쓸 수 있는 범위가 꽤 다릅니다. 클로바더빙 무료는 매달 15,000자까지 쓸 수 있는 대신 수익이 생기는 채널에는 쓸 수 없고, 타입캐스트 무료는 처음에 주는 약 5분 분량의 다운로드로 끝나는 체험판에 가깝습니다. 광고 수익이 붙은 유튜브나 쇼핑몰 영상에 넣을 목소리라면 처음부터 유료 플랜 조건을 보고 고르는 편이 안전합니다. 왜 이 두 서비스를 같이 비교하나 쇼츠 내레이션, 수업 자료 더빙, 상품 소개 영상처럼 "내 목소리 대신 AI 목소리"가 필요할 때 한국 사용자들이 가장 많이 찾는 곳이 네오사피엔스의 타입캐스트 와 네이버의 클로바더빙 입니다. 기능 소개만 보면 비슷해 보이지만, 실제로 문제가 되는 건 음질보다 "이 목소리를 내 채널에 써도 되나" 입니다. 그래서 이 글은 기능 나열보다 무료 사용 범위, 출처 표기 의무, 유료 플랜 가격과 다운로드 한도를 중심으로 정리했습니다. 모든 수치는 2026년 10월 25일에 두 서비스의 공식 요금 페이지와 고객센터 도움말에서 직접 다시 확인한 내용입니다. 한눈에 보는 비교표 항목 타입캐스트 무료 타입캐스트 베이직 클로바더빙 Free 클로바더빙 Standard 월 요금 0원 9,900원 (연간 결제 시 10% 할인) 0원 19,900원 (네이버 클라우드 플랫폼에서 결제) 무료·포함 사용량 음성 생성·재생 무제한, 다운로드는 최초 3,000크레딧(약 5분) 1회 지급 월 30,000크레딧(약 60분) 월 15,000자, 다운로드 월 20회, 프로젝트 누적 5개 (매월 1일 갱신) 월 30,000자, 다운로드 월 40회, 프로젝트 누적 20개 쓸 수 있...