I am using pinpoint Marketing Tool with OL2007/BCM on a standalone computer running XP.

I don't know whether this was intended or not, but it appears that embedding merge codes in any plan element other than task or project task (i.e., call, email, letter, appointment) does not cause information to be merged into the element from the contact record of the contacts to which the plan applies.

When creating a plan that is applied to several contacts, it is very helpful to put some unique identifiers in the element to distinguish the multiple, identically-worded tasks (or project tasks) that are generated.  For example, creating a call element "Call real estate agent for lunch" generates 8 identical call tasks if the plan is applied to 8 contacts.  Not very helpful to have 8 tasks saying exactly the same thing.  If the call element could embed say [[Last Name]], "Call [[Last Name]] for lunch" the resulting 8 call tasks would be much more effective and efficient. 

I suppose that I could just use task elements to build the plan, since embedding merge codes in task elements (and in project task elements) seems to pull unique information into the multiple tasks (or project tasks) just fine.

But, why the distinction?

 

wcmack:

There shouldn't be a distinction -- you should be able to use the merge codes in a call the same as a task. Are you sure that the step in the plan is formatted the same as the task or project task? Are the merge codes exactly the same?

If you're still having problems, please call Belinda at x6110 for some help.

Thanks,
Lon

What does the merge function do in an email letter if that field for a specific contact does not exist? Does it just leave it blank I assume? Is there a way that if a certain field does not exist for a specific contact that the program could automatically substitute something in for that contact? For instance in an email merge, if no first name exists for a contact can the program automatically put in "Sir" as in Dear Sir in place of Dear John?