Opportunities

#From deal to ACE opportunity

When a tracked deal reaches the gate stage, or someone approves it in the review queue:

1. CoSell reads the deal, its account and its contact from Zoho.
2. It builds the ACE opportunity from your mapping and checks it against AWS's rules first. It needs a title, a customer company and website, an industry, a country, a close date in the future, a positive monthly spend, and a business problem of at least 50 characters. AWS also needs a delivery model, the sales activities so far and the customer use case, each chosen from AWS's own list. If something is missing, the deal shows needs information with the list, and nothing is sent.
3. It creates the opportunity, attaches your solutions and submits it to AWS for review.
4. It writes the ACE opportunity ID, the Partner Central link and the review status into the Zoho deal.

#Statuses

AWS's review status is shown next to it: Pending Submission, Submitted, In review, Action Required, Approved or Rejected.

#Finding deals

Every list in the console works the same way: Opportunities, the review queue, Pipeline health, AWS invitations, Sync errors, Notifications, Bulk jobs and the Audit log.

• Search finds every word you type, in any order. On Opportunities that means the deal and customer names and the Zoho and ACE IDs.
• Filters show how many items each choice would leave. Clear filters puts them all back.
• Sort by clicking a column heading. A second click reverses the order.
• Page size can be 25, 50 or 100 rows.

What you choose is kept in the page address, so you can bookmark a view, share it with a colleague, or come back to it with Back.

#What AWS lets you change

AWS controls what can change after submission, and CoSell follows the same rules:

• Submitted / In review: read-only until AWS responds.
• Action Required: only the fields AWS asked about can change.
• Approved: most fields can still change. AWS locks the title, the customer's country, postal code, industry and website, the business problem and the partner identifier. Edits to those in Zoho are not sent.
• Rejected: read-only.

#Updates in both directions

• Zoho → AWS. Editing a tracked deal sends the change within seconds. CoSell compares each field with what it sent last and sends only fields changed in Zoho.
• Changes made in Partner Central stay. If you move the stage, or change another field, in Partner Central, CoSell does not send Zoho's older value back over it. That field goes to AWS again only once it changes in Zoho.
• AWS → Zoho. Review status, comments, the AWS seller, engagement score, stage and close date come back through Partner Central events. A reconciliation every 15 minutes catches anything missed.
  • AWS's stage is shown in the deal's ACE Stage field. The Zoho Stage itself is not moved.
  • Pipeline health flags a deal whose two stages disagree.
• If Zoho and AWS change the same field within five minutes of each other, CoSell records a conflict under Sync errors for you to confirm.

#On the opportunity page

• Sync from Zoho, Refresh from AWS and Submit to AWS now. The last one submits a deal that is outside the filter or below the gate, but never a closed one.
• What AWS says: review comments, involvement, engagement score, expected spend, the AWS team and next steps.
• Needs attention: this deal's pipeline health findings, with their fixes.
• Draft next steps and summary: drafts from the deal, its notes and pasted meeting notes, saved only when you approve (Drafts and approvals).
• Ask Partner Central: ask AWS's agent about this opportunity.
• Partners on this opportunity and AWS Marketplace private offers.
• Opportunity quality coach: scores the business problem the way AWS validators read it and suggests a stronger version. Nothing is written back automatically.
• Sync history: every attempt, with direction, outcome and latency.

#Many deals at once

Tick deals to change their stage or fields, or to reassign them in Partner Central, now or later. Import CSV creates deals from a file. See Bulk operations.