“When performance is measured, performance improves. When performance is measured and reported, the rate of improvement accelerates.”
Thomas S. Monson
Quality Assurance aims to prevent errors in student-agent interactions by establishing standards, processes, and procedures for consistent performance. Its ultimate goals are customer satisfaction, confidence building, and continual improvement. QA involves reviewing cases and providing feedback to ensure quality throughout interactions.
These are the criteria used for evaluating Quality Assurance for each resolved case.
FERPA Done Correctly
Confirm that the student's information is authenticated in our information system.
Perform a 3-step FERPA verification on every call interaction. All FERPA laws and BYU-Pathway Worldwide's confidentiality policies are not being violated.
Case Title is Unique and Relevant to the Question/Issue
When creating a new case, the case title must be concise and related to the case information.
If the case was created by another person or the system, the case title should NOT be edited.
Student Name, ID, and Contact Information Identified
Attach the correct student record as the customer.
Case Filled Out Completely for Anyone to Understand
Proper Spelling, Grammar, Capitalization, and Punctuation Used in All Interactions
Communicate with students in complete sentences.
Use correct punctuation, spelling, grammar, and capitalization.
Exclamation points may be used sparingly to show enthusiasm and emotion. Only one exclamation point at a time should be used. (e.g., "Congratulations!" instead of "Congratulations!!")
Font Size and Type Consistent Throughout Interactions
Use a font that is clear and understandable. (Do not use fonts such as Scriptina, Hobo, Papyrus, and Comic Sans.)
BYU-PW Programs and Systems Referred to Properly
BYU-Pathway Worldwide programs and systems are spelled in title case, such as the following terms.
Includes Appropriate Greeting and Closing, With Proper Empathy and Concern for the Student Shown Throughout
Use a brief professional greeting and a closing.
For the closing email, ensure that it is clear to the student that we are closing the case. Clarify that if they have more questions related to the same topic, they should reopen the case. For unrelated concerns, they should submit a new case/request.
Demonstrate Professionalism and a Proper Attitude While Using Common Courtesy
Do not use smiley faces, emoticons, emojis, and texting slang. (e.g., ya, IDK, TY, :), 😀,📌, ✅)
Avoid making unclear statements such as: maybe, possibly, I think
Do not use Pathway jargon and internal terms.
Do not send internal KB articles.
Include Signature on Written Communications
Include your name as an agent.
Include your team name. (If you are currently helping another team, use their team name.)
Include help.byupathway.edu
Gather Information Effectively to Obtain a Clear Understanding of the Student's Issue/Question Without Making Assumptions and Avoid Unnecessary Follow-Up
Help the Student in Their Selected Preferred Contact Method
Only the Technical Support Team can contact the student through WhatsApp.
If the Student is Non-responsive, Two More Verifiable Communication Attempts are Made Over a One-Week Period, and then the Case is Resolved with an Explanation to the Student.
A student will be considered Non-Responsive only if they fail to respond to any form of communication.
The Information Given is Correct, Concise, Relevant, Updated, and Based on KB Articles, Trainings, and/or Announcements.
Provide correct information according to KB articles and announcements.
Direct the student to the correct tool if needed.
Provide information that is relevant and helpful.
If the information is from an announcement, instructed by SL, or is not on any existing KB articles, indicate in the notes with supporting evidence.
All Stated Questions/Concerns are Fully Addressed, and Response is Clear, Concise, and Easy to Understand
Direct the instructions to the student and their concerns.
If the student has several questions in their case, respond to all questions included.
All Resources are Sent or Provided to Students as Promised (Links, Attachments, etc.)
Ensure that the links and attachments sent are working.
If another case was created, provide the case number and the team name the case was sent to.
Respond to the Student within 2 Business Days of the Case Being Picked or Assigned to them
Replies (Comments or Questions) from the Student, While the Case is Still Unresolved, are Responded to within 2 Business Days
Proactively address tasks with urgency and ensure case resolution without waiting for deadlines to hit.
If Necessary, Attempt to Contact the Student by Phone or Zoom to Speed Up the Resolution or Help Avoid Confusion
Never Allow More Than 3 Business Days to Go by Before Providing the Student with an Update, Unless Different Expectations were Set Clearly with the Student
Communicate the Reason for Any Delays or Work Being Done Internally to Resolve the Issue
Communicate When the Case is Transferred to Another Team, Including Which Team and Why
Detailed Notes About Interactions with the Student, Internal Staff, or Other Institutional Partners
Include notes in the Timeline section of the case for internal employees to see and understand what steps have taken place to resolve the case.
The notes should include updates, what interactions occurred, and supporting evidence. Add screenshots if they will help with future understanding of the student’s case.
All Interactions with the Student are Documented and Attached to the Case (Email, Phone Log, Voice Calls, Appointments)
Links to calls should be provided if they are not directly attached to the case.
Attach Related KB Articles to the Case or Let the SME Team Know When an Article Was Missing or Needed Updates
Use the correct KB Articles.
If the KB Article is missing or needs updates, add a note about giving feedback.
Only use KB articles labeled as “Published”. Do not use KB articles marked as "Restricted".
Select the Accurate Portal Products/Services
Follow All Other Established and Trained Case Handling Procedures.
Follow the procedures located in the KB articles and announcements.
Refer the student to the appropriate office or department if needed.
Follow the procedures for merging duplicate cases.
Ensure that all calls through the CRM are recorded.
Follow specific team procedures.
Do not send emails back to General Support or Advising.
Work only on cases you picked or were assigned to you.
These are the criteria used for evaluating Quality Assurance for each phone calls by the Phone Support team.
Criteria will be listed
Descriptions will be listed
Criteria will be listed
Descriptions will be listed
Criteria will be listed
Descriptions will be listed
Criteria will be listed
Descriptions will be listed
Criteria will be listed
Descriptions will be listed
Criteria will be listed
Descriptions will be listed
Criteria will be listed
Descriptions will be listed
Criteria will be listed
Descriptions will be listed
Criteria will be listed
Descriptions will be listed
These are recommended actions that the Quality Assurance Team (QA Team) suggests for providing the service. While Advisors might not be graded on these contents, it is still suggested that they follow these procedures closely.
1. When FERPA-protected information is given out, the email used to contact the student needs to be identical to the email listed in our system.
2. If a 3rd party contacts us on behalf of a student, a 3rd release form must be on file. This can be found within the student’s contact in the CRM. If there is NOT a 3rd party release form on file, you may only give out general program information.
1. Corresponding months should be disclosed when referring to semesters or terms. Months do not need to be disclosed in subsequent references. (e.g., Winter 2025 – Term 2 (March - April))
2. The word "glitch" should not be used.
3. Advisors should explain the terms "residency credits", "upper-division credits", and "GPA” when they use them for the first time with a student.
4. Avoid trigger words that use spammy language or excessive exclamation marks. (e.g., Hurry!! Act Now!)
5. Introduce yourself and BYU-Pathway Worldwide or your team in the first email you will send.
These Critical Violations are subject to change depending on the situation. It is advised that these violations be avoided, regardless.
Delayed Response: The Advisor failed to respond to the student within a reasonable timeframe, specifically within one week of the case being assigned.
Inappropriate Remarks: The Advisor made an inappropriate or unprofessional comment to the student.
Misassignment: The Advisor unnecessarily referred the student to another team, despite it being clear that this action was not appropriate or required.
Premature Case Resolution: The Advisor marked the case as "resolved" when the issue had not been fully addressed or resolved.
Failure to Deliver: The Advisor committed to taking specific actions (e.g., escalating a case) but failed to follow through on those commitments.
Each Advisor is graded for 3-5 resolved cases per month. These cases are picked randomly, and none of these cases are resolved on the same day.
The Support Leaders can access your QA scores through the CRM, and Advisors can reach out to them about the feedback and scores you receive.
To dispute for QA Feedback received, please use this link to the QA Dispute Form.