All Collections
Streamline Intake with Workflow
Understand the Requested Referral Process
Understand the Requested Referral Process

Learn what it means for a referral to be 'requested' and if it will work for your agency's workflow.

Rachel Shelswell avatar
Written by Rachel Shelswell
Updated over a week ago

This is a more complex referral process focusing on moving a referral from a Requested state and either accepting it or denying it, before moving forward.

Why start at a requested state?

When a referral is submitted or booked, it is ready to be acted upon and action is sought. An action would mean determining if your agency needs to evaluate referrals prior to intake (i.e. determining if they're going to accept or deny the referral).

After Requested

Once it lands in your inbox, you have several options. First, if the sender likes to know once you've reviewed the referral moving it to a Received classification would be helpful. After Received, or if you've opted to bypass the Received option, you can move the referral to either Accepted or Rejected. If you moved it to Rejected at this point, the referral has reached its final destination and no future actions will take place.

In Progress

A referral can move to this state once you've decided to accept the referral, but a final action has not yet taken place.

On Hold

At any point in time, a referral can be moved to on hold (i.e. Waitlisted) as referrals may have to be put on pause for a number of reasons, regardless of what else has been going on in relation to the referral. 

Final Action Sub Status Classifications

This includes Completed, Failed, Rejected, and Cancelled which we discuss in detail over here

Need help implementing this process? 

Please send us a message, using our Chat box. 

Did this answer your question?