How to Train an AI Support Bot on PDF Pricing Sheets

Your website says "Contact sales for pricing." Your reps email a 14-page PDF rate card. Visitors ask chat anyway—and without that PDF indexed, the bot either hallucinates a number or says "I don't know." Both kill trust.

Chirps lets you upload PDFs alongside your website crawl so answers ground in the same documents your sales team uses. This guide covers upload strategy, versioning, and prompts that prevent invented quotes.

Why PDFs Still Matter for B2B Support

• Tiered pricing too complex for a marketing page—volume discounts, regional rates, partner tiers.
• Spec sheets with SKUs, dimensions, and compatibility matrices.
• SLA and support add-ons buried in sales-only collateral.
• Legacy PDFs that predate your current website redesign.

Crawling your public site alone misses all of this. Uploads close the gap.

Step-by-Step: Train on PDF Pricing

1. In Chirps dashboard, open your assistant → Knowledge → Upload Files.
2. Drag your rate card PDF (or .docx, .txt). Name it clearly: `pricing-2026-q2-rate-card.pdf`.
3. Run Train so embeddings index the new content.
4. Crawl your public pricing page separately—visitors may ask about list prices vs. negotiated rates.
5. Test five real pricing questions your sales team hears weekly.
6. Remove superseded PDFs when publishing new quarters—stale docs cause wrong quotes.

Version control best practices

• Include effective dates in filenames and cover pages.
• Add a one-paragraph "pricing FAQ" on your website that mirrors PDF tiers—gives the crawler a second source.
• If tiers are ambiguous, instruct the bot to say "pricing varies by volume—see latest rate card or contact sales."

System Instructions That Prevent Hallucinated Quotes

Add explicit boundaries in your assistant instructions:

Pair PDFs With Website Crawl

The strongest setup uses both sources:

• Public site: List prices, plan names, feature comparison tables—what self-serve buyers expect.
• PDF uploads: Enterprise tiers, partner pricing, custom SLAs—what reps attach to emails.
• Recrawl after launches: When you publish new web pricing, recrawl so chat stays aligned with marketing.

Common failure modes

1. PDF is a scanned image with no OCR text—re-export as searchable PDF.
2. Outdated Q3 PDF still indexed after Q4 launch—delete old upload.
3. Question uses slang ("what's the team plan cost?") but PDF says "Business Tier"—add synonyms to FAQ page.
4. Visitor asks for pricing not in any doc—bot should escalate, not guess.

Test Questions Before Going Live

Run these against your trained assistant after every upload:

• "What's included in the Pro tier?"
• "Do you offer volume discounts above 500 seats?"
• "What's the difference between Standard and Enterprise SLA?"
• "Is there setup fee for annual contracts?"
• "What currency are these prices in?"

If any answer cites a number not in your PDF or site, fix instructions or remove conflicting sources before embedding the widget.

When to Escalate Instead of Quoting

Custom quotes, government procurement, multi-year renewals, and bundle negotiations should trigger a lead capture form or human dispatch—not an AI-generated price. Configure artifacts for "Request custom quote" with fields for company size, use case, and timeline.