Chat With PDF: Ask Questions of Any Support Document
Upload a PDF, Word or text file up to 10 MB and chat with a model that answers only from it. Test a help center export, a policy or an SOP before an agent reads it.
A support team's real knowledge is rarely on the website. It's the returns policy in a PDF that legal signed off, the SOP for chargebacks in a Word file, the help center export nobody has reviewed since the last platform migration. Whether that content is good enough for an agent to answer from — unambiguous, current, complete — is something you can only judge by asking it questions and reading what comes back.
Upload the file — PDF, Word or plain text, up to 10 MB. It's converted to Markdown, the same step a WireDesk workspace runs on every uploaded document, and a chat opens with a model that answers only from what's in it, quoting the section it used. Ten messages or fifteen minutes per session. The file is held in memory for the session and dropped when it ends; it isn't written anywhere, and nothing you type is stored.
This ran once, on one input. The product runs on your whole site, every conversation.
Chat with every document you have — start freeExample: three turns on an e-commerce returns policy
You: can a customer return a sale item? Agent: Yes, but for store credit and within 14 days rather than 30. Section 2.3: "Items bought at a discount of 20% or more may be returned for store credit within 14 days of delivery." Refunds to the original payment method aren't offered on sale items. You: what if it arrived damaged? Agent: Section 4.1 asks for a photo within 48 hours of delivery. After that the customer chooses a replacement or a full refund, and the policy says return shipping is covered by the company in that case. You: do we refund the original shipping charge on a change-of-mind return? Agent: Not in the document. Section 2 says who pays return shipping (the customer, unless the item was faulty) but says nothing about refunding the outbound shipping charge. I'd check with whoever owns the policy before answering a customer.
What each input means
- 01
Upload a file
PDF, .docx, .doc, .txt or .md, up to 10 MB. A help center export, a policy document or a procedure works best. Scanned PDFs with no text layer convert to nothing: if you can't select the text in a viewer, the model can't read it either.
- 02
Ask what the document should settle
Ask the questions agents escalate about: the exception, the edge case, the customer who's just outside the window. Then ask something the document doesn't cover. A good document produces a specific answer with a section reference; a vague one produces a hedge.
- 03
Ten messages, fifteen minutes
Each session is ten of your messages or fifteen minutes, whichever comes first. When it ends the file is discarded. Upload a different document to start again — one file per session, so test the policy, then the SOP, not both at once.
Questions about this tool
PDF, Word (.docx and .doc), plain text and Markdown, up to 10 MB. Conversion to Markdown keeps headings, lists and tables, which is what makes section references possible. Spreadsheets and slides aren't accepted here; the Markdown converters on this site handle those, and you can save the result as a text file and upload that.