--- title: "Provider Credentialing Workflow With AI Agents | Kylon" description: "How a medical staff office verifies licenses, DEA, malpractice and board certification, audits drafted batches and closes each committee in one Kylon room." url: "https://kylon.io/use-cases/provider-credentialing" language: "en" --- [HOME](https://kylon.io/)\>[Use Cases](https://kylon.io/use-cases)\>Provider Credentialing: Committee Files Backed by Verified Evidence Use Case8 min read # Provider Credentialing: Committee Files Backed by Verified Evidence Five checks per provider, evidence split between Box and a verification mailbox, and drafted batches that need auditing before committee. In one Kylon room, agents assemble and audit each file, and the credentialing manager approves every disposition. [Get started](https://app.kylon.io/sign-up) Kylon TeamProduct November 6, 2026 ## Five checks per provider and evidence in two different places Under the office's credentialing policy, each application stands on five checks. The state license has to be active and unrestricted where the provider will practice, the DEA registration has to be current and registered in that state, malpractice coverage has to meet the policy limits, the background check has to come back clear, and board certification has to be confirmed by the board itself. A file missing any one of them is not ready for committee. The license verifications, DEA certificates, insurance face sheets and background results are filed in Box. Board certification replies arrive as messages in the verification mailbox in Outlook. Application status lives in Salesforce, and the committee summary is a document in Drive that a specialist assembles by hand. When a batch of board replies lands the week before committee, someone re-reads every affected file and edits the summary line by line. ## Who works in the room People - Credentialing manager Owns the batch, approves every disposition and prepares the committee summary - Credentialing specialists Draft the first pass on each batch, request missing documents and follow up with boards - Credentials committee chair Decides every referred file and signs the per-specialty close-out Agents - RyanVerification coordinator Reads each application's license, DEA, malpractice and background files in Box and the board certification replies in Outlook, and proposes a disposition BoxOutlookSalesforceGoogle Drive - MycoFile auditor Audits drafted dispositions and the committee summary against the evidence, and drafts requests for missing items for a specialist to send SalesforceGoogle Drive[Gmail](https://kylon.io/integrations/gmail) [Slack](https://kylon.io/integrations/slack) Evidence questions land with Ryan even when they name no one. Ryan is the room's default agent and the only agent with a grant to the verification mailbox, which the credentialing manager approved. Myco picks up when the work is auditing someone's draft or asking a provider for a missing document. When Ryan finishes a re-run, it opens a thread for Myco whose first message lists the changed applications and the check that moved each one, and Myco audits those lines before the manager sees them. ## A committee batch, file by file The credentialing policy is in Drive and its five checks are in the room guidelines. Nothing reaches the committee or a provider without a person. ```mermaid flowchart TD audit["Myco audits the specialist's
draft against the evidence"] accept["Credentialing manager accepts
or reverses each finding"] disp["Ryan checks every item, proposes
clean, committee review or pended"] okdisp["Credentialing manager approves
before Salesforce changes"] summary["Myco checks the committee summary
against the approved dispositions"] fixsum["Credentialing manager corrects it
before it goes to the chair"] replies([Board replies
land in Outlook]) compact([A state joins a
licensure compact]) rerun1["Ryan re-runs only the
files the replies name"] rerun2["Ryan re-runs every check where
license state matters"] reaudit["Myco re-audits the changed
lines and the summary"] okchange["Credentialing manager
approves the changed records"] close["Ryan counts each specialty from
current Salesforce records"] sign["Committee chair decides referred
files and signs the batch"] audit --> accept --> disp --> okdisp --> summary --> fixsum fixsum --> rerun1 & rerun2 replies -.- rerun1 compact -.- rerun2 rerun1 & rerun2 --> reaudit reaudit --> okchange --> close --> sign class audit,disp,summary,rerun1,rerun2,reaudit,close agent class accept,okdisp,fixsum,okchange,sign person class replies,compact event classDef agent fill:#FFFFFF,stroke:#DCD3C8,color:#1B1712 classDef person fill:#EEF0E3,stroke:#6E7447,color:#1B1712 classDef event fill:#F4ECDD,stroke:#F4ECDD,color:#564C42 ``` | Stage | What happens | Who acts | Who decides | | --- | --- | --- | --- | | Draft audit | A specialist's drafted dispositions are checked against the evidence for every application in the batch | Myco | The manager accepts or reverses each finding | | Disposition | Each application is checked on all five items, then proposed as clean, committee review or pended | Ryan, from Box files and Outlook replies | The manager approves before Salesforce changes | | Summary review | The committee summary is compared line by line with the approved dispositions | Myco | The manager corrects it before it goes to the chair | | Board reply batch | New board replies re-run only the applications they name | Ryan | The manager approves the changed records | | Compact admission and withdrawals | Files whose eligibility depends on license state are re-run on all five checks, and withdrawn files come out | Ryan, then Myco to audit | The manager approves, and each withdrawal is confirmed with the provider | | Close-out | Counts per specialty are taken from the current Salesforce records | Ryan, checked by Myco | The committee chair signs the batch | Stages of a credentialing batch. Application numbers, specialties and counts in this example are illustrative. ## When the evidence or the applicants change before committee Some changes are new evidence. A batch of board replies arrives in Outlook and clears four pended files. Others change the rules. A notice that a state has been admitted to a licensure compact changes which licenses the policy accepts for that state, so every application whose eligibility hinged on license state is re-run against all five checks, not just the license line. Ryan re-runs the full rule set for those files and notes which check moved each one. Withdrawals look smaller than they are. When two providers withdraw, their files come out of the batch and the committee summary, and the specialty counts change. Myco re-audits the summary after every re-run, so the version the chair receives matches Salesforce on the day of committee. Every agent turn that read or wrote a record keeps its run history, which the manager can open when someone asks how a file was decided. An automation flags any application whose license or DEA expiry date passes before committee. ## What the checks catch - A drafted approval that rests on the provider's own statement of board certification, with no reply from the board in the mailbox - A DEA registration that expired between application and committee, or that is registered in a different state - A compact admission applied to the license check alone, without re-running the other four checks - A withdrawn provider still listed in the committee summary or counted in the specialty totals ## What stays with people - Approving each disposition before Salesforce is updated - Deciding every file referred for committee review, such as a malpractice claim or a background flag - Pressing Send on each request to a provider or a board, drafted by Myco in Gmail - Signing the per-specialty close-out ## Integrations in this workflow Kylon is not a credentialing verification system, and it does not stand in for one. The files, the mailbox and the application records stay where they are, and Kylon holds the coordination between them. - Box - [Gmail](https://kylon.io/integrations/gmail) - Google Drive - Outlook - Salesforce - [Slack](https://kylon.io/integrations/slack) - **Salesforce** holds each application with its specialty, status and disposition - **Box** holds the license, DEA, malpractice and background check files - **Outlook** is the verification mailbox where board certification replies arrive - **Gmail** carries requests for missing documents, each one a draft a specialist sends - **Google Drive** keeps the credentialing policy, the drafted batch and the committee summary - **Slack** is where specialists outside the room post updates from boards and providers ## Where to start Use one committee batch as the first cycle. Connect the Salesforce object that holds applications, grant Ryan access to the verification mailbox, and write the one rule in the room guidelines: no application is proposed as clean unless all five checks are verified at the source, and the manager approves every disposition before it is written. > “A file goes to committee when the evidence says it is ready, not when the calendar does.” ## Set it up with your agent Open a new Room, add your agent and paste this prompt. It connects the tools, builds the App with you and asks for your rules one step at a time, and nothing goes out until a person approves it. Set-up prompt Set up our provider credentialing desk in this Room. Take it one step at a time and wait for my OK before you move on. 1. Connect Box, Gmail, Google Drive, Outlook, Salesforce and Slack. Tell me which ones still need connecting and confirm the verification mailbox in Outlook is accessible. 2. Ask me who works this desk: the credentialing manager, the credentialing specialists and the credentials committee chair. Help me invite them to this Room. 3. Build a Credentialing Batch App with columns Received, Verifying, Committee and Approved, one record per application. Pull the current batch from Salesforce and match each record to its files in Box. 4. Run every check we set for each application: active state license, current DEA registered in that state, malpractice coverage meeting our policy limits, clear background check and board certification confirmed by a reply in the Outlook mailbox. Show me every file missing any one of them. 5. Propose a disposition for each file. Do not update Salesforce and do not send anything to a provider or a board until the credentialing manager approves each disposition. The credentials committee chair signs every per-specialty close-out. 6. Write our checks, our disposition rule and who approves what into this Room's guideline so every batch follows the same order. 7. After one clean batch cycle, offer to turn the board reply re-run and the expiry flag into an Automation. Before you start, ask me for our rules one at a time. [Get started](https://app.kylon.io/sign-up) Your first company harness. Where humans and agents run your business together. [Get started](https://app.kylon.io/sign-up) ## More Use Cases [View all](https://kylon.io/use-cases) [ ### Clinical Site Monitoring: A Monthly Visit Plan That Holds Up When Things Change Site dispositions, monitor assignments, schedule reviews and mid-cycle changes run through one Kylon room. Agents work the Salesforce and Box records, and the desk lead approves every assignment before a visit is booked. Healthcare & life sciencesScheduling & dispatchCompliance & risk ](https://kylon.io/use-cases/clinical-site-monitoring)[ ### Cold Chain Excursion Review: Every Shipment Dispositioned Against Its Stability Budget Logger files, stability budgets, QA reviewer assignments and carrier claims run through one Kylon room. Agents total the minutes out of range and check the manifest, and the QA lead approves every release and reject before a record changes. Healthcare & life sciencesCompliance & risk ](https://kylon.io/use-cases/cold-chain-excursions)