A: Your notes should consist of issues you want to raise to the client and general notes for the team. You should list out any important details in the Notes field.
Client style guides in most cases will contain more specific and detailed instructions on both WHEN and HOW to leave transcription notes. If you are still uncertain, read along for general tips. If you are still unsure after both readings, reach out to a pod lead!
Notes should be left only for critical information, such as:
removal of items without pricing
missing options
etc.
This does not include general notes such as: correcting casing, updating min/max, etc. Always ensure it is clear who your notes are intended for, and that they are delivered to the correct recipient.
When leaving notes for a Client, it is also important to consider their perspective and the tone that you are using with them. Be sure to type messages in short, clear, and professional language. Make sure that you do not mention internal terms like:
V8
Client code names
Internal tools like MyHours or Discord
For general client communication guidance, please refer to the v8 Comms Guidance Sheet.
Take a look at the chart below for some common issues that should be flagged to the client and how your notes should be structured. Please be sure to refer to the client-specific style guide to make sure you're not missing anything.
Notes to Client:
Issue | Potential Reason | Example |
|
|
|
|
|
|
|
|
|
|
|
|