Suger

Outbound Referral

Share opportunities from your CRM with partners


Overview

With your co-sell configurations, sharing with partners can be as easy as a few mouse clicks.

Outbox

Outbox is the place to show your CRM opportunities that are ready to be sent to partners.

Without any configuration, this tab lists all your CRM opportunities. You can click the filter button to specify various filters to narrow down the scope:

Filter options for narrowing down Outbox opportunities

You can also use the search box on the top right:

Search box for Outbox opportunities

Share an Opportunity

Sharing happens on its own full page, not in a pop-up dialog. The page has its own URL, so you can bookmark a share in progress, reload it, or send the link to a colleague. Its header reads Share to {cloud} co-sell referral — for example, Share to AWS co-sell referral.

Below is an example where we share a Salesforce opportunity with AWS.

  1. Find an opportunity from the Outbox.

  2. Click on the opportunity name (in teal color) which navigates to the detail page.

  3. Click the Share button on the top right. Suger opens the share page.

  4. Work through the stepper at the top of the page. Each step groups a related set of fields; fill in the required fields, and any optional fields you want to send.

  5. If all validation passed, the Submit button will be clickable. Click on it.

  6. Suger sends this to AWS. This process usually takes ~5 seconds but sometimes it takes longer.

  7. The shared opportunity will be moved to the “In Sync” tab.

    Shared opportunity listed in the In Sync tab
  8. You can click on it to check the details. You should see the “APN CRM Unique Identifier” in the “Destination” section on the bottom.

    APN CRM Unique Identifier shown in the Destination section

Duplicate title advisory

When you submit, Suger checks whether the same partner already has a still-open referral with a matching title. Matching ignores letter case and surrounding whitespace, so “Acme Corp — Migration” and “acme corp — migration ” count as the same title.

If it finds one, Suger shows you the matching referrals so you can decide whether you are about to create a duplicate.

Re-submit a failed referral

A referral that failed on the way to the partner does not have to be recreated from scratch. Open the referral’s detail page and use the Re-submit action.

When Re-submit is available

SituationRe-submit?
Status is CREATE_FAILEDYes
AWS referral whose review status is still pending submissionYes
Any other status — the referral is healthy or already at the partnerNo

If you reach the re-submit flow for a referral that does not qualify, Suger refuses it with: “This referral cannot be re-submitted.”

What happens when you re-submit

  1. Open the failed referral’s detail page.
  2. Click Re-submit. Suger seeds the form from the payload it stored on the original attempt, so every value you entered the first time is still there.
  3. Correct whatever the partner rejected — the error message on the referral tells you what to fix.
  4. Click Submit.

Bulk Share

You can share multiple opportunities at the same time. This can be very efficient if your CRM data is in good quality (e.g., all postal codes are filled) and the field mappings & templates are well-configured.

  1. Click the Bulk Share button to enter the selection mode.

    Bulk Share selection mode for Outbox opportunities
  2. Select those you want to share and click Submit.

  3. A dialog will pop out showing the AWS opportunity we are about to submit.

    Bulk share confirmation dialog for AWS opportunities

    You can click on any of them to check the details.

  4. If all validation passed, you can click the Submit button. Otherwise you’ll need to manually fill them.

Running two bulk shares at once

You can start a second bulk share while a first one is still processing. Previously the second batch could be dropped, or leave rows sitting in Pending Create indefinitely — that no longer happens.

If a batch cannot be started, its referrals are marked CREATE_FAILED rather than left stranded, with the message:

Could not start the {partner} submission for this bulk share — please resubmit the referral

Those rows behave like any other failed referral: open one and use Re-submit to push it through.

Auto-Share Retries

Auto-share does not give up on a referral the partner rejected. A CREATE_FAILED referral re-enters the candidate list on the next auto-share run — roughly every 3 hours — and Suger updates the existing record rather than creating a duplicate.

Retried automaticallyCREATE_FAILED
Never retriedUPDATE_FAILED, PENDING_CREATE, DRAFT
Retry limit16 attempts, roughly 48 hours

After 16 attempts the referral stops being retried and stays CREATE_FAILED. At that point the cause is almost always data the partner will keep rejecting — fix the underlying field and use Re-submit on the referral itself.

Auto-Enrich Referrals

Save time and improve data quality by automatically filling in missing company and contact information when sharing opportunities with cloud partners. The auto enrichment feature helps ensure your referrals have complete information, increasing the chances of successful partner engagement.

How It Works

When you preview an opportunity before sharing it with a cloud partner (AWS, Azure, or GCP), Suger can automatically fill in missing fields like company addresses, contact names, and more. This happens seamlessly in the background - you’ll see the enriched data right in your preview.

To enable auto enrichment:

  1. Go to SettingsCosellCosell Configs
  2. Find your partner configuration (AWS, Azure, or GCP)
  3. Enable the Auto-Enrich Referrals option
Auto-Enrich Referrals option enabled in Cosell Configs

Once enabled, the enrichment will happen automatically whenever you preview opportunities for that partner. Your existing data is always preserved - only empty fields are filled in.

What Information Is Needed

For the enrichment to work effectively, your CRM data needs to have some basic information about the company and contacts.

For company information, the service needs at least:

  • Company name, or
  • Company website/domain

For contact information, the service needs at least:

  • Contact email address, or
  • Contact first and last name (along with company information)

If these basic fields are missing in your CRM data, the enrichment service won’t be able to find additional information for that record.

What Fields Can Be Enriched

The auto enrichment feature can fill in many commonly required fields for each cloud partner. Here’s what can be automatically populated:

AWS

Company Information:

  • Company name and website
  • Full address (country, state, city, street address, postal code)
  • Industry classification

Contact Information:

  • Email address
  • First and last name
  • Job title

Azure

Company Information:

  • Company name
  • Full address (country, state, city, street address, postal code)

Contact Information:

  • Email address
  • First and last name
  • Job title

GCP

Company Information:

  • Organization name and domain
  • Full address (country, state/province, city, postal code, street address)
  • Industry classification
  • Company region
  • Employee count

Contact Information:

  • Email address
  • First and last name (given name and family name)

Spotted something wrong or out of date on this page? Tell us and we'll correct it.