Canned Responses + SotW & Bonuses

Important Update About Canned Responses & Tags

As you know, with the release of Rubric 3.0 our tagging system has slightly changed. Not only have we added new tags like “Exceptional” and “Poor communication”, but we have also automated a few of our tags so they automatically are applied to certain sessions.

For example, using the canned response (known as “Auto Replies” on your tutor dashboard) for inappropriate behavior will automatically trigger our system to tag the session as ‘Inappropriate Behavior’ and block the student. Similarly, using the cheating canned response will automatically apply the “Cheating” tag to the session.

For this reason, it is extremely important that you are using canned responses when applicable so the appropriate tags are be applied. This means:

– Using the “Inappropriate Behavior” canned response when the student sends foul, threatening or sexual messages or images

– Using the “Cheating” canned response when a student admits to taking a non-practice test, exam or quiz.

SESSION OF THE WEEK

Congratulations to Session of the Week winner, Sejal Kothari! Nice work using a whiteboard example to break down the concept for the student, Sejal!

Nominate one of your own exceptional sessions via the submission form and you could win a $25 bonus!

PERFORMANCE BONUS RECIPIENTS

Congratulations to the following tutors who achieved a Top Ten tutor ranking for two or more consecutive weeks, earning them a $25 performance bonuses. Great work!

–   Partha Sarathi Reddy Kamireddy
–   Helen Herring
–   Namburi M Krishna Varma
–   Vaughan Leslie 

Happy tutoring!

— Team Yup

Updates to Speed Policies and Response Speed Reminder

Hello Tutors,

Thanks for your insightful feedback on our Response Speed Reminder!

The changes below are in response to your feedback, the “new normal” we’ve reached with messaging speed, and the emphasis we want to put on the speed policies rather than the Response Speed Reminder.

  • Starting the week of August 21st, your median tutor-to-student response time needs to be below 8 seconds, rather than 10 seconds, to earn a $25 bonus for the week. Your median tutor-to-anyone response time must be below 25 seconds, rather than 30, to avoid 2 infractions for the week.
  • Effective immediately, the Response Speed Reminder will appear two minutes, rather than 45 seconds, after your latest message.

You will not need to worry about these targets moving again for the foreseeable future. With these changes in place, we’ll be focusing much less on messaging speed and much more on instruction pace, which we’ve found to be a more pressing issue for most students. You can expect your Tutor Whiteboard, Canned Responses, and Review State to be improved and streamlined in the coming weeks. A couple last points:

  • Some key cases prevent us from being able to tie the Response Speed Reminder to the student’s messages rather than yours. For example, the student may repeatedly send messages like “Hello? Are you there?” which would prevent the tutor from receiving the warning.
  • For a sense of what your fellow tutors are thinking: roughly 80% of you responded that tutors should be sending a message every 15 to 45 seconds on average, which is in line with our general expectations of Tutor-To-Tutor messaging speed.

Keep up the great work,

Team Yup

 

NEW Tutor Rubric, Quality Assurance System, and Session Tags!

Good evening tutors,

We are thrilled to announce the launch of Tutor Rubric 3.0! 

Sessions will be graded according to Rubric 3.0 starting this coming Monday, August 7th. 

The new rubric shares many features with the last version, but includes new emphasis on instruction pace, responsiveness, teaching tools, and fostering a growth mindset in students.

Along with the new rubric, we are releasing Quality Assurance System 2.0. The redesigned system provides you with individual workbooks that let you see your performance, scheduling, and payment information all in one place. Each of you will be emailed a link to your individual QA 2.0 Workbook later this evening.

Finally, we’ve updated the Session Tags that tutors and TQMs apply to sessions after they’ve ended. Everything you need to know about these changes can be found in the following short documents.

Tutor Rubric 3.0

Guide to Tutor Rubric 3.0 and Session Tags

Guide to Your Tutor Workbook

Connecting Your Tutor Workbook

We ask that you familiarize yourself with the new Rubric, QA System, and Tags by this coming Monday. We’re excited to be starting another school year with all of you and want to hear any feedback you have on these changes over the coming weeks.

Thank you,

Team Yup

NEW Speed Policies and Features!

Why is speed so important?

