Last updated on September 20th, 2021
We have a partner scoring matrix against which a
Each partner is given a score from 1 - 6 across the following 8 core categories;
While we aim for full publication on all platforms, we know that isn't always the case when dealing with so many different partners and such a high volume of customer data. We have monthly meetings with most of our Tier 1 partners to discuss operational performance. At these meetings, we will address errors at scale and identify solutions to publication issues at scale. For Tier A customer issues at scale, we will have a shared work document to address ad-hoc publication issues reported through Jira.
These partners tend to be applicable for particular regions or verticals, for the most part, these partners tend to have the highest costs to Uberall. We try to ensure we connect in the most meaningful way at the point of implementation and maintain that connection for the duration of the relationship. We work to resolve bugs that are caused by our end using our established prioritization logic and customer tagging in JIRA. We report bugs on the partner's side through the shared reporting document.
We have quarterly meetings with most of our Tier 2 partners to discuss and optimize operational performance. At these meetings, we will address errors at scale and identify solutions to publication issues at scale.
These partners are, for the most part, extended longtail business directories. These partners provide the least value to our customers and our product and so we dedicate the least technical resources.
We do not work on resolving bugs for these partners and publication issues that are the fault of the partner are escalated by Data Operations for Tier A customers.
We do not escalate case-by-case issues for Tier B &C customers. We will send the partner an automated report of all issues which occurred on their channel once a month and request they resolve those issues.
Slack - Product will update #product_partner_news slack channel with new implementation announcements or any known issues affecting many locations
JIRA - You can see more granular information about each implementation in the implementation tickets