

Your partner
in the student
housing experience
Your partner
in the student
housing experience
Your partner in the student housing experience
See a Demo
See a Demo
Blog /
Customer Stories
Seconds, Not Days: Inside SUNY JCC’s Housing Help Desk
Seconds, Not Days: Inside SUNY JCC’s Housing Help Desk

Team Housing.Cloud
Team Housing.Cloud
Auto-routed tasks, prioritized notifications, and a single source of truth for student requests
At SUNY Jamestown Community College (SUNY JCC), Director of Residence Life Tyler Silagyi has built a housing help desk designed for how students actually live today: mobile, fast, and transparent.
When a student submits a housing request, it lands directly with the staff member who can resolve it. Profile changes go to Tyler. Roommate and suite issues route to the assigned Residence Director. Notifications arrive in a priority inbox folder. Many requests close in seconds.
That kind of responsiveness reflects what JCC has always prioritized for its on-campus residents: a relationship-driven community where students can focus on learning and growth. Housing.Cloud is the platform Tyler chose to make that responsiveness the default, not the exception.
“It could be a day or more for a request to be seen, versus a task that gets done in seconds because it’s automatically going right to the person it needs to get to.”
—
Tyler Silagyi
Director of Residence Life, SUNY JCC


SUNY JCC serves a close-knit residential community where relationship-driven living defines the on-campus experience. The college’s suite-style residence halls give students private sleeping spaces alongside the responsibility of managing their own cooking and cleaning. The halls have brought a meaningful vibrancy to campus and have made it possible to enroll international students and students from across the country who might not otherwise find their way to a small community in western New York. Tyler’s decade in the role has been shaped by that student-first culture, and his approach to modernization has been guided by it too.
How It Works at JCC
Three steps. One system. Nothing gets lost.
STEP 1 Student Submits a Request Students submit housing requests directly through Housing.Cloud, rather than emailing a general inbox or stopping by the office. | STEP 2 Request Becomes a Task Each request auto-routes to the right owner based on category. Profile changes to Tyler. Roommate issues to the assigned RD. Clear ownership from the start. | STEP 3 Resolved and Followed Through Staff resolve the request directly inside Housing.Cloud, tied to the student profile. No system-switching, no context loss. |
That workflow represents a deliberate evolution for Tyler’s team. When JCC first signed on with Housing.Cloud, the team was operating the way most higher ed housing teams have long operated: through email. Tyler saw an opportunity to build something more responsive for students and more sustainable for his team.
“Really everything before Housing Cloud was fully manual. Everything was coming through email.”
—
Tyler Silagyi
Director of Residence Life, SUNY JCC


Where Tyler’s Team Gets Time Back
Tyler’s operation gains time at three layers. Each builds on the next.
Layer of improvement | Starting point | Where Tyler’s team operates today |
1. Request resolution speed | Requests arrived through a general email inbox and required manual triage to reach the right owner | Requests auto-route to the right owner with a priority notification; many close in seconds |
2. Delegation overhead | Tyler served as the triage point for inbound requests, routing each to the correct RD | Requests are auto-assigned by category; the delegation step happens automatically |
3. Number of surfaces to manage | Requests arrived through email, Starfish, and in-person visits, three surfaces the team tracked together | One system, tied into Active Directory; searches and context live in one place |
1. Request resolution speed
The most visible improvement: a request that used to require triage before reaching the right owner now lands with them directly. Priority notifications make the difference. Housing.Cloud pings arrive in a dedicated folder, so they stay visible even on a busy inbox day.
“When I see Housing.Cloud notifications, someone’s looking for something specific with my group of students that I need to make sure has a good experience.”
—
Tyler Silagyi
Director of Residence Life, SUNY JCC


2. Delegation overhead
Tyler used to serve as the triage point for nearly every housing inbound. Auto-assignment by category now handles that work, so requests reach the right residence director the moment they’re submitted. The result is immediate ownership, without requiring Tyler in the middle.
“There’s not really that lead time between when the student wants something and when we find it.”
—
Tyler Silagyi
Director of Residence Life, SUNY JCC


