Assign CTA in C360 Cockpit to R360 Relationship

Related products: None

Hi,













We have CTAs being generated at C360 level - some of these need to be manually reassigned to the relevant R360s under that account. I cannot find a way to be able to do that however - I'm aware you can create a new CTA directly in R360 but is there a way existing CTA can be assigned to a R360?













Thanks in advance













Katerina











Hi Katerina,





Thanks for sharing this. Is it not possible to create the CTA at the relationship level right from the start (Or does that can to happen only manually?)




In this case it's not possible - we can have up to 30-40 relationships per account and there is no logic we can apply to determine which one this CTAs ought to be assigned, CSMs need to manage that manually




Got it. What are these relationships representative of in your case? And are each of them handled by different prople or is it the same person handling the entire account?




A bit difficult to explain but in short, we use R360 to identify a subset of customers so for example we have manufacturers as C360s (e.g. Coca Cola) who send them products to a number of retailers (e.g. Walmart, also our customer) so we will have Coca Cola as C360 with a number of retailers as R360s. These relationships are, in some cases, managed by a different CSMs. This CTA in question will be automatically created at the C360 Coca Cola level but may need to be assigned to the R360 Walmart. We cannot automate this CTA directly to the R360 level (our own data limitation) so need to reassign it manually.





The question is – can this be done?





thanks




We have a different use case, but the end result is the same.  A CTA can accidentally be logged to C360; and then it needs to be moved to its correct home in R360.  Would be great if that can just be reassigned to R360 and all the tasks and timeline updates go with it.  

As it is today, we need to create a new CTA in R360 and copy/paste the data.  

Another example is transferring tasks between R360’s for the same account.  This will need to happen at scale. 


@tstayin Thanks for the feedback. One of the challenges we see in moving it is that the CTA fields and layout between a company CTA and relationship CTA may be different. This will cause data inconsistency issues and that’s why we haven’t provided ability to migrate CTA at entity level (company or relationship) and CTA type level (each type might have different layout).