Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current Restore this Version View Page History

Version 1 Next »

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.

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.

 If the request duplicates content that already exists

Check the dealer folder or Content History Sheet in the client sheet before beginning to fill a request and make sure it’s not a duplicate.

  • There are two types of duplicates you may encounter:

    • Hard duplicates: The request exactly matches content that already exists for the dealer

    • Soft duplicates: The request doesn’t look like a duplicate based on the title, but all content that would be covered is already covered in a different piece

      • ATV Hunting Accessories vs UTV Hunting Accessories

      • Travel Trailer Maintenance vs Fifth Wheel Maintenance

 If the request is too challenging, technical, vague, or obscure