Clazar Auto - Heal

Overview

This guide explains how Auto-Heal works and how to configure it for your co-sell setup. Auto-Heal automatically detects and resolves common sync errors during co-sell auto-create and auto-update — so your opportunities reach AWS or Azure without manual intervention.

If you've experienced co-sell sync failures caused by missing fields, invalid dates, or empty values from your CRM, Auto-Heal is designed to fix these automatically.

What Is Auto-Heal?

Auto-Heal is a multi-layered system built into Clazar's co-sell sync pipeline. It resolves the most common classes of sync errors by applying intelligent fallback values when your CRM data is missing or invalid.

Auto-Heal addresses three main scenarios:

1. Invalid or missing date fields — Target close date, contract start date, or contract end date is empty or in the past.

2. Empty required fields during auto-update — Mandatory fields like expected monthly AWS revenue or delivery model are mapped but return empty from your CRM.

3. Missing company details — Domain-based enrichment fails or returns incomplete data.

How Auto-Heal Works

When Clazar syncs a co-sell opportunity (via auto-create or auto-update), it evaluates every mapped field through a multi-tier fallback:

Tier 1: CRM Value — If the mapped CRM field has a valid value, Clazar uses it. No fallback needed.

Tier 2: Auto-Resolve Expression (date fields) — If the date field is empty or invalid (e.g., target close date in the past), Clazar evaluates a configurable expression like today() + 15d and uses the result.

Tier 3: Configured Default Value — If the field is non-date and the CRM returns empty, Clazar falls back to your configured default value for that field.

Tier 4: Validation Error — If none of the above produce a valid value, the standard validation error surfaces as before.

Real CRM data always takes priority. Defaults are only used when your CRM value is missing or invalid.

Defaults Are Temporary — Not Permanent Overrides

A common question: If Clazar uses a placeholder value (like $1 for MRR), does it stay on AWS forever?

No. Defaults are designed as temporary bridges. Here is how the self-correcting cycle works:

Step 1 — Auto-Create: The CRM field is empty. Clazar uses the default (e.g., $1 for MRR). The opportunity syncs to AWS successfully instead of failing.

Step 2 — Sales rep updates CRM: Days or weeks later, the rep fills in the real value in Salesforce or HubSpot (e.g., $50,000 MRR).

Step 3 — Auto-Update picks it up: The next auto-update cycle detects the CRM now has a valid value. It pushes the real value to AWS, replacing the placeholder automatically.

This self-correcting behaviour applies to every field where auto-update is enabled. No manual cleanup is needed.

Supported Fields and Default Expressions

Date Fields (Auto-Resolve Expressions)

These fields use formula-based defaults that resolve dynamically:

These three date fields alone account for the majority of co-sell sync errors on AWS.

Required Fields for Auto-Update (AWS)

These 6 fields are included in every auto-update API call to AWS. If your CRM returns empty and no default exists, the update fails.

Required Fields for Azure Co-Sell

How to Review and Customize Your Defaults

Step 1: Navigate to Co-Sell Settings

1. Log in to your Clazar dashboard.

2. Go to Settings > Integrations in the left sidebar.

3. Click Salesforce (or HubSpot, depending on your CRM).

4. Select the Co-Sell tab.

5. Choose AWS or Azure as the hyperscaler.

Step 2: Open Field Mappings

1. Click the Field Mappings tab.

2. You will see a table with three columns:

   • ACE/Partner Center Field Name — The field required by AWS or Azure.

   • CRM Field — The Salesforce or HubSpot field mapped to it.

   • Default Value — The fallback value Clazar will use if the CRM field is empty or invalid.

Step 3: Review Pre-Configured Defaults

Scroll through the field mapping table. Fields that have Auto-Heal defaults will show the pre-configured value in the Default Value column. These are ready to use immediately — no action required from you unless you want to customize.

Step 4: Customize a Default Value (Optional)

To change a default value for a non-date field:

1. Find the field you want to customize in the mapping table.

2. Scroll to the right to the Default Value column.

3. Click the edit (pencil) icon next to the field.

4. Enter your preferred default value.

5. Click Save.

Your custom default will take priority over the pre-configured default going forward.

Step 5: Customize a Date Expression (Optional)

For date fields (target close date, contract start date, contract end date), you can customize the auto-resolve expression:

1. Find the date field in the mapping table.

2. Click the edit icon in the Default Value column.

3. Use the expression builder with four controls:

   • Base value: today() or a CRM field reference

   • Operator: + (add) or - (subtract)

   • Number: Any positive integer

   • Unit: days or months

4. Click Save.

Supported expression examples:

Step 6: Configure Auto-Update Settings

1. Go back to the Settings tab (next to Field Mappings).

2. You will see two options:

   • Auto-Create — Automatically creates co-sell opportunities in AWS/Azure when CRM deals match your criteria.

   • Auto-Update — Automatically syncs field changes from your CRM to Partner Central.

3. For Auto-Update, click to expand and you will see a checkbox next to each field.

4. Tick the checkbox for every field you want Clazar to keep in sync automatically.

5. Click Save.

Auto-Update runs twice daily. When enabled, any field change in your CRM (stage, close date, MRR, etc.) syncs to AWS or Azure automatically.

Step 7: Verify Auto-Heal Is Working

After Auto-Heal is active on your account:

1. Check your Co-Sell Opportunities list in Clazar.

2. Opportunities that previously showed sync errors should now show as successfully synced.

3. If an opportunity was auto-healed, the synced value reflects the default used.

4. Once your sales rep updates the CRM with real data, the next auto-update cycle replaces the default with the actual value.

What Auto-Heal Does NOT Do

• Does not affect manual opportunity creation. Auto-Heal only fires during auto-create and auto-update flows (CRM sync). Creating or editing opportunities manually through the Clazar UI is unaffected.

• Does not override real CRM data. If your CRM field has a valid value, Clazar always uses it. Defaults are only used when the CRM value is missing or invalid.

• Does not work without field mappings. You must have your CRM fields mapped in Clazar for Auto-Heal to apply. If no mapping exists for a field, Auto-Heal cannot intervene.

CRM Compatibility

Auto-Heal works identically with both Salesforce and HubSpot. The auto-resolve engine operates after CRM values are resolved, so it functions the same regardless of which CRM you use.

Frequently Asked Questions

Q: Do I need to configure anything for Auto-Heal to start working? No. When Auto-Heal is enabled on your account, all supported fields are pre-configured with sensible defaults. It works immediately on your existing setup. You can optionally customize defaults at any time.

Q: What happens if the expression evaluation fails? The original value passes through unchanged. The normal validation error surfaces as before. Auto-Heal is best-effort — it never makes things worse.

Q: What if I don't have a CRM field mapped for contract start or end date? You can still configure a default expression on a field even without a CRM source mapping. The expression evaluates against today() or references to other fields directly.

Q: Won't placeholder values like $1 MRR look wrong to AWS? These are intentionally minimal valid values. AWS requires these fields to be non-empty — without a default, the opportunity fails to sync entirely. A synced opportunity with $1 MRR is better than an opportunity that never reaches AWS. The value is automatically replaced once the sales rep updates the real amount in the CRM.

Q: Can I disable Auto-Heal for specific fields? You can remove or clear the default value for any field in the field mapping UI. Without a configured default, that field will not be auto-healed.

Q: How do I know Auto-Heal resolved a value? Opportunities that were auto-healed sync successfully instead of failing. You can verify by checking the synced opportunity in Clazar and comparing the value with what's in your CRM.

Still Having Issues?

If you're still seeing sync errors after Auto-Heal is active, or if you need help configuring your defaults:

• Reach out to your dedicated Clazar Implementation Specialist.

• Contact Clazar Support via Slack or your support channel.

• Include the opportunity ID and the specific error message for faster troubleshooting.