3. Number of surfaces to manage
Requests that arrived through email, Starfish, and in-person visits now live in one system.
“It is nice having things in one spot versus 'oh, you sent me an email, or you sent me a Starfish, or I stopped in.' Everything is nicely knit in Housing Cloud.”
—
Tyler Silagyi
Director of Residence Life, SUNY JCC


Together, these three layers are what Tyler describes when he talks about the time his team has gained. No single number captures it. The pattern does.
Next Up: A Modern Visitor Check-In
JCC’s current visitor process reflects the care the team puts into guest safety and accountability. RAs and student workers staff the desk from 9pm to 3am every night, recording guest information on both paper forms and a digital backup so Tyler has a searchable record if something needs review later.
Tyler’s team decided to bring on the Visitors Management product from Housing.Cloud and is running it in parallel this spring, with the goal of fully launching in the fall. The approach is thoughtful: test alongside the existing process, gather feedback, refine, then roll out broadly once the team is confident.
What’s already resonating
Photo capture for guests and IDs at check-in, useful for accurate records and for consulting law enforcement if an incident occurs
Centralized, searchable visitor data that brings disconnected records into one place
Guest requests submitted in advance, which lets staff identify who may already be in a building when visitation hours begin
“With the Housing Cloud Visitor Management tool, we can take a picture of the guest and their ID at check-in. If we ever have an issue that requires us to consult law enforcement, the information is right there.”
—
Tyler Silagyi
Director of Residence Life, SUNY JCC


A Platform That Prompts Better Process
For Tyler, Housing.Cloud has become more than a tool for running housing. It’s a thought partner. Ongoing conversations with the Housing.Cloud team consistently surface new ways to rethink existing workflows.
“That’s another benefit for me with Housing.Cloud: it helps me question and reflect on what we’re doing and why.”
—
Tyler Silagyi
Director of Residence Life, SUNY JCC


A recent example: when Tyler discussed room change requests with his Housing.Cloud contact, the conversation shifted from “how do I build a form for this” to “how do I build a form that helps the student reflect on the decision before submitting.” That reframing turned a data-collection task into a student-development moment.
He’s also exploring a redirect task for facilities requests (JCC’s facilities team uses a separate work order system), which would route students automatically to the right system and skip the manual hand-off.
Student Autonomy as a Selling Point
A core reason Tyler invested in modernization was his belief that students should shape their own residential experience. Until a summer cutoff each year, JCC students choose where they live and with whom. That autonomy is a meaningful selling point when Tyler meets with prospective students.
“I really wanted students to create their own experience. It’s a huge selling point when we tell them, you’re taking a lot of decisions into your own hands.”
—
Tyler Silagyi
Director of Residence Life, SUNY JCC


There’s a practical benefit on the back end as well. When roommate issues arise later, Tyler can look inside Housing.Cloud to see who chose whom, which grounds the conversation in context rather than starting from scratch.
Looking Ahead
JCC’s housing operation has grown with Housing.Cloud. Tyler’s philosophy, that “Housing.Cloud could become more like social media that students use year-round,” hints at where he’d like to take it next.
Tasks are the backbone. Visitor management is the next layer. And an ongoing cadence of reflection with the Housing.Cloud team keeps uncovering new ways to make the student and staff experience sharper.
For housing leaders thinking about modernizing their own help desk, JCC’s path offers a clear template: clear owner from the start, one system instead of several, and a platform that grows alongside the team using it.
Auto-routed tasks, prioritized notifications, and a single source of truth for student requests
At SUNY Jamestown Community College (SUNY JCC), Director of Residence Life Tyler Silagyi has built a housing help desk designed for how students actually live today: mobile, fast, and transparent.
When a student submits a housing request, it lands directly with the staff member who can resolve it. Profile changes go to Tyler. Roommate and suite issues route to the assigned Residence Director. Notifications arrive in a priority inbox folder. Many requests close in seconds.
That kind of responsiveness reflects what JCC has always prioritized for its on-campus residents: a relationship-driven community where students can focus on learning and growth. Housing.Cloud is the platform Tyler chose to make that responsiveness the default, not the exception.
“It could be a day or more for a request to be seen, versus a task that gets done in seconds because it’s automatically going right to the person it needs to get to.”
—
Tyler Silagyi
Director of Residence Life, SUNY JCC


