Automated Predetermination Packet Prep
Every morning, WebRun opens XLDent to find restorative treatment plans needing a predetermination, gathers the procedure codes, narrative, and supporting images into a packet in Google Drive, and prepares a DocuSign cover for signature, leaving the submission queued for your billing lead to approve before anything is sent.
How do I automatically assemble dental predetermination packets?
WebRun opens XLDent each morning to find restorative plans needing a predetermination. It gathers the codes, narrative, and supporting images into a packet in your secure Google Drive folder and prepares a DocuSign cover, then queues the whole submission for your billing lead to approve, so predeterminations are ready to release but never sent to an insurer unreviewed.
- Predetermination packets are assembled and ready to release the same morning
- The billing lead approves each submission instead of building it from scratch
- No patient detail reaches an insurer without a human approving the release
Built for prosthodontists · dental billing specialists · restorative practices · insurance coordinators
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
www.xldent.comin a real browser with your saved login - no setup, no API keys. -
1
XLDent - gather predetermination details
- Open XLDent and find restorative treatment plans that require a predetermination before scheduling
- Capture the procedure codes, tooth numbers, clinical narrative, and any supporting images or radiographs
- Skip plans whose predetermination has already been assembled or submitted
Done when Every plan needing a predetermination has its codes, narrative, and supporting evidence captured.
-
2
Google Drive - build the packet
drive.google.com
WebRun opens Google Drive to build the predetermination packet. - Open the practice's secure predetermination folder in Google Drive
- Assemble a packet per patient with the codes, narrative, and supporting images in the payer's expected order
- Name each packet clearly and keep it in the review folder, not a shared external link
Done when A complete, clearly named predetermination packet sits in the review folder for each plan.
-
3
DocuSign - prepare the cover for signature
docusign.com
WebRun opens DocuSign to prepare the predetermination cover for review. - Prepare a DocuSign cover or attestation for the billing lead to sign where the payer requires it
- Attach the assembled packet reference so the reviewer sees the full submission
- Leave the envelope queued and unsent for the billing lead to review and release. Never submit to the insurer automatically
Done when Each predetermination is queued in DocuSign for the billing lead to approve and release.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it submit predeterminations to the insurer automatically?
No. WebRun assembles each packet and queues a DocuSign cover, but leaves it unsent. Your billing lead reviews and releases every submission, so nothing reaches an insurer without approval.
How is the patient's clinical information protected?
The packet stays in your secure Google Drive review folder, not a shared external link, and the DocuSign envelope is held for internal review. Patient detail is only released when your billing lead approves it.
What if a predetermination has already been submitted?
It checks XLDent each morning and skips any plan whose predetermination is already assembled or submitted, so no duplicate packet is built for the same case.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.