View source for TracCloud: SAGE

{{TracCloudGuideTabs}}
<div class="tcWidgetPage">
{{RetentionTier}}
<div class="categoryDynamic">
{{TracCloudModulesTOC}}
</div>
<div class="pageTitle">SAGE Early Alerts</div>

The SAGE Early Alert module is TracCloud’s early-alert referral system. It allows faculty and support center staff to submit referrals or progress reports for students who may be struggling academically or have other concerns. Through an online form, a professor can flag a student and indicate the issue (e.g., poor attendance, low grades, personal concern) and SAGE will route that information to the appropriate support staff. Based on how the referral is configured, TracCloud can automatically notify relevant parties – for example, send an email to the student’s academic advisor or to a tutoring center coordinator to reach out proactively. SAGE basically creates a case for the student: support staff can record follow-ups, note whether the student was contacted, and close the loop. This helps colleges be proactive in connecting at-risk students with resources. This early-warning systems ensures no student “falls through the cracks” when faculty raise a concern.

You can think of SAGE like a three-step process.
:'''1. Creation, a referral is submitted, emails are sent out.'''
:These emails could be sent to advisors, professors, or the student themselves, notifying us of something the student may be struggling with.

:'''2. Follow-up, more information is given, new emails are sent out.'''
:The follow-up email lets relevant users know how this referral is going, what has been done, and what we are doing to help this student.

:'''3. Resolution, a final email is sent out to wrap everything up.'''
:Once the referral has been processed, we can fill out some additional information letting the relevant users know what we did to help this student.

<hr>
==<b>Creating and Completing Referrals</b>==

There are multiple ways to create referrals for students, depending on which method best fits your campus workflow. Referrals can be created by faculty via the class roster, or by advisors or other staff from student profiles.

<hr>
<!--------------------------------------- Roster annotations --------------------------------------->
<div style="float: left; margin-top: 0em; margin-bottom: 1em"><big><b>Faculty View: Roster Annotations</b></big></div><div class="mw-collapsible mw-collapsed">
<br><br>
Faculty Members are typically the primary user-type submitting referrals, and as such, they have a streamlined view of the referral submission process. On the faculty dashboard, you'll find their class rosters along with the referrals that have been designated as Roster Annotations (which will be covered later in this article). This allows faculty to immediately access important referrals for each of their rosters.

[[File:2782382.png|900px]]<br><br>

As a faculty member, let's say we wanted to submit a referral for one of our classes. We can simply click on the referral we want to submit for any given roster, then we'll be given access to a batch referral tool. 

[[File:8435382.png|900px]]<br><br>

From this menu, we can click on individual students and fill out unique referrals for each without leaving this screen. Once we've filled out referrals for the specific students, we click save and we're all set. The referral process has begun for each of these students that we filled out a referral for and emails will be sent.

[[File:2335678.png|900px]]<br><br>

If the referral is configured as a roster annotation for [X] days (covered later in this article), we can even open this batch referral tool later (but within the day limit) and continue where we left off by updating existing referrals. The green check-marks indicate a referral that has already been opened. Clicking it again lets us pick up right where we left off. 

[[File:1308519.png|900px]]<br><br>

We also have the ability to apply the same Reason/Recommendation to multiple students at once. Select <b>Affect All Selected and Shown</b> and check the checkboxes for each student we want to assign this reason/recommendation to. Now when we make a recommendation or apply a reason to one student, it will also affect all other checked students. We will see that all other students now have a <big><b>...</b></big> icon, which indicates that a referral is in progress.

[[File:7205192.png|900px]]<br><br>

As a faculty member, we can also book an appointment for the student from this screen as well (assuming our permission group allows it). This can be accomplished by clicking on the calendar icon on the right-hand side for the relevant student.

[[File:6205497.png|900px]]<br><br>