SUNY JCC serves a close-knit residential community where relationship-driven living defines the on-campus experience. The college’s suite-style residence halls give students private sleeping spaces alongside the responsibility of managing their own cooking and cleaning. The halls have brought a meaningful vibrancy to campus and have made it possible to enroll international students and students from across the country who might not otherwise find their way to a small community in western New York. Tyler’s decade in the role has been shaped by that student-first culture, and his approach to modernization has been guided by it too.
How It Works at JCC
Three steps. One system. Nothing gets lost.
STEP 1 Student Submits a Request Students submit housing requests directly through Housing.Cloud, rather than emailing a general inbox or stopping by the office. | STEP 2 Request Becomes a Task Each request auto-routes to the right owner based on category. Profile changes to Tyler. Roommate issues to the assigned RD. Clear ownership from the start. | STEP 3 Resolved and Followed Through Staff resolve the request directly inside Housing.Cloud, tied to the student profile. No system-switching, no context loss. |
That workflow represents a deliberate evolution for Tyler’s team. When JCC first signed on with Housing.Cloud, the team was operating the way most higher ed housing teams have long operated: through email. Tyler saw an opportunity to build something more responsive for students and more sustainable for his team.
“Really everything before Housing Cloud was fully manual. Everything was coming through email.”
—
Tyler Silagyi
Director of Residence Life, SUNY JCC


Where Tyler’s Team Gets Time Back
Tyler’s operation gains time at three layers. Each builds on the next.
Layer of improvement | Starting point | Where Tyler’s team operates today |
1. Request resolution speed | Requests arrived through a general email inbox and required manual triage to reach the right owner | Requests auto-route to the right owner with a priority notification; many close in seconds |
2. Delegation overhead | Tyler served as the triage point for inbound requests, routing each to the correct RD | Requests are auto-assigned by category; the delegation step happens automatically |
3. Number of surfaces to manage | Requests arrived through email, Starfish, and in-person visits, three surfaces the team tracked together | One system, tied into Active Directory; searches and context live in one place |
1. Request resolution speed
The most visible improvement: a request that used to require triage before reaching the right owner now lands with them directly. Priority notifications make the difference. Housing.Cloud pings arrive in a dedicated folder, so they stay visible even on a busy inbox day.
“When I see Housing.Cloud notifications, someone’s looking for something specific with my group of students that I need to make sure has a good experience.”
—
Tyler Silagyi
Director of Residence Life, SUNY JCC


2. Delegation overhead
Tyler used to serve as the triage point for nearly every housing inbound. Auto-assignment by category now handles that work, so requests reach the right residence director the moment they’re submitted. The result is immediate ownership, without requiring Tyler in the middle.
“There’s not really that lead time between when the student wants something and when we find it.”
—
Tyler Silagyi
Director of Residence Life, SUNY JCC


3. Number of surfaces to manage
Requests that arrived through email, Starfish, and in-person visits now live in one system.
“It is nice having things in one spot versus 'oh, you sent me an email, or you sent me a Starfish, or I stopped in.' Everything is nicely knit in Housing Cloud.”
—
Tyler Silagyi
Director of Residence Life, SUNY JCC


