It wasn't a "report".  Someone posted that I had told him something
which I hadn't and he said it was in May.  I found it and that he had
corresponded iwth another support person back in January. No black
hole to fall into. That ticket was closed because the question was
answered.

When you send a message to supp...@legacyfamilytree.com, you should
get a response from our ticketing system which gives you the ticket
number and other information. If you're not getting that within a
short period of time, check your spam folder, esp on the web. Some
ISPs don't like auto-responses.

The ticket number shows up in the subject line of every message sent
to us through the proper channels.

That's why it's so important to write to supp...@legacyfamilytree.com
rather than to a specific tech directly now.  That way we can all keep
better track of what we're doing <g>

Sincerely,
Sherry
Technical Support
Legacy Family Tree



On Mon, Aug 2, 2010 at 9:16 AM, CE Wood <wood...@msn.com> wrote:
> Oh Ron!  You are going to get people all excited.  Many emails from support 
> have advised us it will be a looooooooooong time before that happens.  As has 
> been said many times recently, the programmers are focused on FamilySearch to 
> the detriment of correcting problems reported more than four years ago.  
> There are times it seems our reports go into a black hole.  Even Sherry 
> recently admitted to not knowing about a report, and found it buried 
> somewhere only because the reporter had a report number.  Most never get 
> those when we report a problem to support......
>
>
> CE



Legacy User Group guidelines:

   http://www.LegacyFamilyTree.com/Etiquette.asp

Archived messages after Nov. 21 2009:

   http://www.mail-archive.com/legacyusergroup@legacyusers.com/

Archived messages from old mail server - before Nov. 21 2009:

   http://www.mail-archive.com/legacyusergr...@legacyfamilytree.com/

Online technical support: http://www.LegacyFamilyTree.com/Help.asp

To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp



Reply via email to