### Answer
Yes, putting objection handling directly in your prompt will increase token usage compared to using the Knowledge Base. However, there's a trade-off to consider:
**Token costs with KB**: Using Knowledge Base costs $0.005 per minute of calls that have knowledge base enabled [(1) ](
) . When KB is invoked, it retrieves chunks (default: 3 chunks with 0.60 similarity threshold) and appends them to the LLM prompt under "Related Knowledge Base Contexts" .
**Prompt engineering approach**: You can use sectional prompts to keep your instructions organized and focused [(2) ](
) . For objection handling specifically, you don't need to write lengthy responses - just concise guidelines .
**Recommended hybrid approach**:
- Put brief objection handling
guidelines in your prompt (e.g., "If caller says not interested: acknowledge and ask if there's a better time")
- Keep detailed product information, policies, and FAQs in the KB [(1) ](
)
For example, instead of full Q&A pairs in your prompt, use concise style guardrails [(2) ](
) :
## Objection Handling
If the caller says they're not interested: "I understand. Is there anything specific..."
If the caller is frustrated: "I hear your frustration, let me help resolve this..."
This keeps your prompt lean while maintaining deterministic control over conversation flow. The token increase from brief objection guidelines is typically less impactful than the unpredictability of KB overriding your node transitions [(3) ](
) [(4) ](
) .