Lead and opportunity operations
Lead and opportunity management lets you register leads, record follow-ups, convert qualified leads into opportunities, and update sales stages and outcomes. Data is isolated by organization, Application, product, and environment.
Delivered sales features are available in your own application scope without a separate capability request. Application owners and collaborators use their current duties and data scope.
Enable the capability
In Developer Console, select your organization and application, then open Customer operations → Leads or Opportunities. The platform checks your current application access and duties before reading records. No aggregate configuration or second enable step is required.
If a menu is missing, check the current application's capability state and your sales permissions. Records remain closed when the capability is inactive or suspended, read permission is absent, or permission cannot be confirmed. Lead read, manage and convert, and opportunity read, manage and reopen are separate permissions. Company access does not grant sales access. Sandbox and Production are configured separately and do not share sales records.
Register and convert a lead
- Open Leads and choose Create lead. Supply the source system, original source reference, company name, contact and owner references, lawful collection basis and its reference, and an operation reason.
- The source system and reference identify the original lead. Registering that source again in the same scope causes a conflict. Find the existing record instead of changing the source to create another lead.
- Open the record and choose an allowed action to edit details, assign an owner, add a followup or assess qualification. Recorded followups are immutable; add another followup to clarify an earlier entry.
- To mark a duplicate, search for and select the target lead in the current application. This records the relationship and preserves the original record.
- A qualified lead can be converted to an opportunity. Supply its name, requirements, owner, estimated amount and currency, expected date, and reason. The converted lead becomes read-only and retains the opportunity reference.
Contact, assignee and collection-basis references should come from your lawful presales process. Entering them does not verify customer identity or grant personnel-data or marketing access.
Conversion saves the lead and opportunity together. Customer companies, payers and product eligibility require separate setup.
Opportunity stages and outcomes
Depending on your permissions, edit requirements, an exact estimated amount, expected date, owner and sales stage. Amounts are sales estimates. Record a reason for a win or loss; a win does not confirm an order, payment, provisioning or revenue.
Closed opportunities are read-only. With separate reopen permission, provide a reason to return to a pre-sales stage while preserving the previous win or loss. Quote linking and customer-company summaries are not yet available. An opportunity cannot replace an approved quote or transaction terms.
Search and recover
Search and status filters apply to all records within the current scope. Load more reads the next page. The directory is live rather than a fixed snapshot. If a later page fails, loaded records remain available and retry uses the original cursor.
Unknown results preserve and lock the original form:
| Condition | Action |
|---|---|
| Timeout or temporary unavailability | Choose Recover original request with the same content, version and key to avoid duplicate leads |
| Version conflict | Keep the draft, read the current record and review changes before confirming the new version |
| Success | Query current state; the original receipt may describe an earlier state |
Revocation or switching organization, application or environment clears old records and unfinished forms. If reading remains unavailable, confirm current capability and permissions before contacting support.
Defaults and automatic recovery
Application owners can use basic company, lead and opportunity actions for the current application immediately after activation. They do not need to create roles or assign permissions. Other members use their assigned permissions; commercial links, purchase history and payments retain their separate checks.
Menus update immediately after activation. Temporary failures retry automatically, then every 30 seconds until ready. You can choose Check menus again; returning to the page checks again.
Disabling hides the entry; disabling prerequisites also disables dependent capabilities. Settings and history remain and are checked on reactivation. Contact support for operator suspension.