Together, these three layers are what Tyler describes when he talks about the time his team has gained. No single number captures it. The pattern does.
Next Up: A Modern Visitor Check-In
JCC’s current visitor process reflects the care the team puts into guest safety and accountability. RAs and student workers staff the desk from 9pm to 3am every night, recording guest information on both paper forms and a digital backup so Tyler has a searchable record if something needs review later.
Tyler’s team decided to bring on the Visitors Management product from Housing.Cloud and is running it in parallel this spring, with the goal of fully launching in the fall. The approach is thoughtful: test alongside the existing process, gather feedback, refine, then roll out broadly once the team is confident.
What’s already resonating
Photo capture for guests and IDs at check-in, useful for accurate records and for consulting law enforcement if an incident occurs
Centralized, searchable visitor data that brings disconnected records into one place
Guest requests submitted in advance, which lets staff identify who may already be in a building when visitation hours begin
“With the Housing Cloud Visitor Management tool, we can take a picture of the guest and their ID at check-in. If we ever have an issue that requires us to consult law enforcement, the information is right there.”
—
Tyler Silagyi
Director of Residence Life, SUNY JCC


A Platform That Prompts Better Process
For Tyler, Housing.Cloud has become more than a tool for running housing. It’s a thought partner. Ongoing conversations with the Housing.Cloud team consistently surface new ways to rethink existing workflows.
“That’s another benefit for me with Housing.Cloud: it helps me question and reflect on what we’re doing and why.”
—
Tyler Silagyi
Director of Residence Life, SUNY JCC


A recent example: when Tyler discussed room change requests with his Housing.Cloud contact, the conversation shifted from “how do I build a form for this” to “how do I build a form that helps the student reflect on the decision before submitting.” That reframing turned a data-collection task into a student-development moment.
He’s also exploring a redirect task for facilities requests (JCC’s facilities team uses a separate work order system), which would route students automatically to the right system and skip the manual hand-off.
Student Autonomy as a Selling Point
A core reason Tyler invested in modernization was his belief that students should shape their own residential experience. Until a summer cutoff each year, JCC students choose where they live and with whom. That autonomy is a meaningful selling point when Tyler meets with prospective students.
“I really wanted students to create their own experience. It’s a huge selling point when we tell them, you’re taking a lot of decisions into your own hands.”
—
Tyler Silagyi
Director of Residence Life, SUNY JCC


There’s a practical benefit on the back end as well. When roommate issues arise later, Tyler can look inside Housing.Cloud to see who chose whom, which grounds the conversation in context rather than starting from scratch.
Looking Ahead
JCC’s housing operation has grown with Housing.Cloud. Tyler’s philosophy, that “Housing.Cloud could become more like social media that students use year-round,” hints at where he’d like to take it next.
Tasks are the backbone. Visitor management is the next layer. And an ongoing cadence of reflection with the Housing.Cloud team keeps uncovering new ways to make the student and staff experience sharper.
For housing leaders thinking about modernizing their own help desk, JCC’s path offers a clear template: clear owner from the start, one system instead of several, and a platform that grows alongside the team using it.
#StudentHousing
#ResLife
#EdTech
#HousingManagement
#StudentAffairs
#CampusOperations
Your partner in the student housing experience
See a Demo
Auto-routed tasks, prioritized notifications, and a single source of truth for student requests
At SUNY Jamestown Community College (SUNY JCC), Director of Residence Life Tyler Silagyi has built a housing help desk designed for how students actually live today: mobile, fast, and transparent.
When a student submits a housing request, it lands directly with the staff member who can resolve it. Profile changes go to Tyler. Roommate and suite issues route to the assigned Residence Director. Notifications arrive in a priority inbox folder. Many requests close in seconds.
That kind of responsiveness reflects what JCC has always prioritized for its on-campus residents: a relationship-driven community where students can focus on learning and growth. Housing.Cloud is the platform Tyler chose to make that responsiveness the default, not the exception.
“It could be a day or more for a request to be seen, versus a task that gets done in seconds because it’s automatically going right to the person it needs to get to.”
—
Tyler Silagyi
Director of Residence Life, SUNY JCC


