Hair transplant candidate flow: from photo review to operation day

A first message from a hair transplant candidate rarely carries enough information. The photo is the central input for assessment. Before defining stages in Zoho, decide which record and structure will hold that photo, and who can access it. This choice shapes personal-data marking, search coverage, edition requirements, and every assessment step that follows. The stage list should come only after these boundaries are clear.

The flow is more than a status field showing where a candidate stands. The photo must reach a record, the physician's decision must be written, the lead must convert at a defined moment, the request must reach the right coordinator, and the operation date must remain consistent. Each step uses different data structures, so define the record model and access before naming the stages.

The flow starts with the photo's location

A photo supports graft estimation and suitability assessment. Keeping it on a coordinator's phone does not create the same working model as storing it with the candidate record. Decide who reviews the image, where the physician writes the decision, and where the team reads that decision during a later conversation. Stages can then rest on an explicit assessment point instead of an unrecorded chat history.

A coordinator reviews photos received at night on a personal phone and shows them to the physician the next morning. The physician answers verbally, leaving no record updated. Three weeks later, when the candidate repeats the question, the team searches through a chat history. The problem is not the channel itself. It is the absence of one record joining the photo with the decision.

Choose the photo structure from the start

Image upload fields, file upload fields, and note attachments are separate structures in Zoho records. Per module, image and file fields are limited to 2 in Standard, 5 in Professional, 10 in Enterprise, and 15 in Ultimate. Up to 10 images can be uploaded at once, with a 20 MB limit per image or field file. A note accepts up to 5 files totalling 20 MB.

A web form file-upload field is available only in paid editions. The form accepts no more than 3 files with a combined 20 MB limit. If that boundary is exceeded, submission fails and no record is created. Set the requested photo count before publishing the form. Form fields can be required or hidden, a privacy consent box can be added, and owner and sender notifications can be configured separately.

Patient photos require separate sensitive-data marking

Personal fields can be marked Normal or Sensitive; health information and medical records are Sensitive examples. File and image upload fields can be marked, with a limit of 30 marked fields per module. This facility applies to leads, contacts, vendors, and custom modules, but not team modules. The Manage Compliance Settings profile permission is required.

This Zoho marking restricts data transfer through four channels: export, API access, transfer to Zoho applications, and transfer to third parties. Its documented technical effect ends there. Do not present the setting as a legal compliance result. The institution's legal team must determine the photo's legal classification and any additional safeguards; the product setting does not perform that assessment on its own.

Define the moment a lead becomes a patient record

Lead conversion creates an account and contact first, with an optional deal, and cannot be reversed. An account is created only when the company-name field on the lead is populated. For an individual patient, leaving that field empty produces only a contact. Lead data transfers to corresponding contact fields only when those fields are empty. Define conversion as one shared sentence applied after the assessment decision.

Check for the same person before conversion. Similar-record detection looks first at unique fields, then at the lead's email, company name, and name field. Choose in advance which data will support that check. The profile performing the action also needs the Convert Leads permission. This makes the transition depend on defined data and authority instead of an individual coordinator's habit.

The request channel sets assignment scope

Assignment rules operate on records created through imports, web forms, and APIs. They do not trigger for a record manually created from a chat request. A rule can check whether a user is signed in and currently within shift hours. Online status can lag by up to five minutes. If nobody qualifies, the record does not remain unowned; it goes to the default user.

Assignment Threshold sets a maximum record count per person for a day, week, or month, with an optional maximum for pending records. When a threshold is exceeded, the record falls to the default assignee. The threshold applies in assignment rules, web-form records, and modules synchronized through integrations. Manual creation and import display only a warning. The Assignment Rules & Threshold profile permission is required.

Keep operation day on the record

The Zoho Appointments module is added when Services is enabled and is available in Professional, Enterprise, and Ultimate. Its start time must fall within company business hours. Duration comes from service availability and cannot be changed on the appointment. Only one member can be assigned. Allowing appointments outside service availability and outside business hours uses two separate options; the second appears only after the first is enabled.

One week before the operation, a patient changes the flight time. The coordinator updates the calendar, but the record retains its old date, so hotel and transfer lists use outdated information. Defining one date source prevents this split. An automatically created deal from a completed appointment starts as won; its amount maps to service price, closing date to appointment start, and unchangeable deal name to appointment name.

Subforms impose planning and reporting tradeoffs

Enterprise allows 2 subforms per module and Ultimate allows 5; lower editions do not provide them. A layout can contain no more than 25 subform fields, while all subforms together can hold up to 200 rows. Subform fields cannot serve as custom-view columns, web-form fields, import fields, global-search targets, validation-rule inputs, or workflow criteria. Add an aggregate field first and use that field for applicable rules.

The complete design requires Enterprise because both the session and graft subform and product-line customization start there. Ultimate supports the same structures with more subforms. Professional includes Quotes, Services, Appointments, and field-level permissions, but has no subforms. Standard limits image and file upload fields to 2 per module and has neither Quotes nor Appointments. Free does not provide file upload in web forms.

Check visibility and searchability before completion

Access follows record ownership. To give access to a physician outside the owner's hierarchy, use a user field identifying that person and select an access level. Each module supports up to 5 single-user fields and 1 multi-user field, which can contain 10 people. Hiding a field or making it read-only by profile is available in Professional and above, and the permission applies across every layout in the module.

Zoho global search covers a fixed, nonconfigurable set of field types and requires at least three characters. Single-select picklists, dates, date-times, checkboxes, and user fields are outside that set. Store information that must be found in a supported field, then test access with the actual user profiles. Deleted records and attachments remain in the recycle bin for 60 days, so include deletion behavior in the final access and retention review.

Zoho CRM