This is an illustrative story; Maria and the other characters are made up.
Maria's new responsibility arrived in a short message: could she look after Zoho CRM?
She knew the sales process. She answered questions, found missing records, and helped colleagues remember their next steps. Now she was also the person expected to change the system.
Her first request sounded small. Add fields for a deal's buying context, put them together on the layout, and create a follow-up task when a quote reached Delivered.
Maria wrote the request in her notebook. Then she underlined “live CRM.”
The uncomfortable save button
She opened Setup and looked at the existing fields. A label sounded close to one of the requested fields, but she could not tell whether it meant the same thing.
She opened the layout, found a section, and considered where the new fields should go. Then she backed out to check the original request.
For the workflow, she opened the rules and read their names. Was there already something similar? Would her new rule run on every edit? Would it create tasks for old quotes? Which person would receive the task?
The menus were only part of the problem. Maria wanted to understand the effect of the change before she pressed Save. A correct-looking field in the wrong place could confuse the team. A poorly scoped rule could keep creating work nobody wanted.
She sent a question to a former colleague, who now looked after CRM at another company. They suggested using the Zoho CRM AI Assistant to inspect the setup and prepare the change with her.
Asking for the job in ordinary words
Maria opened the Chrome side panel with approval mode enabled. She kept the field change separate from the workflow, so she could review each part without rushing.
Inspect our Deals fields and layout. We need a Buying context section with a Decision process text field and a Procurement notes multiline field. Check whether equivalent fields already exist. Show the proposed field types and placement, and wait for my approval before creating or moving anything.
The assistant inspected the existing fields and layout. Maria reviewed the proposal against what the sales team actually meant. She checked the field types and section placement, then approved the proposed writes.
The assistant created the agreed fields and updated the layout. Maria opened a deal to check the result herself. The custom-field use case describes this kind of request: name the module, fields, types, and section, then review what will be added.
She had not needed to guess her way through the whole configuration. She still understood what she was asking the system to store.
The rule deserved its own pause
Next came the part Maria had been most nervous about.
Inspect Quotes workflow capabilities and existing rules. When Quote Stage changes to Delivered, create a Follow up on quote task for the quote owner, due three days later. Show the trigger, condition, task action, and activation effect before creating anything. Wait for approval.
The assistant checked the module's supported triggers and actions, existing rules, and task actions. It proposed the rule and its follow-up task.
Maria read the trigger carefully. She wanted a stage change, not a task on every unrelated edit. She checked that the task would belong to the quote owner, which matched the supported workflow described in task after a quote is sent.
Creating a workflow is a critical action in the side panel. Maria reviewed the final confirmation before proceeding. The rule would be active when created; the assistant's proposal was not an isolated practice environment. Existing quotes already sitting at Delivered would not receive tasks simply because the rule was added.
After confirmation, the assistant created the task action and rule. Maria used an agreed test quote to check the stage transition and resulting task. She also checked an unrelated edit, so she could explain when the rule should stay quiet.
A change she could explain
Maria wrote down the field meanings, section placement, trigger, task owner, and test outcome. She showed the sales team where to enter the buying context and what would happen after a quote was delivered.
She still planned to ask for expert help with unfamiliar process decisions. The assistant had not decided the company's sales policy for her. It had helped her turn an agreed request into CRM configuration she could inspect.
For more background, the layout guide and workflow guide explain the decisions behind those changes.
Try it with your own CRM
Your account needs API access, the relevant Zoho features, and permission to change setup. Start with a clearly named module and a small change.
Inspect these requested fields against our existing Deals fields. Show possible duplicates and a proposed layout placement. Make no changes yet.
Propose a quote follow-up rule with its trigger, criteria, record owner, and due date. Explain when it becomes active before asking me to confirm.
Maria could now answer the question behind her new responsibility: yes, she could look after this change, understand it, and check it. No more clicking it all yourself.