Lastly, faculty can submit a "Nothing to Report" referral from this screen. This will immediately create a generic referral for the current date labeled as "[Nothing to Report]."
</div>
<hr>
<!--------------------------------------- Individual --------------------------------------->
<div style="float: left; margin-top: 0em; margin-bottom: 1em"><big><b>Student Profiles: Individual Referrals</b></big></div><div class="mw-collapsible mw-collapsed">
<br><br>

Referrals can be submitted individually from student profiles as well. As non-faculty staff don't have access to the class roster view, this will be their primary utility for submitting referrals, but faculty can of course use this method too. New referrals can be created through the <b>Actions</b> button, past referrals can be viewed on the student timeline.

[[File:3092325.png|900px]]<br><br>

After selecting the referral type that we want to submit, we're taken to the full referral submission screen. We'll cover more on configuring this side of SAGE later in this article.

[[File:8037497.png|900px]]
</div>
<hr>
<!--------------------------------------- Mass Referral Tool --------------------------------------->
<div style="float: left; margin-top: 0em; margin-bottom: 1em"><big><b>Student Listing: Batch Referrals</b></big></div><div class="mw-collapsible mw-collapsed">
<br><br>

It's also possible to submit referrals from the student listing in bulk. This allows us to search for students enrolled in a specific course, [[TracCloudGuideGlobalLists|load a list]], or just search for a couple students manually and create referrals as a batch. This screen will operate in the same way as the faculty roster referral tool. Students are selected with the checkboxes on the right-side.

[[File:4781587.png|900px]]<br>

[[File:2946252.png|900px]]
</div>
<hr>
<!--------------------------------------- Processed --------------------------------------->
<div style="float: left; margin-top: 0em; margin-bottom: 1em"><big><b>Processing/Completing Referrals</b></big></div><div class="mw-collapsible mw-collapsed">
<br><br>
After a referral is marked as processed, we will see the following screen summarizing basic information about this referral, and providing a location to write additional notes about how this situation was resolved. Once saved, the final "Processed" email will be sent out, as configured in your <i>Automated Emails</i>. A referral can be re-opened by unchecking the "Processed" box.

[[File:8734417.png|900px]]
</div>
<hr>
<!--------------------------------------- Referrals Listing --------------------------------------->
<div style="float: left; margin-top: 0em; margin-bottom: 1em"><big><b>Referrals Listing</b></big></div><div class="mw-collapsible mw-collapsed">
<br><br>
If a permission group allows it, it's also possible to utilize the Referrals Listing to quickly access all referrals in your TracCloud instance. This can be accessed by going to <i>Other > Listings > Referrals</i>.

[[File:8390835.png|900px]]

