A useful deal tells you what the buyer is considering, where the decision stands, and who will do what next. If any of those answers lives only in a salesperson's memory, the opportunity is hard to manage.
Use this walkthrough for a fictional request for an annual support package. There is no named customer, assumed revenue, or promised result. Replace the example's decisions with your own sales rules. At every step, inspect the saved record before moving on.
Decide when a request should become a deal
Write down your threshold for an opportunity. A contact asking for a brochure might need a response without entering the pipeline. A buyer discussing a defined service, a decision process, and a likely purchase date might meet your threshold. The distinction is a team decision; a record alone does not prove qualification.
For the support-package example, suppose your rule requires an identified account, a contact involved in the decision, and a specific need. Budget remains unconfirmed. You can create an early opportunity if your process allows that, but label the unknown clearly. Do not turn uncertainty into an invented amount or a later stage.
Keep the three identities separate:
- The account represents the organization you are dealing with.
- The contact identifies the person involved in the conversation.
- The deal describes this particular buying decision.
A company can discuss a renewal and a separate new purchase at the same time. Give each opportunity a name that distinguishes the scope and decision period. Avoid using only the company name, which tells the next person little about the sale.
Before creating anything, search for the existing opportunity. Compare the account, scope, and current conversation. A fresh request may be an update to an open deal rather than a new sale. If two records look plausible, resolve that ambiguity with the owner before proceeding.
Zoho documents manual creation, imports, and deal creation during lead conversion in its deal creation guide. Choose the route that matches the source of the request. For qualification before that point, use the guide to leads.
Your qualification note should explain why the opportunity exists now. “Asked about support” is too vague. “Requested an annual support proposal and agreed to discuss coverage with the operations contact” gives the owner a concrete next conversation. It still leaves price and timing open if those were not discussed.
Create and link the opportunity
Prepare the values before opening the creation form. For the fictional request, use a worksheet like this:
| Item | Example entry or decision |
|---|---|
| Deal name | Annual support package — evaluation |
| Account | Select the confirmed existing account |
| Contact | Select the person who made the request |
| Owner | The salesperson responsible for the next action |
| Stage | Your earliest qualifying open stage |
| Amount | Confirmed value, or an explicitly unresolved value |
| Closing date | Your documented planning date, with its basis recorded |
| Next action | Confirm support coverage with the buyer |
Check your layout for required fields and use your organization's actual stage names. A planning date is not a customer commitment. If you must enter one before the buyer confirms timing, explain that basis in the note and give the owner a task to validate it.
Create the deal, select the intended account and contact, then save. Reopen the record. Read the names and identifiers of the linked records rather than relying on a similar-looking search result. Check the owner, amount, stage, and closing date against your worksheet.
The deal details page brings related accounts, contacts, activities, notes, and emails together. That makes it a useful inspection point, but it does not make every association automatically correct. Open the related contact and confirm that it is the person from the request.
Where the Zoho CRM AI Assistant helps
You can ask the Assistant to create the same opportunity from the request:
Find the existing account and contact using the identifiers I provide. Check for an open deal about the annual support package. If none exists, prepare a deal with the agreed owner, our initial qualification stage, and the planning closing date below. Leave unconfirmed facts unresolved. Show the links and proposed values for approval before creating it.
The Assistant works on the CRM task you request and changes data only after you approve. It can also handle the surrounding CRM configuration, such as adding a needed field or adjusting a workflow. Give it the intended business rule rather than asking it to guess how your team sells.
After approval, inspect the actual record and its links. If the request concerns information from another system, provide that information or its export. The Assistant prepares and fixes the Zoho CRM side; it does not operate an external finance or sales application for you.
Keep the creation check small enough to repeat. Ask the owner to read the saved record and say what happens next. If that answer differs from the note, fix the record while the request is still fresh.
Map stages to real sales decisions
A stage should represent evidence, not effort. Sending an email is work you did. Receiving agreement on the proposal scope is a change in the buying decision. Write stage entry criteria in terms that another salesperson could verify from the record.
For example, your early stage might require a confirmed need and a named contact. A proposal stage might require agreed scope and a proposal delivered to the right buyer. A decision stage might require a known decision date and an identified approver. These are illustrative definitions, not Zoho defaults.
Zoho's documented deal categories include open, closed won, and closed lost. Check how your stage names map to those categories. A stage that sounds nearly finished can still represent an open opportunity. A lost decision should not remain in an open category merely because someone hopes to restart the conversation.
Stage probability contributes to expected revenue. Treat that probability as a forecasting assumption tied to your process. Do not change it on a single opportunity just to make the forecast look better. If your team revises stage assumptions, record the reason and check the effect on the pipeline report.
Review three representative records:
- An open deal should have evidence for its current stage and a future action.
- A won deal should have a confirmed buying decision and a clear handoff.
- A lost deal should explain the outcome and whether a future revisit is appropriate.
If a record fails the test, decide whether its stage is wrong or the evidence is missing. Ask the owner before moving it. A weak note does not prove that a real customer conversation never happened.
Use the pipeline guide when you need to align these definitions across the team. Keep the definitions short enough that people can apply them during an ordinary update. A stage model that requires a separate interpretation meeting for every deal will be difficult to maintain.
Also agree how to handle stalled opportunities. Lack of activity can trigger a review, but it should not silently become a lost decision. The owner needs to explain whether the buyer delayed, the next step was missed, or the request is no longer active.
Update the deal after every conversation
Capture the conversation while you can still distinguish what the buyer said from what you inferred. Separate confirmed changes, unanswered questions, and your next action. Avoid copying a long transcript into a record without identifying the decision it contains.
For the support-package example, imagine the buyer confirms the coverage scope but has not approved a budget. They ask for a revised proposal before an internal meeting. You now have a scope update and a next action. You do not yet have a won deal or a reliable final value.
A useful update sequence is:
- Save a concise note identifying the conversation and its participants.
- Update only the fields supported by explicit statements.
- Create the next task with an owner and an unambiguous due date.
- Reopen the deal and verify the note, fields, and task together.
Ask the Assistant:
On the identified support-package deal, save these call notes. Record the confirmed scope, keep the amount unchanged because budget is unconfirmed, and create a proposal-revision task for the existing owner due on the date below. Do not advance the stage unless the notes meet our proposal-stage criteria. Show the changes before writing them.
The call-note update workflow is useful when one conversation produces several CRM actions. Review each output separately. A saved note does not prove that the task was created, and a task does not prove that its due date is correct.
Read dates literally. Replace “next Friday” with the actual date when preparing the request. Identify the responsible salesperson, especially when a colleague took the call while the owner was away. Put unresolved ownership questions in the review queue rather than assigning the work by guesswork.
If an email does not appear under the deal, inspect the contact association, the message's intended recipient, and your email configuration. The related-email area is an inspection surface, not proof that every message should be attached there. Check Zoho's help docs for the behavior of your current email setup before changing associations or resending anything.
Similarly, do not create a second deal to make a missing email appear. First establish whether the existing deal is the right opportunity. Keep a note of the communication while you investigate its association.
Find opportunities that need attention
Use the list and stage views documented for Deals to review the pipeline from two angles. A stage view helps you inspect progress. A focused list helps you work through exceptions. Neither replaces a clear definition of what requires action.
Start with overdue closing dates. Define the review as open opportunities whose planning closing date is before today. For every match, ask the owner whether the customer decision moved, the record was neglected, or the opportunity should close. Change the date only when you have a new basis for it.
Next, review open deals without a useful next activity. “No open activities” and “no useful next step” are related checks, but they are not identical. A generic task with no date may exist while the buyer's next decision remains unmanaged. Conversely, an owner may have a legitimate next step documented elsewhere that needs to be captured consistently.
Use an exception worksheet:
| Exception | Question for the owner | Acceptable resolution |
|---|---|---|
| Closing date passed | What changed in the decision timing? | Confirmed revised date or recorded outcome |
| No next action | What happens next, and who owns it? | Specific owned task with a date |
| Stage lacks evidence | What supports the current stage? | Added evidence or agreed stage correction |
| Amount is uncertain | Which value is confirmed? | Correct value or a visible qualification question |
| Contact is unclear | Who is involved in this opportunity? | Verified association and a useful note |
Ask the Assistant to list the records before resolving them:
Review open deals in the agreed scope for overdue closing dates and missing next steps. Show each deal, owner, reason for inclusion, and available evidence. Propose the smallest correction for each. Do not move closing dates or create generic tasks merely to remove records from the list.
The deals without a next step check gives you a practical starting point. Work through the exceptions with the owners, approve the changes, and run the same check again. Keep unresolved cases visible with a reason and a responsible person.
If the interface contains unwanted filters, distinguish your review criteria from the available filter controls. You can decide which criteria your operational check needs without assuming every built-in filter can be removed. Check Zoho's help docs for your view and interface before attempting changes to its controls.
Close the deal and verify the handoff
Before marking the support-package opportunity won, establish what the customer accepted. Check the final scope, agreed value, customer contact, and handoff owner. Confirm that outstanding questions about terms or delivery have a responsible person. Use the pre-close check to make the review repeatable.
If a quote supports the decision, compare its accepted version with the deal. Do not assume the most recently edited proposal is the one the buyer accepted. The quotes guide explains a separate line-item and follow-up check.
For a lost decision, record the reason in useful language. “Lost” repeats the category without explaining anything. A note such as “Buyer postponed the project until its next budget review” gives future readers context. Do not select a convenient reason if the buyer never supplied one; record that the reason is unconfirmed.
Ask the Assistant to prepare the closure update and list the tasks that remain. Review whether each task should be completed, cancelled through your process, or retained for the handoff. An accepted sale can still need delivery preparation. A lost opportunity can still need a final response or an agreed future review.
Finally, reopen the saved deal. Verify its category through the chosen stage, its final values, linked records, closure context, and remaining responsibilities. Have the receiving owner confirm that they can understand the handoff from the record itself. The finished opportunity should explain the decision without requiring someone to reconstruct the conversation from memory.
Watch it done
See the Assistant find deals that have no next step.
Watch: Find Zoho CRM deals with no next step | Zoho CRM AI Assistant