MatchCraft Feed Processing

Owned by Brenton Rose
Jun 14, 2022
1 min read

 

All tickets are triggered from an email source

·      hootautoinventoryenrollment@matchcraft.com

 

Additional Contacts (These contacts should be added if not on the original request)

·      Juvenal Fernandez juvenal.fernandez@matchcraft.com

·      Adam Edmonds adam.edmonds@matchcraft.com

·      Christina Canary christina.canary@matchcraft.com

 

Special Instructions should always include:

Please include vehicles with no price on the website and set the price column to $1.00

 

Overview

The tickets are intended to request the creation of new advertisers and to enable the display feed feature. Once the new advertiser is created, advertiser is configured, and feeds are ready for use we must notify the client and include the Facebook Automotive feed URL.

  • Ticket is received from hootautoinventoryenrollment@matchcraft.com

  • Client will receive confirmation email containing the description and ticket number

  • CS Representative should Claim (Assign) the ticket

  • CS Rep must review the ticket for accuracy and completeness. Should there be any questions, please comment on the ticket and await response (Change Status to Waiting for Customer)

  • Once you are ready to start creating the new advertiser update ticket status to “In Progress”. This status change turns off Jira notifications.

  • Create the advertiser inside the Hoot application

  • Dev will receive the ticket and complete configuration

  • The CS Representative who submitted the advertiser will receive an email confirming the configuration was completed.

  • CA representative should review the feed for accuracy

    • Verify number of vehicle sin feed aligns with website

      • New & Used

    • Review prices in feed vs website

    • Check “URL” that it lands on correct website

  • Resolve ticket (Include the Facebook Automotive Feed Link in the resolution notes) This transition should re-enable client notifications.

  • Close Ticket