SUNY JCC serves a close-knit residential community where relationship-driven living defines the on-campus experience. The college’s suite-style residence halls give students private sleeping spaces alongside the responsibility of managing their own cooking and cleaning. The halls have brought a meaningful vibrancy to campus and have made it possible to enroll international students and students from across the country who might not otherwise find their way to a small community in western New York. Tyler’s decade in the role has been shaped by that student-first culture, and his approach to modernization has been guided by it too.
How It Works at JCC
Three steps. One system. Nothing gets lost.
STEP 1 Student Submits a Request Students submit housing requests directly through Housing.Cloud, rather than emailing a general inbox or stopping by the office. | STEP 2 Request Becomes a Task Each request auto-routes to the right owner based on category. Profile changes to Tyler. Roommate issues to the assigned RD. Clear ownership from the start. | STEP 3 Resolved and Followed Through Staff resolve the request directly inside Housing.Cloud, tied to the student profile. No system-switching, no context loss. |
That workflow represents a deliberate evolution for Tyler’s team. When JCC first signed on with Housing.Cloud, the team was operating the way most higher ed housing teams have long operated: through email. Tyler saw an opportunity to build something more responsive for students and more sustainable for his team.
“Really everything before Housing Cloud was fully manual. Everything was coming through email.”
—
Tyler Silagyi
Director of Residence Life, SUNY JCC


Where Tyler’s Team Gets Time Back
Tyler’s operation gains time at three layers. Each builds on the next.
Layer of improvement | Starting point | Where Tyler’s team operates today |
1. Request resolution speed | Requests arrived through a general email inbox and required manual triage to reach the right owner | Requests auto-route to the right owner with a priority notification; many close in seconds |
2. Delegation overhead | Tyler served as the triage point for inbound requests, routing each to the correct RD | Requests are auto-assigned by category; the delegation step happens automatically |
3. Number of surfaces to manage | Requests arrived through email, Starfish, and in-person visits, three surfaces the team tracked together | One system, tied into Active Directory; searches and context live in one place |
1. Request resolution speed
The most visible improvement: a request that used to require triage before reaching the right owner now lands with them directly. Priority notifications make the difference. Housing.Cloud pings arrive in a dedicated folder, so they stay visible even on a busy inbox day.
“When I see Housing.Cloud notifications, someone’s looking for something specific with my group of students that I need to make sure has a good experience.”
—
Tyler Silagyi
Director of Residence Life, SUNY JCC


2. Delegation overhead
Tyler used to serve as the triage point for nearly every housing inbound. Auto-assignment by category now handles that work, so requests reach the right residence director the moment they’re submitted. The result is immediate ownership, without requiring Tyler in the middle.
“There’s not really that lead time between when the student wants something and when we find it.”
—
Tyler Silagyi
Director of Residence Life, SUNY JCC


3. Number of surfaces to manage
Requests that arrived through email, Starfish, and in-person visits now live in one system.
“It is nice having things in one spot versus 'oh, you sent me an email, or you sent me a Starfish, or I stopped in.' Everything is nicely knit in Housing Cloud.”
—
Tyler Silagyi
Director of Residence Life, SUNY JCC


Together, these three layers are what Tyler describes when he talks about the time his team has gained. No single number captures it. The pattern does.
Next Up: A Modern Visitor Check-In
JCC’s current visitor process reflects the care the team puts into guest safety and accountability. RAs and student workers staff the desk from 9pm to 3am every night, recording guest information on both paper forms and a digital backup so Tyler has a searchable record if something needs review later.
Tyler’s team decided to bring on the Visitors Management product from Housing.Cloud and is running it in parallel this spring, with the goal of fully launching in the fall. The approach is thoughtful: test alongside the existing process, gather feedback, refine, then roll out broadly once the team is confident.
What’s already resonating
Photo capture for guests and IDs at check-in, useful for accurate records and for consulting law enforcement if an incident occurs
Centralized, searchable visitor data that brings disconnected records into one place
Guest requests submitted in advance, which lets staff identify who may already be in a building when visitation hours begin
“With the Housing Cloud Visitor Management tool, we can take a picture of the guest and their ID at check-in. If we ever have an issue that requires us to consult law enforcement, the information is right there.”
—
Tyler Silagyi
Director of Residence Life, SUNY JCC


