10 questions to ask a credentialing provider

Which questions make proposals easier to compare?

Send each shortlisted company the same brief: provider types, number of providers and locations, states, target payers, current systems, and the work you want to hand off. Ask for written answers to these questions.

• 1. What work is included? Separate credentialing, enrollment, contracting, licensing, and ongoing maintenance.
• 2. What experience do you have with our provider types and target payers? Ask for relevant examples with permission to share.
• 3. Who owns each task? Name your contact and the responsibilities that remain with the practice.
• 4. How will we see progress? Request a sample status report with blockers and next actions.
• 5. How are missing information and rejected applications handled? Agree on follow-up and escalation responsibilities.
• 6. What timing can you control? Separate the company’s preparation time from decisions made by payers or facilities.
• 7. How are sensitive records handled? Request documentation appropriate to the data you will share and the access staff need.
• 8. What is the total price? Ask about setup, per-provider charges, exceptions, ongoing maintenance, and renewals.
• 9. How does support work? Confirm contact methods, service hours, response expectations, and escalation paths.
• 10. What happens when we leave? Confirm cancellation, record access, export formats, and open-application handoff.

How should you evaluate the answers?

Use evidence rather than a simple yes/no checklist. A sample report is more useful than “full visibility,” and a written list of supported payers is more useful than “nationwide coverage.” Keep unanswered questions visible instead of treating an incomplete proposal as equivalent to a detailed one.

For software, run a demonstration using your own sample workflow. For services, walk through a hypothetical application from intake to completion. In both cases, ask what happens when the process does not go as planned.

How do reviews fit into the decision?

Look for dated descriptions of work similar to yours. A review about billing may say little about credentialing support, and a software review from a large hospital may not reflect a small practice’s needs. Consider both praise and criticism in context.

Record why you chose your shortlist and what still requires confirmation. A rating can help you identify questions to ask; it cannot replace scope, references, or a contract you understand.

How can you compare answers without hiding gaps?

Use an evidence column beside each requirement. “Confirmed in the proposal,” “demonstrated with a sample,” and “not yet answered” communicate more than a single numerical score. A vendor that fits most criteria may still fail a requirement essential to your practice.

For example, an outpatient group adding a location could make the new payer and location scope a required condition, then compare reporting and training among the vendors that meet it. These are illustrative criteria, not ratings of the companies in this directory. Keep the operational owner involved in deciding what is essential.

• Write each requirement as a task or observable result.
• Record the supporting proposal section or demonstration result and its date.
• Keep mandatory requirements separate from preferences.
• List the owner and deadline for each unresolved question.

What makes a customer reference useful?

Ask for a reference with a comparable practice type and service scope. Discuss how the engagement began, how missing information was handled, and what happened when something went wrong. A positive reference about billing does not establish how a credentialing-only engagement will operate.

Read online reviews in the same way: look at the date, service used, specific event, and any company response. Do not treat a few reviews, a company-selected testimonial, or an award without published voting records as a reliable estimate of typical results.

Sources and next steps

• Compare the directory
• Understand our review labels