Credentialing Ticket Routing
Cred Specialization Rules
Jira Escalation Workflow
When to Transfer vs. When to Escalate
SOP & Process Clarification
100

When receiving a Cred question you cannot solve (and you are not part of the specialization), where should the ticket go?

Transfer to CC Cred Specialization using the macro [General] Transfer to CC Cred Specialization.

100

What types of questions commonly get transferred to the CC Cred Specialization?

Credentialing questions not tied to Atlas tasks, MSC rate questions, payer eligibility, recredentialing, and Evernorth MOS recruitment questions.

100

Where do you start when creating a Jira ticket for Cred from Zendesk?

Click the “+” icon → choose “Create issue.”

100

Which issues should be transferred to Cred Docs rather than escalated?

License issues, document upload issues, or questions tied to open Atlas tasks — after confirming they are not self-serve.

100

Where should unclear SOP questions be posted after informing your SME?

#cred-spec-smes on Slack.

200

What is the golden rule for moving tickets into a different Zendesk group?

Always use a transfer macro — NEVER manually change the assignee group.

200

If you're part of Cred specialization but can’t self-serve a solution, what is the next step?

Create an Ops Jira ticket for Cred following the SOP.

200

Which Jira project and issue type must always be selected for Cred tickets?

Project: Operations
Issue type: Cred Specialization

200

Which types of problems should not be escalated through the Cred Zendesk → Jira workflow?

Any Ops requests unrelated to Credentialing.

200

If a provider asks about payer eligibility that is not covered in SBSS, what do you do?

Escalate using the Cred Ops Jira workflow.

300

Name two issue types that should be transferred to the Cred Docs team.

– Questions about an open Atlas task
– License issues or issues with documents at intake

300

Should recredentialing questions always be escalated?

No — always check first, as many answers are in the SOP.

300

True or False: You may update the “Reporter” field when creating the Jira ticket.

False — never update the Reporter field.

300

A provider is not DPSR and claims cannot be submitted. Should this be escalated?

Yes — Cred specialization should escalate via Ops Jira if it cannot be self-served and is credentialing-related.

300

What must you never copy-and-paste into a Jira ticket?

The Zendesk ticket body — rewrite issue details in bullet points.

400

Which macro should be used for transferring documentation-related issues to the correct cross-functional team?

[General] Credentialing documentation, Transfer to XFN team (public reply).

400

If you believe an SOP or SBSS section is unclear, what must you do first?

Flag the issue to your SME, who will then engage #cred-spec-smes.

400

What must you ALWAYS fill out in a Cred Jira ticket, even if the question is not about a payer?

The Payer name – Cred field (select N/A if not payer-related).

400

What should you ensure before transferring a ticket related to intake documentation issues?

Verify whether it is self-serve by reviewing intake troubleshooting guides.

400

Which Jira field stores the provider’s identification used in credentialing workflows?

The Provider NPI field.

500

A provider uploads a COI with the wrong name or incorrect amounts. Where should this ticket be routed?

To the Cred Docs team, after confirming it is not self-serve.

500

A provider tags a ticket as Credentialing, but the issue is client eligibility. What should you do?

Transfer using the macro [General] Transfer to ONSHORE Other reason (public reply).

500

What happens if you choose the wrong Jira project or issue type?

The ticket will be closed automatically.

500

If a provider has multiple profiles or a “deceased provider” flag, where does the ticket go?

Escalate via Ops Jira — these are non-self-serve credentialing issues.

500

What is the final action required to submit the Jira ticket?

Clicking the blue “Create Issue” button — which automatically links Jira + Zendesk.

M
e
n
u