What the Crisis Safety Platform Actually Is
If you’ve been handed a login and a referral to process but aren’t sure what you’re logged into, here’s the short answer: the Crisis Safety Platform (CSP) is Carelon’s behavioral health referral and crisis-coordination system, used by the Georgia Collaborative ASO under the Georgia Department of Behavioral Health and Developmental Disabilities (DBHDD). It’s the tool that moves a person needing crisis care from one facility to an available bed — tracking referrals, acceptances, denials, and placement in one place so the coordination doesn’t happen over a chain of frantic phone calls.
One point trips people up: CSP is not the same as GCAL or 988. The Georgia Crisis & Access Line (GCAL, reachable at 988) is the phone-and-text front door where someone in crisis first calls for help. CSP is the back-end system staff use to coordinate what happens next — finding a placement, routing the referral, confirming a bed. They work together, but you don’t dial CSP and you don’t log into 988.
The people using CSP are the staff you’d expect: workers at crisis stabilization units (CSUs), emergency rooms, jails, mobile crisis teams, and state hospitals — anyone coordinating a referral or bed placement. So if a supervisor gave you credentials or assigned you a referral task here, you’re in the right place. The rest of this guide walks you through using it.
How to Log In and Complete Okta Verification
That unfamiliar verification screen isn’t a glitch — it’s Okta, the identity service Carelon uses to guard access to the platform. Once you know what you’re looking at, it takes about a minute to clear.
First, confirm you’re in the right place. The legitimate login lives on the Georgia Collaborative ASO portal hosted by Carelon. Before you type credentials, check that the URL ends in a Carelon or georgiacollaborative.com domain and shows a padlock. If a search result drops you on a generic “crisis solutions” marketing page or a bare login box with no Georgia branding, back out — that’s not it.
Completing Okta multi-factor verification
- First-time enrollment: After your username and password, Okta prompts you to set up a factor. Choose Okta Verify (app push), SMS, or voice call based on what your facility allows.
- Pick your factor on return visits and trigger the code or push.
- Enter the 6-digit code or approve the push within roughly 30 seconds before it expires.
If the code never arrives or the screen looks wrong
- Wait 60 seconds, then hit “Send again” — carrier delays are the usual culprit.
- Confirm your phone number on file is current; an old number silently routes codes nowhere.
- Clear your browser cache or try an incognito window if the layout looks broken or stuck.
Most first-login snags trace back to one of these. If the account is fully locked after several tries, that’s a password-reset issue — covered next.
How to Reset a Password or Recover a Locked Account
A locked account at the wrong moment feels like a wall, but most lockouts clear in under five minutes if you take the right path instead of guessing. CSP runs sign-in through Okta, so password recovery happens on the Okta screen, not inside CSP itself.
Self-service reset
- On the CSP login screen, click “Need help signing in?” then “Forgot password?”
- Enter your work email or username and choose your verification factor (SMS, email, or the Okta Verify app).
- Follow the link, set a new password, and sign back in.
Locked vs. expired
An expired password still lets you reset yourself — Okta typically forces a reset every 60–90 days. A fully locked account (often after several failed attempts) may show “account locked” with no reset option. Locks frequently auto-clear after 15–30 minutes, so a short wait sometimes solves it.
When to call for help
If self-service fails, you have no enrolled verification factor, or your access was never fully provisioned, that’s an administrator or help desk job. Contact your facility’s CSP super-user first, then the Georgia Collaborative ASO support desk for Carelon-side issues.
Avoiding fake reset pages
Only reset through the legitimate Okta domain you reach by typing the official CSP URL yourself — never through a link in an unexpected email or text.
Finding the Right Referral Workflow for Your User Type
Here’s why a generic walkthrough may not match your screen: a mobile crisis clinician and a state hospital discharge planner use CSP for almost opposite purposes, even though they log into the same Carelon-managed system. The buttons you’re looking for may not exist for your role — and that’s by design, not a bug.
The core split comes down to whether you send, receive, or route referrals:
- ERs and jails typically initiate referrals — you’re pushing a patient or detainee out to a CSU, crisis stabilization unit, or bed-finding queue.
- CSUs and crisis stabilization units mostly receive them — your task is accepting or denying incoming referrals, often against bed availability.
- Mobile crisis teams often do both: triaging in the field, then routing to the right facility through GCAL/988 coordination.
- State hospitals lean toward discharge and transfer workflows, moving people back into community placements.
If a task your supervisor mentioned isn’t appearing, the issue is almost always your assigned role and permissions, not the platform itself. Check your user profile inside CSP for your facility type and access level. If accept/deny controls or a referral queue are missing entirely, your role likely needs to be updated — a permissions request through your facility administrator or the Georgia Collaborative service desk, not something you can fix by clicking around.
When you search for help, add your setting — “CSU referral acceptance,” not just “CSP referral” — so the workflow you find matches the one in front of you.
Steps to Accept, Deny, or Route a Referral Correctly
The scariest click in CSP is the one you can’t easily undo — and when a patient is waiting, that pressure is real. Here’s how each path works so you can act with confidence.
Accepting a Referral
Open the referral from your queue and review the clinical summary first. Before you accept, confirm your actual bed or slot availability — the system won’t check this for you. Click Accept, then update the status to reflect intake (often “Accepted – Pending Arrival”). This pings the sending party that the patient has a confirmed destination, so don’t accept what you can’t truly hold.
Denying or Declining
A denial requires a reason code — you can’t bounce it with a blank field. Choose the code that genuinely fits: No Capacity, Out of Service Area, Clinical Exclusion, or Insurance/Eligibility. The sender sees this code immediately, which tells them whether to resubmit or look elsewhere. A vague or wrong code is what delays care, not the denial itself.
Routing or Redirecting
If the referral belongs with another provider, use Route (sometimes labeled “Redirect”) rather than denying it. This forwards the full record — documentation intact — to the appropriate facility without forcing the sender to start over. The original referral stays linked, so nothing disappears from the audit trail.
Every status change is a message: Accepted says “we’ve got them,” Denied with a code says “here’s why not,” and Routed says “try this provider instead.” When unsure, route rather than deny — it keeps the patient moving.
Red Flags to Avoid When Acting on a Referral
The fastest way to delay care isn’t a system error — it’s a small handling mistake that buries a referral until someone notices it’s been sitting too long. A few patterns cause most of the trouble, and they’re all avoidable once you know what to watch for.
- Letting a referral time out. Most referrals in the Carelon platform carry an acceptance window, and an unacknowledged referral doesn’t politely wait — it can auto-route or escalate, pulling your facility into a compliance loop. Even if you can’t act immediately, open it and acknowledge receipt so the clock reflects reality.
- Denying without a valid reason code. A denial that skips the required reason code or supporting documentation reads as an incomplete bounce, not a clinical decision. Pick the accurate code, add a brief note, and you’ve protected both the patient’s path and your own audit trail.
- Acting on the wrong record. Duplicate referrals and similar names are common under pressure. Confirm date of birth and the referral ID before you accept or deny — updating the wrong record is far harder to unwind than it is to prevent.
- Treating a phone handoff as the update. A call to GCAL, the receiving CSU, or a mobile team coordinates care, but it does not change the in-platform status. If the screen still says “pending,” the system — and everyone relying on it — believes the referral is still open.
Where to Find Official Training and Guides
The fastest way to learn CSP isn’t a Google search — it’s the official provider resource pages maintained by the Georgia Collaborative ASO, which Carelon operates on behalf of DBHDD. The Georgia Collaborative provider portal hosts the legitimate training materials, and Carelon’s provider resource sections link out to role-specific documentation that generic vendor marketing pages simply don’t carry.
Once you’re in, look for the training and education or provider resources tab. That’s where you’ll find quick-reference guides and recorded webinars sorted by user type — CSU, ER, jail, mobile crisis, and state hospital workflows are documented separately because the referral steps genuinely differ.
Making sure a guide is current
Before you trust any PDF, check three things:
- A revision date or version number on the document, ideally within the past 12–18 months
- Whether it names your role and workflow explicitly, not “providers” in general
- That it’s hosted on a Georgia Collaborative or Carelon domain, not a third-party reseller site
If you’re a supervisor onboarding new staff, point them to the recorded webinars first — they walk through live screens — then to the printable quick guides. If a current guide for your facility type doesn’t exist, the provider support line can send the official version directly rather than letting people piece it together from outdated screenshots.
When to Escalate and How to Submit a Support Ticket
Knowing when to keep troubleshooting versus when to file a ticket saves you the most precious thing you have on shift: time. Most account snags are self-resolvable in minutes — try those first before escalating.
Self-Resolve vs. Escalate
Handle these yourself: a locked account (wait 15–30 minutes or use the self-service reset), an Okta verification prompt you didn’t expect (re-enroll your device through the Okta panel), or a forgotten password. Escalate when a reset email never arrives, your account exists but has the wrong user type or permissions, a referral is stuck in a status you can’t change, or you get a persistent error code the system won’t clear.
Where the Real Support Lives
CSP is operated by Carelon Behavioral Health through the Georgia Collaborative ASO. The legitimate help desk and ticket portal are reachable via the Georgia Collaborative provider support line and its web portal — not a random search result. Don’t trust third-party “login help” pages asking for your credentials.
To get a ticket resolved on the first pass, include your user type (CSU, ER, jail, mobile crisis, or state hospital), the exact error message or code, a screenshot, and the referral or member ID if relevant.
One critical distinction: if a person is in an active behavioral health crisis, that is not a platform issue — call GCAL/988 immediately for clinical help.
