Getting help: what to include in a support request
Summary
A report that says "it does not work" cannot be solved; a report that says which app, when, which file, which options and the exact message usually can. This page is a checklist for what to gather, how to get each item, and where to send it, limited to channels that exist on the site.
Details
Where to report (verified channels only)
- The Contact link. The site's menu and the footer of the AI tools carry a Contact link that opens the company's contact page. Use it for problems and questions. This book does not know of any promised response time, so do not rely on one.
- The feedback widget on each app page. Under the result, the page asks "How was your experience?" with answers Great, Okay and Not good. For the last two it asks you to say in a few words what you did not like or want improved, and has a Send feedback button. It also has a tooltip "Click to share your feedback about this tool". Good for quick signals; it is not a ticket system.
- If you work from the CLI, MCP or API, the same report items below apply, plus the command or call you ran.
This book names no email address, phone line, chat channel or SLA because none is documented in the product text it was written from. If the Contact page shows a more specific option, follow that.
The report checklist
Copy this list into your message and fill it in.
- App and site. Name of the app (for example Searchable, Ask PDF) and which site: the classic tools or the AI tools (Two sites, one product family).
- When it happened. Date, time and your time zone. The team can match it against their logs.
- Your file(s). Type (PDF, DOCX, JPG...), size in MB, number of pages, and how many files were in the run. Say whether the PDF is a scan or has selectable text, whether it is password-protected, and whether it was produced by another Documentize app.
- The options you chose. Language, output format, levels, anything you changed from the default. A screenshot of the settings panel is ideal.
- The exact message. Copy the text word for word, including the headline ("Free time limit reached", "Processing has stalled.", "Server error 500"...). Do not paraphrase.
- What you expected and what you got. One sentence each, plus the page numbers where the problem shows.
- Identifiers, if the page shows them. A task id (a GUID that can appear in result links) and, for a stopped free run, that a continuation was offered. Continuation ids are kept inside your browser and are not designed to be copied around; state "a continuation was offered at HH:MM" instead.
- Signed in or anonymous, and free or paid plan.
- Your environment. Browser and version, device, and whether a blocker or privacy extension is active. Note if it works in a private window.
- What you already tried. For example "re-ran after rotating", "tried Recovery".
Extra details that help, by kind of app
| Kind of app | Also mention |
|---|---|
| Organize (Merger, Splitter, Rotation) | The page ranges or order you typed; the page count before and after |
| Structure (Add TOC, Flatten) | The entries or field names you entered; whether the PDF had real form fields |
| Protect (Sign, Unlock) | Which step came before (compress, protect...), the certificate type (never the certificate itself) |
| Shrink and repair (Compressor, Recovery) | Size before and after; the level chosen; the damage notes Recovery printed |
| Extract (Searchable, OCR Image) | The document language, whether pages were sideways, a short sample of the wrong text |
| AI apps (Ask PDF, Abstracts) | The question or topic, the language, and the passage you believe is wrong |
Do before you report (saves a round trip)
- Run the matching page of this part: upload.md, bad-result.md, stopped.md, security-problems.md, ocr-ai-quality.md.
- Try once more after a few minutes if you saw "Server error" or a stall.
- Try the same file in a second browser, or after shrinking it, to separate a file problem from a page problem.
- If the file is damaged, try Recovery.
What to leave out
- Do not paste passwords, certificate files or
.pfxpasswords into a message. - Do not attach confidential documents unless you are sure you may. Describe the structure instead, or make a small test file that shows the same problem (a two-page file with dummy text is often enough).
- Anything you would not want read by a stranger.
Good to know about failed files
When a web run fails with an error that looks like file corruption (not a password or quota problem), the page automatically sends the failed file to the team's repair corpus, which is used to improve the Recovery tool. Password failures are never sent. You do not need to attach such a file again, but you should still report the problem if it blocks you.
A model report
App: Searchable (classic tools). Time: 14 Nov, about 15:20 UTC+1. File: scanned PDF, 48 MB, 120 pages, not protected. Options: language German, Deskew on, output Searchable PDF. Message: "Processing has stalled." after about ten minutes, signed in, free plan. Expected: a searchable PDF. Tried: a 20-page part of the same file, which worked.
That is all a person needs to start.