Maintaining the veracity of the content in our database is a high priority and InsideView has an effective process to manage data that is flagged by a customer.
Data that is flagged as Wrong Info comes directly to the InsideView Content team who are responsible for researching the information, validating it using various sources, correcting the InsideView data if it is inaccurate, and responding to the person who reported it.
The process followed by the Content team is as follows:
- Analyze the wrong data flagged.
- Validate the data by performing secondary research that includes looking up company websites, SEC filings, recent news articles, web-based sources, publicly available information, and various other resources.
- Respond to the person who reported it as Wrong Info.
Once the validation is complete, the Content Analyst will update the records if the reported data is accurate. If the reported data cannot be authenticated with the validation resources available, the request is designated as No-Change and the Content Analyst will not take any action and then respond to the requester. In critical cases, the Content Analyst will establish a communication channel with additional resources to authenticate the request. The criticality is based on ambiguity and the borderline nature of the request. Borderline cases are those that are most recent changes that may be true but aren't reflected in any of the sources InsideView depends upon.
Here’s an example of how it works. Let's say a user used the wrong information flag for Tim Jones, a director at BlueBerry Consulting, a $ 5M company. According to the user, Tim is no longer with BlueBerry and he has moved to a different company.
To respond to this request, the InsideView Content Team must be able to establish the accuracy of the reported information before updating using their secondary research process. If they cannot verify the reported information, the Content Analyst will establish a communication channel with the user. Upon completion, the Analyst will either designate the request as Record Updated or No Change. In either case, an email notification is sent to the user apprising him/her about the result of the wrong information notification.