Opportunity sync

Hi Jean-Philippe,

What is the reason for employing Opps in the Market while having Sugar Sell in place?

Opps are the objects for Sales team efforts, while the Lead is the outcome of marketing efforts and inbound entity for Sales, so that sales could qualify them and convert into Opps according to b2b methodology.

To keep nurture the  Contacts of the Opps with Marketing, those Contacts should belong to some Target list.

The Target list could be actualized automatically with e.g. SugarBPM /report/ logic hook (developed or configured with Logic Builder) - but anyway it is done on the basis of some criteria that maintained in the sales tool - SugarSell.

For example you may use a logichook to add Contact to the Target list as soon as it linked to Open Opp, and remove it once the Opp is closed or Contact is unlinked from the Opp - I can configure an example with Logic Builder if you like, or you can make it

I may presuppose, Opps in the Market are for non-Sugar subscribers of ex-SalesFusion

Best,

Dmytro

Hi Jean-Philippe,

What is the reason for employing Opps in the Market while having Sugar Sell in place?

Opps are the objects for Sales team efforts, while the Lead is the outcome of marketing efforts and inbound entity for Sales, so that sales could qualify them and convert into Opps according to b2b methodology.

To keep nurture the  Contacts of the Opps with Marketing, those Contacts should belong to some Target list.

The Target list could be actualized automatically with e.g. SugarBPM /report/ logic hook (developed or configured with Logic Builder) - but anyway it is done on the basis of some criteria that maintained in the sales tool - SugarSell.

For example you may use a logichook to add Contact to the Target list as soon as it linked to Open Opp, and remove it once the Opp is closed or Contact is unlinked from the Opp - I can configure an example with Logic Builder if you like, or you can make it

I may presuppose, Opps in the Market are for non-Sugar subscribers of ex-SalesFusion

Best,

Dmytro

I would like to slightly disagree on that one

Yes you can use target lists (although in Sugar you have to code to make them dynamic, or to build BPMs). But TLs will get cumbersome if you want to have a high level of personalisation: date of purchase, amount, products, type (renewal/first time) etc. Actually the same goes for other business objects: contracts, cases, etc. 

I've spoken to the Market team and they are working on that. Let's hope we'll have more data to play with in the future. 

Hi Dmytro,

This is to meet the following use case with Sugar Sell or ENT: a client has a B2B target but a B2C approach and sells online. In this case, you use the Opps entity to store the orders. By sincing the opps and using the listeners, we could imagine to send emails to the contact related to the Opp (e.g. Congratulations for your 1st order). 

We could also imagine to add the contact to a Nurture (e.g. Customer Success emails-serie) when an Opp is won.

In this view, it is important to know what could be the side effects if several contacts are related to the Opp in Sugar, as only 1 contact is linked to the Opp object in Market.