Automated rfxcel Customer License Verification
The moment a new customer application is submitted, WebRun pulls the applicant's DEA registration and state license details into rfxcel, verifies the license is active and unrestricted in NABP, prepares the new customer agreement in DocuSign but leaves it unsent, and posts your account team a Slack alert once verification is complete.
How do I verify a new pharmacy customer's license before opening their account?
WebRun verifies a new pharmacy customer's license the moment their application is submitted. It captures the DEA and state license details in rfxcel, confirms the license is active and unrestricted against NABP's own record, and prepares the customer agreement in DocuSign, holding it unsent until compliance signs off. Your account team gets a Slack alert once verification is complete.
- Every new account is verified against NABP before it ships a single order
- The customer agreement stays unsent until compliance signs off
- Invalid or restricted licenses are flagged before the account opens
Built for pharmaceutical wholesalers · drug distributors · compliance officers · account-opening teams
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.rfxcel.comin a real browser with your saved login - no setup, no API keys. -
1
rfxcel - capture the application's license details
WebRun opens rfxcel to capture the application's license details. - Read the new customer application for the DEA registration number, state license number, and resale certificate
- Enter the applicant's details into rfxcel's trading partner record
- Flag any field that is missing or looks malformed
Done when The application's license details are captured in the trading partner record.
-
2
NABP - verify the license is active
WebRun opens NABP to verify the license is active. - Look up the state pharmacy license in NABP's verification tool
- Confirm the license status is active and unrestricted
- Note the expiration date on file
Done when The license is confirmed active and unrestricted, or flagged if it is not.
-
3
DocuSign - prepare the customer agreement
WebRun opens DocuSign to prepare the customer agreement. - Prepare the new customer agreement with the verified license details filled in
- Attach the verification result to the envelope for the record
- Leave the envelope unsent until compliance confirms the account can open
Done when The agreement is prepared and held, not sent, pending compliance sign-off.
-
4
Slack - notify the account team
WebRun opens Slack to notify the account team. - Notify the account-opening team that verification is complete
- State clearly whether the license passed or needs a closer look
- Point them to the held DocuSign envelope ready for their review
Done when The account team has the verification result and knows the envelope is ready to review.
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 send the customer agreement before the license is confirmed?
No. WebRun prepares the agreement in DocuSign and leaves it unsent until a person on your compliance team confirms the license and clears the account.
What if the license comes back inactive or restricted?
WebRun flags it clearly in the Slack alert instead of preparing the agreement, so the account is not opened on an invalid license.
Where does it verify the license?
Directly against NABP's licensure verification tool, so the status reflects the state board's actual record, not a cached or self-reported value.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.