Skip to content
Guide

AWS referrals explained: engagement invitations and leads

AWS shares two kinds of engagement invitation with partners: referrals, which are opportunities an AWS seller wants to co-sell, and leads from AWS marketing. This guide covers what each one shows before you accept, how long you have to answer, and what to set up so none of them lapse.

9 min readUpdated By the HabileLabs CoSell team

An AWS referral is a customer opportunity that AWS shares with your company through AWS Partner Central. It arrives as an engagement invitation that you accept or reject, and the clock starts when AWS sends it. This guide follows AWS documentation as of November 2026. For the other direction, logging your own deals, see how to submit an ACE opportunity.

AWS-originated and partner-originated opportunities

Every ACE opportunity records where it came from in its Origin field.

  • Partner-originated (Partner Referral). You found the deal, created the opportunity and submitted it for AWS review. Every opportunity you create in the production catalog has this origin.
  • AWS-originated (AWS Referral). An AWS seller attached your company to an opportunity in AWS's own CRM. AWS then sends you an engagement invitation holding part of that opportunity's data. AWS says these referrals come from customers who agreed that a partner may help them.

You can create an AWS Referral opportunity yourself only in the Sandbox catalog, which is handy for testing your CRM before a real referral arrives.

AWS sends two kinds of engagement invitation, told apart by the PayloadType field: OpportunityInvitation for a referral and LeadInvitation for a lead.

ReferralLead
What it isAn opportunity an AWS seller is working and wants your help onA prospect who responded to AWS marketing; nobody has qualified it yet
Where it appearsOpportunity invitations tabLead invitations tab
Visible before you acceptCompany, website, country, industry, project title, business problem, expected spend, target close date, AWS contactsCompany, website, country, industry, segment, AWS maturity, campaign, what the customer did, contact's job title
Revealed after you acceptCustomer contact, street address and city, the customer's AWS account IDContact name, email and phone, and the full interaction history
Time to answerFive business daysFive business days
What it becomesAn opportunity in your accountA lead you work, then convert to an opportunity

Referrals: the opportunity invitation

What you can see before you accept

In the console, a pending referral shows the customer's company, website, country, postal code and industry, the deal's main fields (use case, business problem, next step, delivery model, monthly recurring revenue, target close date) and the AWS people on it.

Through the API, GetEngagementInvitation returns the OpportunityInvitation payload:

  • Customer: CompanyName, CountryCode, Industry and WebsiteUrl.
  • Project: Title, BusinessProblem, ExpectedCustomerSpend and TargetCompletionDate.
  • SenderContacts: up to three AWS contacts.
  • ReceiverResponsibilities: the role AWS expects you to play, such as Software Partner, Services Partner or Managed Service Provider.

The invitation also carries InvitationDate, ExpirationDate and an InvitationMessage. As of November 2026 it can include an EnrichmentContext with AWS insights, such as a lead readiness score.

What stays hidden until you accept

AWS holds back the details that identify the customer's people and premises: the customer contact, the street address and city, and the customer's AWS account ID. It also leaves out the other-solution description and the related entity identifiers. You see them once you accept and the opportunity is created in your account.

How long you have

The AWS Partner Central Sales Guide gives you five business days to accept or reject a referral. If you do neither, the referral is removed from your Opportunity invitations tab. Through the API, its Status becomes EXPIRED and an Engagement Invitation Expired event is sent.

Use each invitation's ExpirationDate as the deadline rather than counting days yourself. The developer guide's 15-day expiry applies to invitations between partners on multi-partner opportunities, so plan AWS referrals around five business days.

Accept or reject

Accepting tells AWS you will work the opportunity alongside its seller.

  1. Open the Opportunity invitations tab and choose the opportunity ID to read what AWS shared.
  2. Select one or more invitations and choose Accept invitation.
  3. Confirm. The opportunity moves to your Opportunities tab with its full details.

Through the API, call StartEngagementByAcceptingInvitationTask. It runs in the background: it accepts the invitation, creates an opportunity in your account from AWS's data, and sends an Opportunity Created event with the new opportunity ID. Read the full record with GetOpportunity. If you don't use events, calling the task again with the same payload returns its latest status.

Rejecting tells AWS you will not pursue the opportunity, and you lose access to its data. RejectEngagementInvitation takes a RejectionReason, and AWS lists five values:

  • Customer problem unclear
  • Next steps unclear
  • Unable to support, when you lack the people or the skills
  • Duplicate of partner referral, when you already submitted the same deal
  • Other

If you cannot serve the customer, reject with a reason rather than letting the invitation lapse. AWS uses the reason to track patterns.

Leads: the lead invitation

How a lead differs from an opportunity

An ACE lead is a prospect, not a deal. AWS shares leads based on signals such as webinar attendance, campaign responses or questions about partner solutions. Nobody has qualified the customer yet and there is no sales stage to report. AWS describes lead nurturing as mostly partner-driven, with joint work starting once the lead becomes an opportunity. An opportunity is a qualified deal that moves through AWS's sales stages and AWS review.

Before you accept a lead you see the company and the interaction: the campaign or source, what the customer did, the business problem they described, the use case and the contact's job title. The contact's name, email and phone stay hidden until you accept. AWS says this protects customer privacy and prevents lead farming.

Accept, work and qualify a lead

Accept leads on the Lead invitations tab, or through the API with AcceptEngagementInvitation. CoSell found that the task used for referrals refuses leads. Accepted leads move to the Leads tab. Through the API, the contact details appear in the engagement's lead context, which you read with GetEngagement.

A new lead's status is Unqualified. As you work it, set it to Qualified, Disqualified or a status of your own, in the console or with UpdateEngagementContext. AWS may add interactions later and sends an Engagement Updated event when it does.

If you reject a lead, it leaves your invitations list and you never see the contact. AWS may offer it to another partner.

Convert a qualified lead into an opportunity

  1. Set the lead's status to Qualified.
  2. Choose Create draft opportunity. Partner Central creates a draft opportunity with the lead's details filled in.
  3. Choose View draft opportunity and add the required fields the lead did not have.
  4. Choose Submit to send it for AWS review.

Through the API, StartOpportunityFromEngagementTask creates the draft and links it to the lead. You then complete it with UpdateOpportunity, attach your solution with AssociateOpportunity and submit it with StartEngagementFromOpportunityTask. Converting this way keeps the link between lead and opportunity, which AWS uses for attribution.

In CoSell's experience, AWS refuses the conversion when the lead has no customer website or industry. AWS leads often arrive without a website, so add both before you convert. The new opportunity is yours to complete and submit, like any deal you found yourself.

How invitations reach you

  • The console. Partner Central has been part of the AWS Management Console since 30 November 2025. Referrals sit on the Opportunity invitations tab and leads on the Lead invitations tab, both under the Sell menu.
  • The API. ListEngagementInvitations lists invitations. Set ParticipantType to RECEIVER for those sent to you, and filter by Status if you want only PENDING ones. Pass both values of PayloadType: CoSell found that leaving the filter out returned only opportunity invitations. GetEngagementInvitation returns one invitation in full.
  • Events. Partner Central publishes Selling API events to Amazon EventBridge with the source aws.partnercentral-selling. Rules must sit on the default event bus in US East (N. Virginia). Engagement Invitation Created fires when a referral or lead arrives, and its payloadType tells you which.
StepReferralLead
Notice itEngagement Invitation Created eventThe same event, with payloadType set to LeadInvitation
List and read itListEngagementInvitations, GetEngagementInvitationThe same calls
Accept itStartEngagementByAcceptingInvitationTaskAcceptEngagementInvitation
Reject itRejectEngagementInvitationRejectEngagementInvitation
Read the full recordOpportunity Created event, then GetOpportunityGetEngagement
Move it onUpdateOpportunityStartOpportunityFromEngagementTask once qualified

Who should own invitations

AWS's guide to Partner Central personas gives sales managers the AWSPartnerCentralOpportunityManagement policy and lists accepting and managing AWS-referred leads among their duties. The alliance lead manages the ACE pipeline as a whole. A workable setup:

  1. Name one owner for each territory or segment, and a backup for leave and holidays.
  2. Check in IAM that both people can accept and reject, not only view.
  3. Set an internal SLA shorter than AWS's window. Deciding within two business days leaves time for a second look before the five-business-day limit.
  4. Check for new invitations every working day, or send the Engagement Invitation Created event to a channel the owner watches.
  5. Record why you rejected each invitation, and review rejected and expired ones every month.

What happens in your CRM after you accept

Partner Central does not write to your CRM. Someone, or an integration, has to carry the referral across:

  • Wait for the opportunity. AWS creates it shortly after the acceptance. Match it to the invitation by the ID in the Opportunity Created event, or by Project.Title as AWS's API reference suggests.
  • Create or match the account. Use the company name and website, so you don't duplicate a customer you already hold.
  • Add the contact, which is now visible on the opportunity.
  • Create the deal with the ACE opportunity ID, the origin AWS Referral, the AWS seller's name and the target close date.
  • Convert the spend. ACE records expected spend per month, in US dollars for most partners. Convert it if your CRM uses another currency or tracks total contract value.
  • Keep both sides in step. AWS sellers update the opportunity too, and Opportunity Updated events tell you when. Send your stage changes and next steps back as the deal moves.

For a lead, create a CRM lead rather than a deal, and convert it only once it is qualified.

Where CoSell fits

CoSell lists AWS referrals and leads together, each with its respond-by date and an owner. Accepting a referral in CoSell accepts it in Partner Central, then creates the account, contact and deal in your CRM: Salesforce, HubSpot, Microsoft Dynamics 365, Zoho CRM, LeadSquared or CoSell's built-in CRM. AWS leads arrive as CRM leads, and a qualified lead can be converted to an opportunity from the same list. CoSell runs hosted by HabileLabs or in your own AWS account, from USD 10 a month on AWS Marketplace; the offer is currently for AWS accounts in India. See features and pricing.

Sources

More guides

All guides

Available in AWS Marketplace

Try CoSell free for 30 days

Start the free trial on AWS Marketplace with your AWS account. Your workspace is ready in minutes, and you connect your CRM yourself.