This document provides a breakdown of the kickback process for content, including common issues and the full process from start to finish.
Official Kickback Disclaimer
Some content requests the team receives provide insufficient information to start or complete the requested content. As a general rule, if the team or an individual writer cannot complete a request for any reason, then the writer is within their rights to kick the request back to the reps. A writer is within their rights to kick back a request at any point during fulfillment, no matter how much work they’ve already put into the piece.
Writers are encouraged to kick back content requests the moment they realize the request is impossible to complete as-is or would take an inordinate amount of time to fill.
Common Kickback Reasons
Whether or not a card needs to be kicked back is largely up to the discretion of the writer tackling the request, however there are some more common errors that come up that should be automatic red flags.
The Kickback Process
When an issue is identified, writers should complete the following steps:
Note on Contacting Reps Directly
In some cases, it may be faster to directly contact the SEO about a point of confusion. These will still need to be recorded in the Kickback Sheet. Check the “Not Official KB” box in column J for these kickbacks.
If attempting to quickly resolve an issue has the opposite effect it’s intended to have, the writer may turn it into an official kickback or escalate the situation to the Content Team Lead (Amanda Kelner). Alternatively, the writer may also contact the rep’s pod lead if the issue indicates a comprehensive retraining is in order.