Customer experience | Sales, Customer Insights,...

Lead's Activities in Account's and Contact's timeline

(1) Share

Report

Posted on by Community Member

Hi guys,

When I create a contact out of Lead, then all the Lead's activities are immediately shown in Contact's timeline. But if I select an existing Contact, then Lead's Activities do not appear in Contact's timeline even after Lead Qualification. Does anybody know a way to change it?

P.S.-btw, does anybody know if we can also show Lead's activities for existing Account without waiting for Qualification of Lead?

Have a wonderful day!

BR, Katerina

All responses (3)

Answers (0)

Suggested answer

LuHao 40,884 on at

Like (0)

Report

RE: Lead's Activities in Account's and Contact's timeline

Hi Katerina,

The following is a comment from the Microsoft engineer on this issue.

this is by design and limitation.
the reason why you are not seeing expected activity(email,appointment,task) in contact timeline bcz it is not mapped with any field when created through Lead's timeline.

for phonecall activity - if Lead has parentcontact associated with it then phonecalls's "To" field will mapped with Lead's parentcontact while create a phonecall for Lead and you will be able to see this activity in Contact's timeline.
and if Lead doesn't have parentContact then it will mapped with Lead Name
Community Member on at

Like (0)

Report

RE: Lead's Activities in Account's and Contact's timeline

Thank you, Hao!

Weird, that it is only for phone calls
LuHao 40,884 on at

Like (1)

Report

RE: Lead's Activities in Account's and Contact's timeline

Hi Katerina,

I tested it, the result is that only Phone Call can appear in the Contact timeline that the Lead is not qualified.

There is a Lead and its Existing Contact and Account contain data.

I create a Phone Call for the Lead, and it appears in the Contact timeline.

But other types of activity records for Lead, such as Email, Task or Appointment, do not appear in the timeline of Contact.

Not sure if this is by design or a bug, I will raise a support ticket for this.