Qualification begins with an identifiable customer request and an accountable Relationship Owner. The guarded action checks evidence already associated with the opportunity; it does not provide a separate managerial approval. Configure the action and its denied paths before using it for the team's ordinary pipeline.
App Administrator confirms the company code, owning organization and eligibility context. Relationship Owner selects the intended customer company rather than importing another customer record under a different spelling.
Relationship Owner creates the New opportunity with opportunity number, subject, owner, expected close date, expected USD sales value and revision. Confirm that the owner resolves to an active member in the permitted organization.
Relationship Owner records the actual customer discussion and attaches supporting files where needed. Existing evidence must explain why the request is qualified; a blank activity outcome cannot support the action.
The configured qualification action validates the page-supplied actor, checks the revision and prevents repeated effects for the same operation key. It logs the qualification evidence as a customer activity, advances New to Qualified and writes the operation receipt.
Relationship Owner identifies whether a drawing or material question needs engineering inquiries. Preserve the qualified opportunity context and use the next appropriate action rather than treating qualification as a feasibility decision.
And how to keep it from happening.
Start free, then use Proto to change fields, steps and approvals before your team goes live.