As reported by students, speed is overwhelmingly the number one reason why they stop using our service. Many students tell us that they often find themselves waiting long periods of time to hear back from their tutors. Part of this has to do with the medium we’re using; when kids text each other, they expect immediate responses. With some minor changes in how we communicate, we can use this to our advantage to keep students more engaged.

How are we measuring speed?

If you’ve taken any sessions in the last few days, then you might have seen this bar in your Tutor Dashboard, which appears when at least 30 seconds have passed since you sent your last message:

If it shows up while you’re drawing on your whiteboard or waiting for your student to finish some work, don’t worry! This is just a reminder to be vigilant and periodically check in with your student. We will not be penalizing you just for letting this bar show up. We’ll soon be introducing policies that do depend on your response speed, though, so it’s important that you know how we measure it.

The feature above depends on how long it’s been since your last message; the new policies in the list below are linked to the time since your student’s last message or since anyone’s last message. In the future, we’ll refer to these last two values as your Tutor-To-Student (TTS) and Tutor-To-Anyone (TTA) response times.

When we calculate your TTS and TTA for a given week, we’ll use the median of these times, not the average, so that letting the student work alone every now and then won’t skew your data. For example, let’s say that your median TTA for a week is 15 seconds. This means that exactly half of your messages came more than 15 seconds after the previous one, and the other half came less than 15 seconds after.

What are the new speed policies?

Next Monday, July 17th, we’ll give you a way to see your median TTS and TTA from the previous week (meaning this current week). For each day of that week, we’ll also show you your median TTS and TTA for the day. The following Monday, July 24th, we’ll start holding everyone accountable for the following policies.

  1. Median TtS for a week is less than 10 seconds: $25 bonus
  2. Median TtA for a week is greater than 30 seconds: 2 infractions
  3. Any session contains a TtS response that took 5 minutes or more: Session refunded

Breaches of these last two policies are rare. Still, we are giving them real consequences to ensure that speed is a high priority in the coming months. We look forward to gathering your feedback on these policies in a few weeks’ time and continuing to refine them as we learn more. We’re fully aware that good explanations take time, but we’ve still found that several of our highest-performing tutors, including some whose native language isn’t English, have maintained a median TTS and TTA of under 10 seconds!

What are some strategies for increasing speed?

The following are some ideas to help you make sure that speed is never an issue. If you think of others, don’t hesitate to share!

  • Break messages into pieces. Be as brief as you can in each message while still being informative. When responding to interruptions and questions, send a short response immediately, then expand on it from there.
  • Explicitly acknowledge what the student has said. Try to use specific words or ideas that have recently shown up in the student’s messages. This helps them understand upcoming steps more quickly and creates a sense of continuous progress.
  • Reassure the student that you’re there. This is a good practice to follow in general and a simple way to avoid response times greater than 5 minutes. That said, you don’t need to check in every 15 seconds or so (which may actually annoy the student) because we use your median times and not your averages.

Keep up the great work,

Team Yup

Speed in Yup Sessions

Hello Tutors! Before your next session, please read and remember the tips below.

Two Types of Speed

The issue that unsatisfied Yup users bring to our attention most often is speed. We also want to stress that responding as quickly as possible and breaking up long messages into shorter ones is only half the battle!

We’ve found that there are really two key things that students mean when they mention speed. We’ll call them “typing speed” and “instruction speed.” Even if you respond immediately to every message, you could still be moving the session and the student’s understanding forward in a way that feels slow to the student. Concrete examples of this include lingering on topics that the student fully understands, asking about topics whose relevance isn’t clear at all to the student, and not pausing or adjusting guiding questions when the student is confused or discouraged.

Tips and Takeaways 

There’s always a way to move toward the solution with input from the student as long as you anchor your questions to what the student knows and stay attentive and encouraging. For example, if you’ve asked more than one guiding question in a row but the student hasn’t been able to answer them, you can always give a limited but helpful amount of information via simplified example problems, whiteboard drawings, or hinting at where the student should direct his or her attention next.

We and other tutors would love to hear about your experiences with session speed and what has helped you with this issue in past sessions. Feel free to discuss in the comments section below!

— Team Yup

Discussion: