Create Co-Sell
Submit a co-sell referral to AWS, Azure, or GCP directly from a Salesforce opportunity using the Fours App.
Overview
A co-sell referral is how you formally ask AWS, Azure, or GCP to work with you on a deal. When you submit a referral, the cloud provider’s sales team can see the opportunity and engage to help you close it — for example, by introducing you to the right contacts, validating the opportunity, or contributing resources. In plain terms, you’re sharing a deal with your cloud partner so they can help you win it.
After adding the Fours App to your Salesforce Console, you can create co-sell referrals from opportunities with ease.
Prerequisites
- The Fours App must be installed, connected, and set up with the Fours widget on your opportunity pages. If you haven’t done that yet, work through the Getting Started and Salesforce Admin Setup steps first.
- You need the Fours User, Fours User - Cosell, or a cloud-specific co-sell permission set assigned to your Salesforce account. If you can’t see the Co-Sell button on an opportunity, your permission set is likely missing or incorrect.
Create a Co-Sell
- Navigate to the opportunity’s detail page and click the Co-Sell button at the top of the Fours App. If you don’t see the widget, it may not be added to your page layout yet.
- Choose the cloud partner you want to submit the referral to — AWS, Azure, or GCP — and fill the form with the necessary information. Required fields vary depending on which cloud partner you selected.
- Once all necessary information is filled in, submit the form to create the co-sell.
- You are all set!
What happens next
After you submit the referral:
- Fours creates a referral record in your Salesforce org, linked to the opportunity.
- The referral is sent to the cloud partner’s system — for example, AWS Partner Central (ACE), Azure Partner Center, or Google Cloud Partner Network.
- The cloud partner reviews the referral and may accept, reject, or request more information.
- Any future updates you make to the Salesforce opportunity are automatically synced to the referral — you do not need to manually push updates to the cloud partner. Fours scans your pipeline once per hour and updates the referral based on changes to the linked deal.
- If the cloud partner scores or updates the referral on their side (for example, AWS assigning an engagement score), those updates appear on the referral record in Salesforce after the next sync.
Create Salesforce Records from a Fours Referral
For Fours (PRM) deal-reg referrals, you can create a linked Salesforce Opportunity or Account directly from the referral — no need to navigate away and create the record manually.
From the referral record (Actions sidebar):
On the referral’s detail page, the Opportunity and Account cards do more than create records — they are how you attach the referral to the right Salesforce record and correct it later. Which actions the card offers depends on whether a record is linked yet:
| Action | Shown when | What it does |
|---|---|---|
| Create | Nothing linked yet | Opens a pre-filled form with fields populated from the referral’s customer and deal information (such as company name, contact, and deal amount). Review or adjust the values, then submit. The new Opportunity or Account is automatically linked to the referral. |
| Link | Nothing linked yet | Attaches an Opportunity or Account that already exists in Salesforce, without creating anything new. |
| View | A record is linked | Opens the linked Opportunity or Account record. |
| Edit | A record is linked | Edits the linked record in place from the referral. |
| Unlink | A record is linked | Detaches the record from the referral. The Salesforce record itself is not deleted — the card returns to its unlinked state, so you can then Link the correct one. |
In day-to-day use Link and Unlink matter more than Create: the Opportunity or Account usually already exists in Salesforce, and the work is pointing the referral at the right one — or repointing it when a referral landed on the wrong record. Create is for the case where the deal genuinely has no Salesforce record yet.
View is available to anyone who can see the referral. Create, Link, Edit, and Unlink require referral write access — with a read-only permission set (for example Fours Cosell (Read Only)) you will only see View.
Linking an offer: an AWS referral also has an Offer card with the same Link/View/Edit/Unlink actions. Its Link action opens Select AWS Marketplace Offer, which lists only offers an ACE opportunity can be linked to: accepted AWS offers that are neither a resale authorization (CPPO_OUT, CPPO_IN) nor a reseller’s resale offer to the buyer (CPPO). The list is also limited to offers from the AWS account your ACE integration is connected as; an offer with no seller account recorded stays listed, and when the ACE integration connects with access keys rather than an IAM role, offers from every AWS account are listed. Search with the box (Search by name, ID, or external ID…); each term must be at least three characters, and terms separated by commas must all match. The search runs on the server rather than filtering a preloaded page, so it still finds the right offer in an org with a large offer catalog. Each result shows its external ID, offer type, and status, and a search with no match reads No offers found. Try an offer name, offer ID, external ID, buyer, or AWS account ID.
After accepting an inbound Fours referral:
When you accept an inbound Fours referral, you are prompted to create linked Salesforce records as an optional next step. You can create an Opportunity, an Account, or both — and a Lead too when your inbound field mapping targets Lead. Fields are pre-filled from the referral data where available. Skipping this step is fine — you can always use the Create button on the cards later.
From an AWS, Azure, or GCP referral: the referral page’s header carries a Create Records button once your Fours admin has saved an inbound field mapping from that cloud to Salesforce. It needs write access to that cloud’s referrals and is hidden on a closed referral. The button opens Create Record, which offers one Create … tile per Salesforce object the mapping fills for this referral — Create Account and Create Opportunity, and Create Lead when the mapping targets Lead. If the mapping preview cannot be loaded, the dialog warns Field mapping preview unavailable. Default values will not be pre-populated. and offers Create Account and Create Opportunity only.
The create form. Whichever way you open it — a card’s Create, the Create Records button, or the prompt after accepting — the form for each object works the same way:
- Select Record Type comes first when you can use two or more active record types for the object, with your default record type preselected; click Next. With one or none, the form opens directly.
- The form lists every field the inbound mapping fills for that object, in the order the mapping saves them — including mapped fields this referral has no value for, so you can fill them in. Any other prefilled fields and the object’s remaining required fields follow. Fields Salesforce sets itself on create, such as Created Date and Created By ID, are not added as required inputs, and a mapped field the object does not have is skipped.
- Click Create. A toast confirms {Object} created: with a link to the record.
Only an Opportunity or Account created this way is linked back to the referral; an Opportunity also links its Account, if it has one. A Lead is created in Salesforce but is not linked to the referral. If the record is created but linking it fails, a sticky {Object} created, but linking to the referral failed error asks you to link it manually — use Link on the card rather than creating the record again.
Fours partner-to-partner (PRM) referrals are also included in the periodic Salesforce backfill, not only in single-record syncs — so a deal-reg referral that was created or changed between syncs still arrives in Salesforce on the next backfill run, without anyone pushing it across by hand.
Contacts on an AWS referral
AWS referrals carry contacts from three different sides of the deal, and the app keeps them separate so it is always clear who owns a given name.
On the AWS referral detail page
Contacts are grouped into three accordion sections, ordered by who owns the record — the customer, then AWS, then you:
| Section | Who is in it |
|---|---|
| Customer Contacts | The end customer’s people — the contact details submitted with the referral. |
| Cloud Contacts (AWS) | AWS-side people on the deal, such as the partner development manager. |
| ISV Contacts | Your own people on the deal — the partner contacts you supplied when sharing the referral. |
Each section shows its own empty state (“No contacts found”) when there is nobody in that group yet, so an empty Cloud Contacts (AWS) section usually just means AWS has not assigned anyone to the opportunity.
ISV Contacts rows carry an Edit button for changing the person filling a role. AWS owns the role, so editing preserves it: the role renders as static text and only first name, last name (each up to 80 characters), email, and phone can be changed. A role can never be renamed or removed — you replace the person in it, or fill it when it is still empty.
Phone is optional, but when given it must be in international format with a + and the country code, for example +12025550170. A number without the + is refused with “Enter the phone in international format with a + prefix.” rather than having a country code guessed for it — the same rule as in the Fours Console.
The two ISV roles render with their plain-English names rather than AWS’s internal codes:
| AWS role | Shown as |
|---|---|
PartnerAccountManager | Partner Account Manager |
OpportunityOwner | Partner Opportunity Owner |
AWS-side roles in Cloud Contacts (AWS) are deliberately not relabelled — AWS keeps adding to that list (PDM, WWPSPDM, ISVSM and others), and a fixed map would silently drop any role it did not know about.
On the AWS co-sell form
The AWS create form mirrors AWS Partner Central’s Add contact details step: one customer contact, plus two partner contacts whose roles are fixed for you.
| Section on the form | Role |
|---|---|
| Customer contact | The customer’s contact. Its Customer Title is free text — you type whatever the person’s title is. |
| Partner Contact - Owner | Fixed role: Opportunity Owner. |
| Additional Partner Contact - Account Manager | Fixed role: Partner Account Manager. |
For the two partner contacts, the role is part of the section heading rather than a field you pick, so there is nothing to select — fill in the name, email, and phone and the role goes across correctly. Leaving a partner contact blank is fine: empty partner contacts are dropped when the referral is submitted.
Share an AWS referral with partners
You can invite another AWS partner to collaborate on an AWS referral from Salesforce. Open the AWS referral and choose Share With Partners from its header menu. The Share with Partners dialog sends one invitation at a time:
- Sender: your Email (required), plus First Name - optional, Last Name - optional, Business Title - optional and Phone Number - optional.
- Partner: the Partner Connection Name (search for it), at least one Partner Engagement Type, and the Comments to share with the partner, all required.
Click Share Opportunity. A toast confirms Opportunity successfully shared with partner.
Share With Partners is disabled when any of these is true:
- AWS has not yet given the referral an opportunity ID.
- The referral already has 10 outbound invitations.
- The referral’s status is Draft, Create Failed or Deleted.
- Its stage is Launched or Closed Lost, or it has no stage yet.
- It is an inbound referral still waiting for you to accept it.
Each invitation you send is listed in the AWS referral’s Invitations section, with its Partner Name, Create Time and Invitation Status. AWS identifies the receiving partner only by its AWS account, so Partner Name shows AWS’s alias for that account, else the name of your partner connection for that AWS account ID, else the account ID itself. Click a row to open that invitation.
What the partner receives, and how invitations are tracked afterward, is in Outbound Referral.
The customer contact on a Fours (PRM) referral
In the Share Co-Sell wizard, after Postal Code, you can add the person at the customer the deal is about: Customer Contact Name, Customer Contact Email, and Customer Contact Role, all optional. A filled-in email must be an email address, or the field reads Enter a valid email. If your CRM field mapping fills the contact from the opportunity, the wizard keeps it.
The contact is set when you share the deal and can’t be changed afterward. On the referral’s details it shows as Contact: the name, the email as a link, and the role. A referral without one doesn’t show the field.
Whose product is being sold on a Fours (PRM) referral
Each partnership has a Relationship Type that says whose product is being sold in your co-sells with that partner. The Share Co-Sell wizard needs one before your first deal with a partner: until it is set, the wizard shows Relationship type required, Define whose product is being sold in co-sells with {partner} before sharing your first deal., and its Set Relationship Type button opens the Relationship Type dialog.
The dialog reads Defines whose product is being sold in co-sells with {partner}. Required before the first co-sell. and Whether {partner} is a reseller, referral partner or distributor is the Engagement Type, set separately. Pick one of three choices, and Fours saves it for the partnership:
| Choice | What the dialog says |
|---|---|
| Our product is being sold | We sell it. {partner} refers or resells it. |
| {partner}‘s product is being sold | {partner} sells it. We refer or resell it. |
| Both products can be sold | Decide per co-sell when you register the deal. |
With Both products can be sold, Share Co-Sell with Partner and the wizard ask Whose product is being sold in this deal?, with Our product — We sell it. {partner} brought the deal. or {partner}‘s product — {partner} sells it. We brought the deal. With either of the other two, the wizard states the answer in a banner, for example Our product is being sold in this co-sell.
When your product is being sold, you are the Seller on the deal; when the partner’s is, the partner is the Seller. The sections below use those words.
Your team on a Fours (PRM) referral
The Share Co-Sell wizard (titled Share Co-Sell with {partner}) collects the people on a partner-to-partner deal as one card per person, and what it asks for depends on which side is the Seller.
When you are the Seller — your product is being sold — the wizard has two sections, both Required, each led by a locked card:
- Your team opens with a locked Partner Manager card: the Partner Manager assigned to this partner, with their name and email. It has no Remove and cannot be edited. Its help text explains that the Partner Manager comes first, then anyone you add — a Salesforce User, a Salesforce Contact, or an existing Fours contact. If the partner has no Partner Manager, the section reads {partner} has no Partner Manager. Assign one in Partner Details before sharing.
- Their team · {partner} opens with a locked Champion card: the partner’s champion contact. If the partner has none, it reads {partner} has no partner champion. Set one in {partner}‘s Contacts before sharing., and its Add contact button stays disabled. Everyone in this section joins both sides’ contacts once the co-sell is accepted.
The cards you add after the locked ones are optional:
- On Your team, Add contact adds a Team Member card. Choose team member fills it from a picker — a Salesforce User, a Salesforce Contact, or an existing Fours contact — or you type the Name and Email yourself (Enter manually). Title is optional.
- On Their team, Add contact adds a Partner Contact card. Choose from their contacts lists the partner’s contacts who are not on the team yet, or you enter Name, Email, and Title by hand.
- Remove takes an added card off. Every card needs a name and an email.
Share Co-Sell is refused with Please complete the required fields. while the Partner Manager or the Champion is missing, or while any card lacks a name or email.
When the partner is the Seller, there is only Your team, with no locked card: add at least one person the same way (“People from your side working on this co-sell. Add a Salesforce User, a Salesforce Contact, or an existing Fours contact — at least one is required.”).
The Accept dialog on an inbound Fours referral (Accept Co-Sell, or Accept & Complete Co-Sell when you are the Seller) uses the same cards under Deal Owner Contacts (Seller Deal Owner Contacts when you are the Seller): Add contact adds a Partner Owner card, and at least one is required.
There is no role picklist on these cards — the roles are implied by the deal’s two sides, so there is nothing to select.
A reseller discount on a Fours (PRM) referral
A reseller who buys at a percentage off your list price and sets its own customer price can carry that as the deal’s terms. In the Share Co-Sell wizard, the Accept dialog, Add Partner and Edit terms, choose Reseller Margin as the Commission Type; the Revenue Share Model list then adds Discount off list price. The option is offered with Reseller Margin only.
With Discount off list price selected:
- The rate field reads Discount (%) and takes a value greater than 0 and at most 100.
- Payment Trigger is replaced by a read-only note, Payment trigger: not applicable. Nothing is paid to the partner; the discount is applied on the partner’s order., and Clawback Window (days) is not shown.
- The referral’s terms read Reseller discount: 20% off list price (not paid out) in place of the commission preview, and closing the deal Won starts no commission lifecycle.
When the partner has a commission plan whose Reseller Margin uses the discount, the Share Co-Sell wizard, the Accept dialog and Add Partner fill these terms in from the plan. Plans are set up in the Fours console; see Commission plans.
Terms are final once a partner’s deal is closed Won with nothing to track. For a partner on a discount, a 0% cut, or any other terms that produced no commission lifecycle, Edit terms is disabled, and hovering it shows This deal was closed Won with no commission to track, so its terms are final. Terms still marked TBD stay editable after Won.
Deal value on a Fours (PRM) referral
A Fours deal can be shared and accepted before it has a quote. It needs a value above 0 only to close Won.
- In the Share Co-Sell wizard, the field reads Deal Value when you are the Seller and Estimated Deal Value when the partner is. It is optional either way: leave it blank or at 0, as the line under it says, No quote yet? Leave it at 0 — the final deal value is required to close as Won. A negative value reads Deal value must not be negative., and a value that is not a number reads Enter a number. Deal Value Currency appears, and is required, once the value is above 0.
- In the Accept & Complete Co-Sell dialog, where you accept a partner’s deal as the Seller, the Deal Value section asks you to confirm or correct the partner’s amount. Deal value can be 0 or blank, Currency is required only when the value is above 0, and the same No quote yet? line sits under the fields.
- To close the deal Won as the Seller, choose Won from the referral’s Change Stage menu. This opens Complete & Close Won, whose Final Deal Value section has Deal Value and Currency. While the value is 0 or blank, the field reads A deal can’t be closed as Won with a value of 0. Enter the final deal value. and Close as Won stays disabled.
Older versions of the Fours package still require a value above 0 when you share or accept a deal as the Seller. Upgrade the package to get this behaviour (see Install the app).
Partner attribution on a Fours (PRM) referral
Every partner on a Fours deal carries an attribution role: Partner sourced, Partner influenced, or Transacted. It is recorded whether or not your org runs commissions, so a partner can always see how the deal credits them. A role saved before these three became the only choices shows as it was typed.
When you are the Seller and share the deal, the Share Co-Sell wizard’s Attribution section (Required) has an Attribution Role picker, starting at Sourced, and the Deal Value Visibility choice, Show deal value or Hide deal value. Add Partner asks for the same two.
When a partner registers a deal with you, the wizard has no picker. Registering claims the deal as partner sourced, so the section reads Your role on this deal: Partner sourced · awaiting confirmation, with the note Registering a deal claims it as partner sourced. {Seller} confirms it, or sets a different role, when they accept. It’s saved whether or not commissions are on. On your public deal registration form, the partner picks its own role when your form asks for it, and a deal sent with no role carries no claim (see Take Deal Registrations Through a Public Link).
Confirming the claim. As the Seller, the Accept dialog on a partner’s registration has a required Attribution section, prefilled with the partner’s claim, or with the role picked on your public form: {Partner} registered this deal, so it’s saved as {role} until you confirm. Change it if your records differ. When the partner picked no role, nothing is selected, the section reads {Partner} didn’t pick a role on this deal. Pick one to accept., and you can’t accept until you pick one. Keep the role to confirm it, or pick another; a different role adds the note {Partner} will see {role} on their copy, with “Changed by {your org}” in Activity. A partner accepting a deal you shared sees its role read-only (Your role on this deal: {role}), with {Seller} sets partner roles. If this looks wrong, reply in Collaboration after accepting.
On the referral’s details, the Attribution section shows, for the Seller, one tab per partner with Partner role, Partner, Deal Value Visibility (Visible to partner or Hidden from partner), and who set it:
| Row | What it shows |
|---|---|
| Claimed by | The partner, by registering, and the date. Shown on a partner’s registration. |
| Set by | Your org and the date the deal was shared. Shown on a deal you shared. |
| Confirmed by | Who confirmed the role and when — you, on a claim; the partner’s acceptance, on a share — or Not yet. |
| Last changed by | Who last changed the role, and when. Shown once it has been changed. |
Commission Terms follow only when commissions apply to the deal. With commissions off, a note says the deal tracks attribution and deal-value visibility only. A partner sees its own copy under Your attribution, read-only: Your role on this deal, Seller, Deal Value Visibility (Visible to you or Hidden by seller) and the same who-set-it rows.
Changing the role later. Only the Seller changes a partner’s role, from the section’s Edit button, which opens the role and the deal-value visibility together; Save sends both. The button is disabled, with the reason on hover, when:
- the deal was closed Won — the role and visibility are then final;
- the partner declined the referral, or the deal was closed Lost with that partner;
- the co-sell is still pending acceptance.
While a partner’s claim is awaiting your confirmation, the role stays read-only in the edit; you confirm or change it when you accept. The Partners & Status table in Deal Details also lists each partner’s Attribution Role.
In the referral list, the Partner Role column shows the role on every Fours referral. On your own deal as the Seller it lists each partner with its role, for example Acme: Partner sourced, Beta: Partner influenced. On a deal you joined as a partner it shows your own role, with (awaiting confirmation) while the Seller has not yet accepted your registration. A role that isn’t set reads Not set, and your own deal with no partners on it shows —, as do AWS, Azure and GCP referrals. The column appears only when you can view Fours referrals and your org has at least one partner connected through Fours, the same rule as the Co-Sell via Fours action on an Opportunity.
For reports, the synced Referral record carries the role in PRM Partner Role (PRM_AttributionRole__c), available in the Cloud Referrals (Fours) report type. The value is the role as Fours stores it and the Fours API returns it, not the label the column shows: sourced, influenced or transacted, so a Flow, Apex or report filter can match it exactly. Only those three are written; any other stored role is left out. A partner’s record holds its own role. The Seller’s record holds every partner’s role, each once and without partner names, always in the order sourced, influenced, transacted, separated by ; , so you can group or filter on it: sourced; influenced. It updates when you accept a partner’s registration, change a partner’s role or remove a partner.
To report which partner holds which role on a deal with several partners, use the Referral Partners (Fours) report type, which has one row per partner on each deal — see Reports.
For the same roles in the Fours Console, see Track and respond to deals.
APN Programs on an AWS referral
APN Programs is a multi-select on the AWS referral. The package carries the full AWS list of eighteen programs, including Cloud Adoption Framework Program (CAF), P3, WWPS NDPP, and Model Provider PARC:
| APN Immersion Days | ISV Immersion Day SFID Program | Partner Opportunity Acceleration Funded |
| APN Solution Space | ISV Workload Migration | The Next Smart |
| ATO (Authority to Operate) | Migration Acceleration Program | VMware Cloud on AWS |
| AWS Marketplace Campaign | Model Provider PARC | Well-Architected |
| Cloud Adoption Framework Program (CAF) | P3 | Windows |
| Partner Launch Initiative | Workspaces/AppStream Accelerator Program | WWPS NDPP |
Seventeen of the eighteen are selectable when you share a referral outbound — every one above except Model Provider PARC. All eighteen are selectable when you edit a referral that AWS originated.
The referral detail page shows the selected programs under APN Programs in Project Detail, semicolon-separated (Model Provider PARC; Well-Architected). The Apex Action accepts that value as-is — it trims each program, so a string copied from the detail page works whether or not you remove the spaces.
Timestamps on the referral detail page
Every referral pane shows how fresh the partner’s copy is, read from Fours’ unified external timestamps rather than from each partner’s own payload:
| Pane | Date rows |
|---|---|
| AWS | Created Date, Last Updated Date |
| GCP | Creation Date, Last Updated Date |
| Azure | Created Date and Last Updated Date |
Both render as YYYY-MM-DD HH:MM — for example 2026-09-02 16:12 — on a 24-hour clock, in your own timezone. That is the same YYYY-MM-DD the other dates on the pane use (Estimated Close Date, Target Close Date, Submitted Date), so a whole pane reads in one format; the time of day is kept because a “last updated” without an hour cannot tell you whether the partner’s copy moved this morning or last week.
An Azure draft that Partner Center has never seen renders both blank. The Opportunity card on the referral also shows the CRM-side Stage, so the partner’s stage and your Salesforce stage can be compared without opening the Opportunity record.
AWS Lifecycle and errors on an AWS referral
AWS keeps its own view of an opportunity’s progress, separate from the stage you maintain. The AWS referral detail page shows it in an AWS Lifecycle section, open by default:
| Field | What it shows |
|---|---|
| AWS Stage | The stage AWS has the opportunity at. |
| AWS Closed Lost Reason | AWS’s reason, when AWS has closed the opportunity as lost. |
| AWS Close Date | AWS’s target close date for the opportunity, not the date it actually closed. |
| AWS Next Steps | The next steps the AWS seller entered on the opportunity in AWS Partner Central — separate from your own Next Step in Next Steps. |
Each reads - until AWS reports it. Because AWS can close an opportunity as lost on its side while yours is still open, check this section when the partner’s stage and yours disagree. The sync also writes the reason, the date and AWS’s next steps to the Referral record’s AWS Closed Lost Reason, AWS Close Date and AWS Next Steps fields — see Referral__c AWS fields. AWS Next Steps is cleared when AWS clears it, and AWS’s history of earlier next steps is not synced.
When a create or update fails, the top of the page reads Referral creation failed or Referral update failed, followed by the latest error. Show other error records (N) opens the earlier errors on the referral; Hide other error records closes them. An error recorded with a timestamp shows that time beneath it, in UTC. The icon on the referral’s status in the Fours widget shows the same latest error on hover.
Notes & Attachments on a Referral
Every referral detail view (AWS, Azure, GCP, and Fours deal-reg) has a Notes & Attachments section at the bottom of the page, so the deal’s supporting materials — private offer PDFs, deal-registration confirmations, customer requirement documents, call notes — live on the referral itself instead of scattered across email and drives.
What you can do:
- Upload Files — attach one or more files to the referral. Files are stored as standard Salesforce Files, so they also appear in Files home, global search, and reports.
- New Note — write a titled note with basic formatting (bold, italic, underline, lists). Notes are standard Salesforce enhanced notes: you can open and edit them later with the native note editor, and they render identically there.
- Preview / Download / Delete — each row’s action menu opens the native file preview, downloads the original file, or removes the item from the referral. A file that is only attached to this referral is permanently deleted; a file that is also attached to other records is detached from this referral only (the file itself is kept, along with its other locations). Delete is only offered on items you added yourself (Salesforce file ownership rules); other people’s items are managed by their owners or by an admin through standard Files pages.
Permissions: the section follows your referral permissions. With read-only access (for example the Fours Cosell (Read Only) permission set) you can view, preview, and download items, but the upload, note, and delete controls are hidden.
Troubleshooting common issues
| Issue | Possible cause | Resolution |
|---|---|---|
| No Co-Sell button visible on the opportunity | Fours permission set not assigned, or the Fours widget is not on the page | Check your permission set. If the widget is missing, add it to your page layout. |
| Only one or two cloud partners appear in the partner selector | Your permission set restricts co-sell access to specific clouds | If you need access to additional clouds, ask your Salesforce admin to update your permission set. |
| Form fields are blank — not pre-filled from the opportunity | Field mapping has not been configured | Field mapping is an optional admin setup. Contact your Salesforce admin to configure it. |
| Referral was submitted but does not appear on the opportunity | Sync between Fours and Salesforce is delayed | Referral records sync on a schedule. Refresh the page after a few minutes. If it still doesn’t appear, confirm the referral was created in the Fours Console. |
| An AWS referral’s Engagement Score reads Not provided by AWS | AWS has not scored this opportunity yet | The referral shows AWS’s own score once AWS scores the opportunity. The field API name is Suger__AWS_EngagementScore__c if you want to use it in automations. The Fours Predicted Engagement Score in the Fours widget is Fours’ own prediction, not AWS’s: it is never written to the referral, so it does not fill this field. Azure and GCP supply no score of their own, so their referral cards show a Fours Predicted Engagement Score row instead. |
| A referral created directly in AWS ACE is not showing in Salesforce | ACE referrals only sync to Salesforce after an update event | The referral appears in Salesforce after AWS accepts it or after you manually edit something. To link it to a specific opportunity, enter the Salesforce opportunity ID in the Partner CRM Unique Identifier field in ACE. |
| A referral has a Partner CRM Unique Identifier in ACE but is not linked to the opportunity | Something other than a Salesforce Opportunity ID is in the field | Either spelling of the Salesforce Opportunity ID works — the 15-character case-sensitive form and the 18-character form are both normalized before matching, so you can paste whichever one your org surfaces. If the link still doesn’t form, check that the value really is an Opportunity ID and that the opportunity exists in the connected org. |
| After Accept or Reject on an AWS engagement invitation, the referral does not change | AWS refused the request | Hover the icon on the invitation’s status badge: it reads Update Failed: followed by AWS’s reason. The referral keeps its previous status, and the message clears when a later accept or reject succeeds. |
| Changes to the Salesforce opportunity stop reaching its AWS referral, which shows Update Failed with a reason starting CRM sync rejected: | Fours’ AWS update check rejected the values the sync derived from the opportunity — for example, Once the opportunity reaches Committed stage or beyond, ‘Other’ is no longer accepted — please select a valid solution identifier. The referral keeps its status, and nothing is sent to AWS. | To read the full reason, hover the error icon beside the referral’s status on its card in the Fours widget, or, on a partner-originated referral, open its Status panel. Correct what the reason names: the value mapped from the opportunity, or the referral data it conflicts with (in the example, a valid solution). The sync re-checks the opportunity on every scheduled run, and once the values pass, a later sync clears the message. |
Frequently Asked Questions
Q: What’s the difference between a co-sell referral and a private offer?
A co-sell referral shares your deal with the cloud provider’s partner team so they can help you close it. A private offer is a custom-priced contract you send directly to a buyer. They serve different purposes — co-sell is about getting the cloud partner involved in the deal; a private offer is the actual transaction.
Q: Do I need to manually update the referral every time the opportunity changes?
No. Fours automatically syncs changes from your Salesforce opportunity to the referral once per hour. If you update the close date, stage, or any mapped fields on the opportunity, those changes flow through to the cloud partner automatically.
Q: Can I submit a referral to more than one cloud partner for the same opportunity?
Yes. You can submit separate co-sell referrals to AWS, Azure, and GCP from the same opportunity — just click Co-Sell again and select a different partner.
Q: Can I see the AWS engagement score on the opportunity page rather than just on the referral record?
Not by default, but it is possible. Your Salesforce admin can set up a formula field on the Opportunity object that pulls in the score from the referral record. The field API name is Suger__AWS_EngagementScore__c. That field holds only AWS’s own score for the opportunity. The Fours Predicted Engagement Score shown in the Fours widget is not stored on the referral, so a formula cannot pull it in.
Q: What happens if I created a referral directly in AWS ACE instead of through Salesforce? Will it show up?
Yes, but not immediately. It appears in Salesforce after AWS accepts it or you manually edit something in ACE. To connect it to the right Salesforce opportunity, enter the opportunity’s Salesforce ID in the Partner CRM Unique Identifier field in ACE — Fours will then associate them automatically.
Spotted something wrong or out of date on this page? Tell us and we'll correct it.