FileRidge Claim Review
Authorized claim reads and separately approved claim and carrier changes with your existing FileRidge account.
FileRidge connects existing customers to authorized claim reads and separately approved claim and carrier changes in ChatGPT or Codex. It is provided by Beach Plain LLC and is intended for availability in the United States. Available tools depend on your organization’s activation, role and permissions; the complete integration has 29 tools, not every account has all of them.
Read and prepare supported changes
Find claims by exact internal FileRidge claim number; read stored status, dates and limited claim-file metadata. When enabled, prepare supported claim updates or creation and carrier profile, reporting requirements and pricing changes. Carrier administration requires a tenant ADMIN. Claim-file reads do not expose file contents or download links. The connection does not execute invoices, record payments or send email.
Review before saving
Read and preview tools do not save business changes. Review the exact proposed values, current state and impact, then give a separate confirmation before submission. Expired or changed proposals require a fresh preview and renewed approval. Pricing changes affect effective-dated pricing settings; they do not rewrite recorded entries or issued invoices. Availability can be stopped without removing authorized read access.
Selected fields, relevant evidence
Use relevant cited carrier-document passages to help populate selected supported fields. Missing or conflicting evidence leaves values unchanged until clarified. Review carrier’s full document for instructions affecting your business; this review only helps populate selected FileRidge carrier fields. This reminder belongs at the start and completion of a field review; it is not a complete policy or compliance assessment.
Carrier documents
Authorized tenant ADMINs can read bounded carrier-document excerpts with source/version/page citations. Separately enabled document actions support preview and approval for upload, replacement, withdrawal and restore. Native ingestion requires the host’s file picker and complete text PDFs up to 25 MB and 50 pages. Scanned, partially extracted or larger files require the FileRidge Carrier Documents UI/OCR workflow. A chat attachment is not automatically stored in FileRidge. Withdrawal retains history; it is not deletion.
Optional feature requests
For an encountered unsupported situation, you may ask to prepare one concise feature request. After reviewing its exact title, description and impact, separately approve submission. It creates a CREATOR_ONLY tenant CHANGE_REQUEST and creation activity in the existing Requests workflow, not a promise of implementation or confirmed staff delivery. Do not include raw guides, attachments, personal claim details or secrets.
Use your existing account
Use your own FileRidge account, organization activation and OAuth sign-in. Access follows existing organization and record permissions. There are no purchases or payments within the plugin. Ask for connection status to confirm the intended account and available capabilities; a missing tool is not permission to use another identity.
Examples to try when connected
“Find this exact internal FileRidge claim number.” “Preview a report-due date change.” “Help populate selected carrier reporting fields from relevant cited passages.” “Prepare a feature request for this encountered limitation.”
Understand what you share
Returned claim metadata, authorized carrier configuration, document excerpts and action previews/results are shared with your selected AI host. For ChatGPT or Codex, that host is OpenAI. The host’s terms, privacy policies and account settings govern its handling of that information. Read the privacy notice before connecting.
Legacy demonstration
The existing demonstration shows the earlier read-only Claim Review workflow. It does not demonstrate or prove acceptance of the current write, carrier-document or feature-request capabilities.