<hr>
{{#lst:Template:TracCloudListingDescriptions|Hamburger_Menu}}

{{#lst:Template:TracCloudListingDescriptions|List_All}}

{{#lst:Template:TracCloudListingDescriptions|Power_Search}}

{{#lst:Template:TracCloudListingDescriptions|Selected}}

{{#lst:Template:TracCloudListingDescriptions|Change_Field_Values}}

{{#lst:Template:TracCloudListingDescriptions|Show_these}}

{{#lst:Template:TracCloudListingDescriptions|Print}}

</div>
<!--------------------------------------- SAGE management --------------------------------------->
<hr>
==<b>SAGE Configuration</b>==

The following chapters of this wiki article will cover how you can create your SAGE referral types, including the reasons, recommendations, emails, custom questions, and more.
<hr>
<!--------------------------------------- Creating referral types --------------------------------------->
<div style="float: left; margin-top: 0em; margin-bottom: 1em"><big><b>Creating SAGE Referral Types</b></big></div><div class="mw-collapsible mw-collapsed">
<br><br>

To create new SAGE Referral Types, modify existing, or simply review your current configuration, go to <i>Other > Modules > SAGE Referral Types</i>. This will bring you to the Referral Type Listing. To create a new Referral Type, you would click the hamburger icon ({{#fas:bars}}), then select <b>New Referral Type</b>.

[[File:4222337.png|900px]]<br><br>

After opening a referral or creating a new one, you will be able to access the following options.

[[File:1919543.png|900px]]<br><br>

* <b>Name</b> is the name of this referral type.

* <b>Profiles</b> is the linked profile for this referral type, primarily used to determine linked advisor in reports.<br>

* <b>Active</b> will toggle this referral on or off, allowing you to deactivate it when unneeded, and reactivate it when necessary.

* <b>Test Mode</b> will send all emails to the <b>Test Email Address</b> rather than the actual recipient. This should be enabled when testing emails to prevent your end users from receiving referral notices for test referrals.

* <b>Condense Roster Referral View</b> will display Reasons and Recommendations in a more tightly packed view for faculty. This may be preferred if many referrals are being created at once. Does not affect visible data fields.

* <b>Roster Annotation</b> designates this referral type as a Roster Annotation, meaning it appears as an option for class rosters from the faculty dashboard perspective.

::* <b>Days</b> is the time-frame provided to the faculty member where they can edit an existing roster referral. After this window has passed, the faculty member will create a new referral rather than editing an existing one.

* <b>Linked List</b> allows you to assign this referral type to a specific student list. Faculty and other users will only be able to create this referral for students on that list. [https://wiki.go-redrock.com/index.php/TracCloudGuideGlobalLists More information on student lists].

* <b>Referral to Testing Center</b> is a bigger topic, which can be found further into this wiki article.

* <b>Roster Annotation Settings For Faculty Viewing</b> allows you to link this referral type to a specific subject. The referral will then only appear in contexts of that subject/course/section from the roster referral perspective.

* <b>Notes Instructions</b> is a message that appears to the user submitting this referral, providing information above the Notes box.

[[File:8328146.png|900px]]<br><br>

* <b>Additional Notes Instructions</b> is a message that appears to the user submitting this referral, providing information above the Additional Notes box.

* <b>Processed Button Title</b> determines the name of the "Processed" option, "Complete," "Resolved," etc.

* <b>Hide Options</b> allows you to toggle certain elements/features of your Referral Type off if preferred. Some fields can also be hidden from faculty specifically, while remaining visible to staff.

* <b>Require Notes</b> / <b>Additional Notes</b> will require that whoever is submitting this referral enter notes in one or both of these fields.

* <b>Ask for Special Needs / Accommodations</b> will provide a question in the referral entry form (for both staff and faculty) to fill out [[TracCloud:_Special_Needs,_Skills,_and_Accommodations|special needs, skills, or accommodations]] for the student. You can configure your search availability widget to automatically select that skill/accommodation when the student next tries to schedule an appointment for the same subject as what the referral was created for. This requires additional configuration in your [[TracCloud:_Search_Availability_Options|Search Availability Widget settings]] to enable.
</div>
<hr>
<!--------------------------------------- Reasons and recommendations --------------------------------------->
<div style="float: left; margin-top: 0em; margin-bottom: 1em"><big><b>Reasons & Recommendations</b></big></div><div class="mw-collapsible mw-collapsed">
<br><br>
Reasons and Recommendations can be one of the most important aspects in creating these referrals, as these options can also dictate which emails get sent out to whom. Typically, these would be configured to allow your faculty to quickly describe where the student is struggling and what they recommend as a solution. However, since these are entirely customizable, you can ask any questions you can think of to help make the referral creation process as straightforward as possible.<br><br>

Click the <b>Add Reasons</b> / <b>Recommendations</b> box to add a new option. Setting a Reason/Recommendation as a "Label" will turn that item into a header for the following list, to help categorize your different options. By entering "(max: #)" with a number in place of #, you can limit how many choices can be made from the options following your header. For example, the label "Attendance (max: 1)" means only one of the following attendance-related reasons can be chosen during referral creation. These options can also be reorganized by dragging the hamburger icon ({{#fas:bars}}) on the right-side up/down.

[[File:2280863.png|900px]]<br><br>
</div>
<hr>
<!--------------------------------------- Custom Questions --------------------------------------->
<div style="float: left; margin-top: 0em; margin-bottom: 1em"><big><b>Custom Questions</b></big></div><div class="mw-collapsible mw-collapsed">
<br><br>
Custom questions allow you to add additional fields to your referrals. These questions can be formatted as a "Pulldown" menu with preset options, a small "Fill In" text box, or a larger "Essay" text field.

To create your custom question, click <b>Add New Question</b>.

[[File:5051253.png|600px]]<br><br>

* <b>Question Type</b> determines the question format. Pulldown (text box with preset options), Fill-in (small text field), or Essay (large text field).

* <b>Required</b> makes the question required to be filled out in order to save the referral.

* <b>Code Reference</b> is used to pull this information into your emails or for additional logic around what email content is sent. Typically, something short and unique like "GradeQuestion1."

* <b>Question</b> is the prompt itself, displayed to users when submitting this referral.

* <b>Choices</b> are the available response options, only applicable to Pulldown format questions. Put each choice on its own line.

* <b>Options</b> can be used for style overrides on the field label. If you aren't sure what to enter here, it should be left blank. Here is an example of what the above will look like in practice.
::[[File:23742374.png|400px]]
</div>
<hr>
<!--------------------------------------- Email Recipients --------------------------------------->
<div style="float: left; margin-top: 0em; margin-bottom: 1em"><big><b>Potential Email Recipients</b></big></div><div class="mw-collapsible mw-collapsed">
<br><br>
These are the possible recipients of alert emails relating to this referral. For example, if this referral's automated emails can be sent to students, then you will need to add students to the list, as seen in the screenshot below. The name of this field is only used for reference when choosing who will receive alerts when managing your automated emails, using the correct twig tag or entering a valid email is important.

[[File:5438124.png|900px]]<br><br>

* <b>Student: </b> <nowiki>{{Student.Email}}</nowiki>

* <b>Faculty: </b> <nowiki>{{Faculty.Email}}</nowiki>

* <b>Assigned Advisor/Other</b> <nowiki>{{Student.CustomData.cf_18}}</nowiki>
::Student Custom Fields can also be referred to here to pull email addresses, such as in the case of an Assigned Advisor. [[TracCloud:_Custom_Fields|More information.]]

* <b>Linked Consultant:</b> <nowiki>{{Consultant.Email}}</nowiki>

* <b>Specific email addresses can also be entered instead of twig tags.</b>
</div>
<hr>
<!--------------------------------------- Referral to Testing Center --------------------------------------->
<div style="float: left; margin-top: 0em; margin-bottom: 1em"><big><b>Referral to Testing Center</b></big></div><div class="mw-collapsible mw-collapsed">
<br><br>
This allows you to provide faculty the ability to book appointments for students that they're creating referrals for during the roster referral creation process. Typically used for Testing Centers or Lab environments, where faculty would need to book appointments on behalf of students, or assign multiple students to the same Group Availability.

[[File:8146523.png|900px]]<br><br>

* <b>Referral to Testing Center</b> enables this feature.

* <b>Book in Center</b> determines which center appears when faculty are searching for appointments on behalf of students.

* <b>Search Reason</b> determines which reason is used for the search availability process. Leave blank for all reasons.

* <b>Group Schedule Button Label</b> is the name of the button to search for availabilities.

* <b>Allow Single Appointments</b> provides faculty the ability to book sessions for students one at a time.

* <b>Allow Group Appointments</b> provides faculty the ability to select multiple students, and book a group availability for all at once.<br><br>

From the faculty perspective, there's a Schedule icon for each student in the roster referral listing, and/or the option to select multiple students and click "Book Testing Center Appointment" to schedule a group appointment for all selected students.

[[File:1969004.png|800px]]
</div>
<hr>
<!--------------------------------------- Potential Actions --------------------------------------->
<div style="float: left; margin-top: 0em; margin-bottom: 1em"><big><b>Potential Actions</b></big></div><div class="mw-collapsible mw-collapsed">
<br><br>

Potential Actions will be available in each submitted referral, with each action being available to add with a date and notes. These actions can be used to piece together a timeline of events relating to each referral and can additionally trigger automated emails.

[[File:6046618.png|600px]]<br><br>

Here's how this appears during referral creation. Each action can be added or re-added using the "Add New Completed Action" button. The text box can be resized by clicking-and-dragging the bottom-right corner.

[[File:3005704.png|600px]]

</div>
<hr>
<!--------------------------------------- Automated Emails --------------------------------------->
<div style="float: left; margin-top: 0em; margin-bottom: 1em"><big><b>Automated Emails & Twig</b></big></div><div class="mw-collapsible mw-collapsed">
<br><br>

The Automated Emails tab allows you to create custom emails that can be sent to one or more of your <i>Potential Email Recipients</i> upon referral submission, follow-up, or completion. Common examples might be an email that is sent to the student when a referral is created for them, with a separate email being sent to an assigned advisor or faculty. The recipients, number of emails, and email contents are up to you.

[[File:7163775.png|800px]]<br><br>

To create your first Email, click <b>Create New Email</b>, type in your subject line, then click Save. This will add the email to your Automated Emails listing. Click the Pencil Icon for the email you just created, and you should end up at a page like this.

[[File:6896918.png|800px]]<br><br>

* <b>Email Subject</b> determines the subject line of the email, as you entered previously. This can be changed at any time.

* <b>Email From</b> lets you change which email address this email is sent from. Uses system address if left blank.

* <b>Add Email Recipient</b> allows you to define which users could possibly receive a copy of this email, based on your <b>Potential Email Recipients.</b>

* <b>Email Sends On Referral Action Based Upon Selected Trigger(s)</b> allows you to decide under what context this email is sent. On initial creation, on follow-up, on completion, and on action completed. The first 3 are detailed further in the next portion of this article, the latter is detailed above.

* <b>Email Body</b> is the actual contents of your email.<br>

* <b>SMS Recipient</b> (Requires [[TracCloud:_TextAlerts|TextAlerts]])
::If you additionally want to send an SMS message along with this email, choose the recipient and write your message below. The "Consultant" choice will primarily use the consultant linked to the referral. If that field is blank, it will use the student's assigned advisor. If that isn't available, it will send the message to the consultant who created the referral.

==Twig==

One of the key elements of configuring your SAGE emails is Twig. Twig plays two key roles, providing tags for the information displayed, and adding logic to your email to determine what content is sent. Before reading this section, it's recommended to read the [[TracCloud:_Twig|Twig Guide]] to have a general understanding of how to write your emails with tags and conditions using Twig. A complete list of Twig tags can be found [[TracCloud:_Rosetta|here]]. 

Here's an example email. Note that arrays such as Reasons and Recommendations must be iterated over using the <i>for</i> tag in Twig.

<syntaxhighlight lang="twig">
Hello, {{Student.First_Name}}, this {{ReferralType.Name}} was submitted by {{Faculty.FirstName}}.

Here's why this alert was created:<br>
{% for item in Reasons %}
    {{item}} <br>
{% endfor %}<br>

Here's what we recommend:<br>
{% for key,value in Recommendations %}
    {{ value }}<br>
{% endfor %}<br>
</syntaxhighlight>

If you wanted to conditionally include text based on Reasons or Recommendations, you can do something like this.

<syntaxhighlight lang="twig">
{% if "Poor Attendance" in Reasons %}
    Online Tutoring is now available! See example.edu/remote/ for more information.
{% endif %}
</syntaxhighlight>

Another common case in SAGE emails is wanting to <b>not</b> send the email in certain cases. For this, you can use the special keyword <i>#ACTION:DO NOT SEND#</i>. Here's how that might look in practice. If the first statement is true, the entire email doesn't send.

<syntaxhighlight lang="twig">
{% if "No recommendations at this time" in Recommendations %}
    #ACTION:DO NOT SEND#
{% endif %}
</syntaxhighlight>

The rest of this section covers edge cases and additional examples. [[TracCloud:_SAGE_Email_Example|A more complete example of a SAGE email can be found here.]] You're welcome to take that and modify it for use in your system.

Another complicating factor in SAGE emails is custom questions and answers. These can be used emails, but you will need to use the "Code Reference" value that you set earlier. For example, if your Code Reference was "GradeQuestion," the format of this tag would be <nowiki>{{Questions.GradeQuestion}} and {{Answers.GradeQuestion}}</nowiki> for the question and answer respectively.

<syntaxhighlight lang="twig">
The answer to {{Questions.GradeQuestion}} was {{Answers.GradeQuestion}}.
</syntaxhighlight>

Here is a list of SAGE-specific Twig tags from [[TracCloud:_Rosetta|TracCloud Rosetta]].

{{#lst:TracCloud:_Rosetta|SAGE}}

Here are some additional unique tags and functions available in SAGE emails.

{| class="wikitable"
|-
| Trigger || The trigger for this email, “Created”, “Followed Up”, or “Processed”
|-
| Email.Subject || The contents of the email subject line
|-
| Questions.CODE || Questions.[Your custom question code]
|-
| Answers.CODE || Answers.[Your custom question code]
|-
| <nowiki>{{ setResultActions('AssignConsultant', '</nowiki><span style="color:red">123</span><nowiki>') }}</nowiki> || If this line is reached within a SAGE email, the assigned staff member will be changed to the specified sequence. The example below shows how you can use this script to link a student's assigned advisor to the referral.
|-
| || <nowiki>{% set staffSeq = getRecordFieldData('Staff','Email', Student.CustomData.cf_1,'Sequence') %}</nowiki><br><nowiki>
{{ setResultActions('AssignConsultant', staffSeq) }}</nowiki>
|-
| <nowiki>{{ setResultActions('SetProcessed', '1') }}</nowiki> || If this line is reached within an email, the referral will be marked as processed/completed.
|-
| <span style="white-space:nowrap;"><nowiki>{{ setResultActions('SetProcessedNotes', 'Example notes') }}</nowiki></span> || Typically used alongside the tag above. Used to automatically add notes to the processed referral.
|-
| <nowiki>{{NewCompletedActions[0].id}}</nowiki> || The ID of the most recently completed action. Only for use in emails with the "On Actions Completed" trigger.
|-
| <nowiki>{{NewCompletedActions[0].name}}</nowiki> || The name of the most recently completed action. Same use restriction as above.
|-
| <nowiki>{{NewCompletedActions[0].date}}</nowiki> || The date of the most recently completed action. Same use restriction as above.
|-
| <nowiki>{{NewCompletedActions[0].notes}}</nowiki> || The notes of the most recently completed action. Same use restriction as above.
|-
| <nowiki>{% for actions in Referral.CustomData.completedActions %}</nowiki><br><nowiki>{{actions.name}}</nowiki><br><nowiki>{% endfor %}</nowiki> || Use this to display every completed action of a referral. Replace 'name' with one of the other values above as needed.
|}

</div>
<hr>
<!--------------------------------------- Created,Follow-up,Processed --------------------------------------->
<div style="float: left; margin-top: 0em; margin-bottom: 1em"><big><b>Created, Followed Up, Processed</b></big></div><div class="mw-collapsible mw-collapsed">
<br><br>

In each automated email, you can determine when the email is sent based on a trigger. Created, Followed up, or Processed. Here's what each of those options mean in practice.<br><br>

<big>On Created</big><br>
Emails configured to send "On Created" will send the first time you hit the “Submit Referral” button at the bottom of a student referral or when a faculty member first submits a roster referral. This email type will only send automatically once during initial referral creation and can only be re-sent by using the <i>Override and Resend Referral Email</i> utility and selecting "Saved Referral" as the send option.

[[File:9766154.png|700px]]<br><br>

<big>On Followed-up</big><br>
Emails configured to send "On Followed Up" will send the first time data is saved in the "Follow Up Date" field. If this email type needs to be sent again for the same referral, the <i>Override and Resend Referral Email</i> utility must be with the "Followed Up" send option.

[[File:4742951.png|700px]]<br><br>

<big>On Processed</big><br>

Emails configured to send "On Processed" will send when the referral is marked as processed/completed/resolved (this phrasing may be configured differently for your system). This button will open a pop-up window to record additional information, the email sends when that pop-up is saved. Like the previous triggers, this email can only be resent by using <i>Override and Resend</i> with the "Processed" option.

[[File:3624980.png|700px]]

</div>
<hr>
<!--------------------------------------- Group Access --------------------------------------->
<div style="float: left; margin-top: 0em; margin-bottom: 1em"><big><b>Permission Group Options</b></big></div><div class="mw-collapsible mw-collapsed">
<br><br>
In order for staff members to view and/or edit referrals, they must be provided access in their permission group. This also gives you the ability to fine-tune what they can and can't do in relation to these referrals.

<span style="color:grey"><i>Other > Other Options > Groups > [The Group you want to modify] > Admin / Modules</i></span>
[[File:9621451.png|900px]]<br><br>

* <b>Allow user to view referrals on Dashboard</b> adds a utility to their dashboard allowing the staff member to quickly review/access relevant referrals.
::[[File:9749885.png|500px]]<br><br>

* <b>User may view which referrals</b> determines if they can view all referrals, or only their own.

* <b>User may DELETE which referrals</b> determines which referrals they're allowed to delete, all, their own, or none.

* <b>Referral Type Access</b> determines which referral types they can view. The icon within each entry can be clicked to cycle between <i>View and Edit</i> or just <i>View</i>. The former allows the user to view and edit referrals of this type, while the latter only allows them to view.<br><br>

To provide access to the referrals listing, add "Referrals" to table access as well. This is also required to give staff the ability to delete referrals.

[[File:5145633.png|900px]]

</div>
<hr>
==<b>Reports</b>==

There are three SAGE-specific reports available in TracCloud, each providing a different way to view your referral data. These reports can be found in the Navigation Bar, under <i>Reports > SAGE</i>.
<hr>
<div style="float: left; margin-top: 0em; margin-bottom: 1em"><big><b>SAGE Referral Snapshot</b></big></div><div class="mw-collapsible mw-collapsed">
<br><br>
{{:TracCloud_Report:_SAGE_Referral_Snapshot}}
</div>
<hr>
<div style="float: left; margin-top: 0em; margin-bottom: 1em"><big><b>SAGE Referrals by ??</b></big></div><div class="mw-collapsible mw-collapsed">
<br><br>
{{:TracCloud_Report:_SAGE_Referrals_by_%3F%3F}}
</div>
<hr>
<div style="float: left; margin-top: 0em; margin-bottom: 1em"><big><b>Referrals by Student and Appointments/Visits</b></big></div><div class="mw-collapsible mw-collapsed">
<br><br>
{{:TracCloud_Report:_Referrals_by_Student_and_Appointments/Visits}}
</div>
<hr>
For information on purchasing the SAGE Module, reach out to [mailto:sales@go-redrock.com sales@go-redrock.com]<br>
For SAGE functionality questions, reach out to [mailto:helpdesk@go-redrock.com helpdesk@go-redrock.com]

[[Category:TracCloud Manual]]
</div>