Originally posted by 263026
View Post
Announcement
Collapse
No announcement yet.
Very Disappointed in familytreedna
Collapse
X
-
^-- And that sort of timeframe should still be possible with proper lab management, staffing, and infrastructure.
Leave a comment:
-
In the good old days of FTDNA:
batch 520
Y-DNA12
Batched 06/12/2013
Completed 06/21/2013
batch 538
Y-DNA25
Batched 10/16/2013
Completed 11/03/2013
batch 562
Y-DNA37
Batched 03/25/2014
Completed 05/07/2014
Leave a comment:
-
Resultsdelayed again
DNA kits sent in late February and early March are delayed to July - this time.
I will recommend that people run from this company. Disappointment has turned to disgust.
Leave a comment:
-
Originally posted by mikechilds54 View PostPersonally, I think a big improvement would be if Familytreedna received half the payment when the kit is ordered, and the other half when the results are ready to be downloaded.
Leave a comment:
-
A big improvement would be
Personally, I think a big improvement would be if Familytreedna received half the payment when the kit is ordered, and the other half when the results are ready to be downloaded.
Leave a comment:
-
Originally posted by Tenn4ever View PostI can understand somewhat but it doesn't explain, for example, Batch 603 and 604 which were purchased at the tail end of the big sale in December being delayed while batches such as 607 and 608 getting their Y results already.
Leave a comment:
-
Originally posted by gtc View PostYes, a batch is an internal construct that FTDNA ought to keep to itself. It doesn't help the customer because a batch of orders can contain a wide variety of test types, each of which has different average processing times.
If it is going to provide ETAs at all, then yes those ETAs to be based on the individual orders, regardless of the order batching scheme.
FTDNA publishes estimated processing times here:
... but that table does not take account of the tsunami of orders it receives every time it runs special offers (and the associated logjams in the lab), or lab processing problems, or staff shortages, or whatever else.
Leave a comment:
-
LMS. Clearly what the lab has (if anything) isn't working. Plus, I personally know several people whose FMS took 20 weeks. FTDNA needs new lab management.
Leave a comment:
-
Originally posted by selah View PostThe estimated dates should be correct from the beginning and not assign the same date to the different tests in the batch.
If it is going to provide ETAs at all, then yes those ETAs to be based on the individual orders, regardless of the order batching scheme.
FTDNA publishes estimated processing times here:
... but that table does not take account of the tsunami of orders it receives every time it runs special offers (and the associated logjams in the lab), or lab processing problems, or staff shortages, or whatever else.
Leave a comment:
-
I share your frustration my Mtdna was due 15 April to 29 April and lo and behold it is now 27 may to 10 june for Batch 612.
Leave a comment:
-
The estimated dates should be correct from the beginning and not assign the same date to the different tests in the batch. That is misleading and is the root cause of everyone's agitation. My FMS should have had the correct estimated results date from the beginning, not the same date as a FF in the same batch and then bumped out. These dates are changing weekly and it's ridiculous. I want to purchase two Y tests, but will probably purchase from yseq.
Leave a comment:
Leave a comment: