如何打造不會編造定價的網站 AI 銷售助理
Building a Website AI Sales Assistant That Does Not Hallucinate Your Pricing
文章提出打造網站 AI 銷售助理的方法，重點是先把銷售實際使用的定價底線、服務範圍、服務地區及資格篩選規則納入知識庫，避免助理自行編造價格。建議按問題而非 PDF 頁面切分內容、附上公開頁面的標準 URL，並在定價或政策變更時更新；助理可先問 3–6 個資格問題，再按匹配程度分流潛在客戶。低信心時應在兩輪對話內轉交人工，並每週抽查 20 段對話，核對答案是否符合已批准的知識庫。
AI chat widgets on B2B sites are easy to install and easy to get wrong. The failure mode we see most is not "the model is dumb" — it is that the knowledge base never received the sentences sales already uses on calls: pricing floors, scope boundaries, regions served, and disqualification rules. The assistant then invents friendly nonsense.
What belongs in the knowledge base first
Prioritize extractable facts over brand essays:
- Who you serve (and who you do not)
- Starting budgets / fee ranges with conditions
- Onboarding steps and typical timelines
- Documents required from the client
- Regions and languages supported
- What happens after a lead submits a form
If a human SDR would refuse to quote without a call, teach the bot to say the same — and to collect the fields that make the call useful.
Structure beats dumping PDFs
Chunk content by question, not by PDF page. Each chunk should answer one intent: "minimum monthly ad budget", "do you open TikTok accounts for games", "which countries for crypto merchants". Include the canonical URL of the public page so the bot can cite it.
Refresh chunks when pricing or policy changes. A stale minimum budget in the KB is worse than no budget at all, because prospects screenshot it.
Qualification logic
Good assistants ask 3–6 questions before deep product talk: company type, target markets, monthly budget band, timeline, existing ad accounts. Route high-fit leads to calendar or WhatsApp; route low-fit to a resource email. This is ordinary sales process, automated.
Safety rails
- System prompt: never invent fees; if missing, say you will have a human follow up
- Block list: competitors' libel, illegal verticals you do not serve, credential requests
- Human handoff visible within two turns when confidence is low
- Log prompts and answers for weekly review
A starter overview of the product side sits at overseas marketing automation / AI sales assistant. Brand home: PandaWM.
Success metric
Not "number of chats". Use: qualified conversations per week, form completion rate, and % of answers that match the approved KB (spot-check 20 transcripts weekly). Hallucinated pricing should be a P0 defect.
Updated October 2026.
來源：DEV Community · dev.to