PPayerLaunch

Fictional demo · Synthetic data only

Claim follow-up for small dental teams

A new report.
Your follow-up history stays.

Track claim follow-up across successive reports. Compare changed source facts while keeping the assignment, notes and reviews that explain what your team already did.

No file or account needed. Try made-up claims and see how follow-up work survives a new report.

Inside the workbenchSynthetic example

SYN-1042

Missing attachment
Fictional work item
Crown submission
Why it surfaced
Illustrative rule: the submission checklist expects a supporting image.
Available corrective choice

Mark attachment checklist complete

Illustrative outcome after human review

ReviewedOnly this demo’s queue changes.

Proposed input path · not connected today

Where would the report come from?

  1. 1. Practice softwareStaff run an agreed claims follow-up report in their practice-management system.
  2. 2. Verified exportSave one supported report format after its fields and meanings have been checked.
  3. 3. Staff uploadUpload the saved file, check the preview, then accept the comparison.
  4. 4. Compare and continueSee changed source facts beside the assignment, notes and earlier reviews.

That is the proposed journey. Today’s samples are independently fictional and use our invented format. No actual PMS export is supported; no payment or PMS API connection is implemented or selected.

Example fields and the work involved
Claim + location ID
SYN-1042 / DEMO-LOC-01 — identify the same item across reports.
Amount + source status
$840 / Missing attachment — facts to compare, separate from staff review.
Source update + report time
14 April 2030 — show when facts changed and how old the export is.
Coverage
Partial — absence from the next file does not mean paid or resolved.

A future user would choose the agreed report and date/location settings, export it, then upload it again for each comparison. We need to test how much preparation that takes and whether required fields are available; no copy-and-paste or automatic sync is promised.

In the demo, assign SYN-1042 and review its attachment checklist. The next sample changes its amount to $865 and asks for comparison. Your assignment and earlier review stay visible, while the changed facts need a new review. An absent item also remains open. This lets you inspect why work needs attention without treating yesterday’s review as approval of today’s facts.

From an exception to a recorded review

A reason to act.
A clear place to start.

01 / Find

Load a sample report

Preview a bundled fictional report, then filter the queue by what still needs follow-up.

02 / Understand

Prioritize and act

Read the reason, assign a fictional teammate and record a review with a sample note.

03 / Review

Refresh and keep your work

Load the updated sample to see new and changed items while keeping earlier notes, assignment and history.

What you can try today

A made-up report and follow-up flow that stays in your browser. Bundled samples use an invented format, not a supported practice-system export. A future service’s real-data entry path, permissions and production safeguards are not yet established.

See what is built and what is still ahead →

Help shape the first release

Build around the follow-up work your team actually does.

Work with Tanglewild Labs to test the proposed report workflow and give active feedback. Your input can help set priorities. We are gauging interest, with no promise to build or deliver a service.

$149per location / month · indicative

Indicative pricing only. No payment, subscription, commitment or price lock. Final scope and pricing require a future agreement.

Express interest