A Platform That Prompts Better Process
For Tyler, Housing.Cloud has become more than a tool for running housing. It’s a thought partner. Ongoing conversations with the Housing.Cloud team consistently surface new ways to rethink existing workflows.
“That’s another benefit for me with Housing.Cloud: it helps me question and reflect on what we’re doing and why.”
—
Tyler Silagyi
Director of Residence Life, SUNY JCC


A recent example: when Tyler discussed room change requests with his Housing.Cloud contact, the conversation shifted from “how do I build a form for this” to “how do I build a form that helps the student reflect on the decision before submitting.” That reframing turned a data-collection task into a student-development moment.
He’s also exploring a redirect task for facilities requests (JCC’s facilities team uses a separate work order system), which would route students automatically to the right system and skip the manual hand-off.
Student Autonomy as a Selling Point
A core reason Tyler invested in modernization was his belief that students should shape their own residential experience. Until a summer cutoff each year, JCC students choose where they live and with whom. That autonomy is a meaningful selling point when Tyler meets with prospective students.
“I really wanted students to create their own experience. It’s a huge selling point when we tell them, you’re taking a lot of decisions into your own hands.”
—
Tyler Silagyi
Director of Residence Life, SUNY JCC


There’s a practical benefit on the back end as well. When roommate issues arise later, Tyler can look inside Housing.Cloud to see who chose whom, which grounds the conversation in context rather than starting from scratch.
Looking Ahead
JCC’s housing operation has grown with Housing.Cloud. Tyler’s philosophy, that “Housing.Cloud could become more like social media that students use year-round,” hints at where he’d like to take it next.
Tasks are the backbone. Visitor management is the next layer. And an ongoing cadence of reflection with the Housing.Cloud team keeps uncovering new ways to make the student and staff experience sharper.
For housing leaders thinking about modernizing their own help desk, JCC’s path offers a clear template: clear owner from the start, one system instead of several, and a platform that grows alongside the team using it.
#StudentHousing
#ResLife
#EdTech
#HousingManagement
#StudentAffairs
#CampusOperations
Related post
Related post
Student-Led Room Selection Drove Applications Earlier Than Ever
How to Audit Your Housing Application Process in 20 Minutes
Modernizing Housing Operations With a Sustainable Path Forward
Digital Transformation on a Deadline: How Lehigh University Modernized Housing Mid-Year
Supporting Student Persistence Through Improved Housing Communication
Commitment to Security & Accessibility
We believe every student and staff member deserves a secure, accessible experience — that commitment is built into the platform.
Commitment to Security & Accessibility
We believe every student and staff member deserves a secure, accessible experience — that commitment is built into the platform.
Commitment to Security & Accessibility
We believe every student and staff member deserves a secure, accessible experience — that commitment is built into the platform.

Service Organization
Control Type II
SOC 2 Type II
SOC 2 Type II
SOC 2
Type II
Compliant
Compliant
Compliant
Cybersecurity

Service Organization
Control Type II
SOC 2
Type II
Compliant
Cybersecurity

Service Organization
Control Type II
SOC 2 Type II
Compliant
Cybersecurity

Web Content Accessibility
Guidelines Level AA
WCAG 2.1 AA
WCAG 2.1 AA
Compliant
Compliant
Compliant
VPAT Ready
Voluntary Product Accessibility Template
(Section 508)

Web Content Accessibility
Guidelines Level AA
WCAG 2.1 AA
Compliant
VPAT Ready
Voluntary Product Accessibility Template
(Section 508)

Web Content Accessibility
Guidelines Level AA
WCAG 2.1 AA
Compliant
VPAT Ready
Voluntary Product Accessibility Template
(Section 508)

Education
Technology 2023
Gold Winner
Top Student Engagement Solutions Provider
Top Student Engagement Solutions Provider
Top Student Engagement Solutions Provider

Education
Technology 2023
Gold Winner
Top Student Engagement Solutions Provider

Education
Technology 2023
Gold Winner






