Within a student's data, you have the ability to add up to three different contacts. These can be parents, guardians, emergency contacts, or whoever you feel is needed. There is no requirement to use all three slots, or even any of the slots for contacts. However, it is recommended that at least one contact is provided in the event something comes up during transportation and we need to reach someone related to the student.


TABLE OF CONTENTS


Contact Groups

As mentioned, we have space for three different contacts in our system. We categorize them into three different types, but these are mostly guidelines and not something that needs to be strictly followed.

  1. Contact 1 ∙ Primary/Stopfinder Contact - We have a system called StopFinder which allows parents to look and see the scheduled route times for their child. Placing a parent or guardian into this field not only makes them the main contact in our system, but also allows links them to the student for StopFinder access if your district has this set up.
  2. Contact 2 ∙ Secondary Contact - This is another contact field, but whoever is listed as contact 2 is not set up for StopFinder access. Another parent or guardian is an ideal choice to put in the secondary contact section.
  3. Contact 3 ∙ Emergency Contact - The last set of contact fields is generally reserved for emergency contacts, in the event something goes wrong and we are unable to reach a primary or secondary contact on the list.


For the primary contact, an email address is needed to enable StopFinder access. Without the email address, the parent or guardian in question will not be able to access route times.


Having said that, here are all the fields we have available for contact information. These are the same for contacts 1, 2, and 3.


First and Last Name

REQUIRED FIELD ∙  The first and last name of the contact, respectively. To set up a contact, we will need these fields filled out.


Contact Type

How the contact is related to the student. Usually the mother or father, but other types can be entered based on their relationship.


Mobile

REQUIRED FIELD ∙ This does not have to be a mobile phone number, but should be the primary phone number for reaching the contact in question.


Address Fields

Used for the address of the contact. Address 1 is the home address. Address 2 is not a second address, but is used for apartment, suite, or room numbers. The city field is a selectable field to make sure the city matches what we have in the system. State and ZIP code are the state and ZIP code of the address in question. 


Email

REQUIRED FIELD (For primary contact) ∙  The email address used to reach the contact in question. For contacts 2 and 3, an email is not needed. Without this field entered, the system will not configure contact 1 for StopFinder access.


Notes

Contains useful information about the contact. For example, a common note added is that the parent may not speak English. This can be used for any other relevant information that does not fit into the other contact fields.