Designed and developed exclusively for higher education admissions, Slate encompasses CRM, outreach, travel management, and online applications and reading.

Who Can Use Slate?

Staff in the various schools, departments, centers, programs, institutes, or other administrative entities who require the creation and management of an application process.

What Can We Do with Slate?

  • Contact Management: Tracking of contact information, associated fields, or touch points. This includes tracking prospective students, how they have interacted with the Admission office, their program(s) of interest, or for which term they are looking to apply.

  • Online Application: Creation of an online application and associated processes. As an example, Admissions Offices will have one or more applications where prospective students can apply for admission to a program. The online application comprises of various pages where information is collected or uploaded and then submitted for consideration.

  • Forms: Online forms that can be used in many ways. Admissions Offices use forms to gather information from prospects through a request-for-information form, or collect information through a registration form.

  • Events: Online Events including registration, check-in, and portals. As an example, Admission Offices will use events for campus visits, setting up interviews, or online events like webinars.

  • Online Reading: Review of application and materials. This process includes reviewing applications, materials submitted as part of an application, and also providing ratings, comments, or recommendations about applications through a review form.

  • Communications/Mailings/Letters: Sending of emails, letters, or text messages. As an example, Admissions Offices need to communicate to applicants that their applications have been received (email) and then once decisions are made, they need to communicate to applicants about those decisions (letters). In addition, contacts in the system can opt in for text messages and alerts regarding approaching deadlines or availability of decision letters.

  • Reporting: Creation of custom reports. Admission Offices need to report on things like yield (how many admitted students have deposited and matriculated). Reports can be created to include any relevant data categorized into groups (by program as an example), and then summarized and totaled (# counts or percentages). Reports can be defined and then run, printed, or emailed out. Reports can also be scheduled to run and emailed.

  • Queries: Creation of custom queries against data in the database. Queries are similar to reports, however, they are more detailed in the information that is returned based on fields, and filters, and queries and do not include summary data such as percentages or counts of specific fields.

  • Payment Processing: Secure PCI-compliant processing of application fees, deposits, or registration fees. As an example, Admissions offices need to collect fees once an application is submitted.

  • Interfaces: As with any system, interfaces need to be developed to feed information to other systems. Extracts can be developed from the system in order to feed data manually, or via secure connections. Admission Offices will receive an application, make a decision, and admit students. These admitted students will now need to be in the Student Information System in order to register for courses, so an interface is built to ensure that data is available in multiple systems.