Friday, October 22, 2010

Contact tendered resignation- retain or edit data?

Contact database updates & verification might seem like an easy work but to handle thousands & thousands of business contacts on a daily basis is a lot more work than one would think. That's why we have a Task Bank in our current website, wherein registered members can help out cleaning our data. We've also improved that to be a more user-friendly feature for the new website (we're currently working on) so new & old users alike can easily understand the contact checking & verifying process. Of course our internal team still has to verify those data but it makes the job easier, faster.

However, disputes over purchased, updated data cannot be avoided. Imagine this scenario:

1. Joe submitted the following contact information:
    Sheila Pih
    IT Manager
    Company Pte Ltd
    sheila@company.com
    6584219561
    Bedok, Singapore

2. Lea selected and purchased Joe's contact.

3. Lea emailed Joe's contact, Sheila Pih.

5. Lea called Sheila's company to follow-up and learned that Sheila has already tendered her resignation a week ago.

6. Lea reported a contact dispute to our website, saying that contact has already tendered her resignation.

7. Joe learned of the dispute and answered that while Sheila is still tendering her resignation, it doesn't follow that her contact information are inaccurate. She is still an IT manager, she's still using that email address
and she is still connected with Company Pte Ltd.

So if the contact information is proven to be current & accurate but one's aware that it will change in a few weeks time, would you still retain that in the database?

The answer would be no. Frankly speaking, since data verification takes a lot of time to do, it would be quite a waste of time to retain data that would still need to be updated in a few weeks or so. Why not update it right there & then and just file a report saying that the contact has already tendered resignation and would need to change information?

Makes sense doesn't it?

No comments:

Post a Comment