Wordfly Profiles and the Deceased

Wondering if anyone else has encountered this with Wordfly.   

We had a Household in which one partner died  -- this deceased partner was the primary name and so emails were addressed to him.  When he died, we updated the Household confirmed the same email would be used by the surviving partner.  The record for the deceased was inactivated.

Then we got the call for the surviving partner complaining that all the emails were still being addressed to his deceased partner and he found this very painful (of course).

We dug a bit more and discovered that Wordfly creates a profile for every email but it does NOT update the profile if different information is passed to it.   We have manually changed the name in Wordfly for this email.

Has anyone else run into this issue with Wordfly?  Is there a way to make certain the profile data is updated or is it now part of the record clean up done when a Household member dies?

  • Wow, Leslie, I have not experienced this in our consortium. I just double checked a few name/salutation changes from TA_AUDIT_TRAIL and WordFly has correctly updated the profile when the changed information has been part of the output set. It also updates the date on that field to match when the subscriber list is uploaded. So that sounds like the intended behavior?

    If there's no WordFly configuration gone wrong, we have had problems with constituents creating two different records and formatting them differently. EX: johndoe@gmail.com and john.doe@gmail.com, which are identical on the gmail side but not the Tessitura or WordFly sides. So we have updated constituent records then found out they were stil getting the wrong information. But that sounds different from what you're experiencing.

    If you get an interesting answer from WordFly please post it!

    -- Mike

  • Former Member
    Former Member $organization

    Yes, we've had a bit of this problem before. Like Mike said, it may be a case of johndoe@gmail vs. john.doe@gmail. Our problem was the output set elements were either not being used, or not mapped to the right fields. If someone is only importing the email, and not salutation fields, no new data is being brought in. It sounds like that's what's happening for you.

    Ann