Thursday, October 25, 2012

[G] Introducing the Manage Inquiries tab for advertisers

| More

Google Affiliate Network: Introducing the Manage Inquiries tab for advertisers

Many savvy shoppers shop online through loyalty and reward programs, since their purchases can lead to incentives like miles, points, or other reward-based currencies (typically referred to as a passback).

As an advertiser, you know how important it is to make sure customers are satisfied with their purchases. If they shop through loyalty programs, you also know how it’s important that they receive their passback. To that end, you may sometimes be contacted by loyalty publishers' customer service teams asking to confirm orders for customers who may not have received their passback. To ease this process, we've released the new Manage Inquiries tab to streamline the order lookup and resolution process so you can quickly review and take action on inquiries.

The Manage Inquiries tab shows all pending order inquiries, and publishers are able to supply the loyalty member ID as well as add any notes to help you review and take action on the inquiry. You’ll also receive a weekly notification email if a publisher has added an inquiry to your account.

Reviewing inquiries
You can start reviewing inquiries by taking the following steps:
  1. Click on the Orders tab, then the Manage Inquiries sub-tab.
  2. Review the list of Pending inquiries.
  3. Review your own reporting to decide whether or not the inquiry is already associated with a valid order.
  4. Click on the Action drop-down and take the appropriate action on the inquiry. You can select the order and approve it as-is, or edit the order amount and approve, or decline the inquiry. You can also use the “select all” function to take action on multiple inquiries at once.
If you have a large number of inquiries, you can save time by exporting them to .csv, specifying the actions in the file and uploading it to the interface.

Learn more about managing pending order inquiries in the Help Center.

Posted by:

Gabe Black, Software Engineer
Mark St. John, Software Engineer

No comments: