AWS Opportunity Insights and Company Prospecting Signals, now in your Salesforce

AWS attaches AI-generated intelligence to your co-sell pipeline — how strong an opportunity looks, how AWS is engaging on it, and what kind of solution fits each account. As part of our new Salesforce Managed Package v1.67 release below properties are now available as part of Clazar's custom object in your Salesforce instance.

New on the Clazar AWS Co-Sell Opportunity object

• Opportunity Quality Score (clazar__opportunity_quality_score__c) — AWS's AI-generated score (0–100) for the opportunity.
• Opportunity Quality Trend (clazar__opportunity_quality_trend__c) — whether the score is Improving, Declining, or showing No Change.
• Recommendation (clazar__cosell_quality_recommendation__c) — AWS's written guidance on how to strengthen the opportunity.
• Co-Sell Motion (clazar__cosell_motion__c) — how AWS is engaging on the deal: Partner-led, AWS Field-engaged, or Agent-engaged.

New on the Clazar Companies object

• AWS Solution Category (clazar__aws_solution_category__c) and AWS Solution Sub Category (clazar__aws_solution_sub_category__c) — the type of solution that, based on AWS's internal insights, is most likely to fulfill this company's needs.
• AWS Solution Score (clazar__aws_solution_score__c) — AWS's confidence that a solution in that category is the right fit for the company.
• AWS Eligible Programs (clazar__aws_eligible_programs__c) — the AWS programs the company qualifies for.

How to get it

Once your org is on package v1.67 (delivered automatically via push upgrade, or installable from the Clazar app under Integrations → Salesforce → Setup → Install Package), the fields populate through your regular Clazar writebacks — no configuration needed.

Two setup notes

• Field visibility on record pages: if you've customized your page layouts for these objects, Salesforce won't add new fields to them automatically. Place them via Setup → Object Manager → the object → Page Layouts.
• Field-level security: if your Clazar integration user runs on a custom profile or a cloned permission set (rather than the packaged Clazar permission set), grant it read/write access to the new fields — otherwise values can't be written. Assigning the packaged Clazar permission set covers this automatically.