When an operation ends and the patient returns home, a new phase of follow-up begins for the clinic. Distance makes consistent communication and a shared view of incoming material more important. A Zoho setup therefore needs two clear decisions: which mechanism carries the follow-up calendar, and where the patient’s photographs, questions, and complaints accumulate. Without that distinction, an open case can appear closed on the clinic’s screen.
A fixed schedule of checks differs from communication that changes when the patient replies. The first can use recurring tasks; the second can use a sequence that ends after a response. Notes, record attachments, and upload fields form the file itself. Their capacity, permissions, and edition thresholds are not identical. A durable design treats the calendar and the file as connected decisions, not one ambiguous process.
The file remains open after departure
Three weeks later, the patient sends a photograph. It stays on the adviser’s phone, unseen by everyone else at the clinic. In the fifth week, the same question arrives by email, and the person answering has never seen the first image. Communication has not stopped completely. Instead, the two contacts fail to appear as parts of one continuing file, leaving the team to respond with an incomplete history.
On another occasion, the review date arrives, but nobody calls because there is no shared place responsible for remembering it. The conversation may go well when the patient eventually calls the clinic. A pleasant conversation, however, does not prove that the follow-up system works. Keeping the file open depends on making the expected check, received response, and shared material visible together, rather than relying on contact that happens by chance.
Recurring task or sequence ownership
A recurring task can run daily, weekly, monthly, yearly, or at a custom interval, but it needs a due date before recurrence can be defined. Weekends and holidays may be excluded from daily recurrence, while a monthly due date may move to a working day. Reminders can be set days, weeks, or months before the deadline and delivered by email, pop-up, or both. Only Completed in the Status field closes the task.
Zoho Cadences combines email, task, call, and WhatsApp follow-ups in a multi-step sequence and can remove a record when a reply arrives. Records may be selected manually or drawn from a custom view. The initial setup permits five follow-ups, with further entries added afterward. A recurring task therefore fits a fixed review rhythm, while a sequence fits communication that changes after a response. They are not interchangeable names for one calendar.
Define the sequence exit first
A record can leave a sequence in four configured ways: falling outside custom-view criteria, satisfying follow-up criteria, reaching a date, or meeting record criteria. When a record no longer qualifies for the feeding view, its scheduled follow-ups are cancelled. One operation can add no more than 10,000 records to a sequence. Exit logic matters early because an existing follow-up cannot later be removed, except when it is the final follow-up in the sequence.
The feeding custom view has four restrictions. It cannot contain the Campaign Name field. Multi-select picklists cannot use Include All, Include Any, Exclude All, or Exclude Any comparators. Related-module criteria are unavailable, and user fields cannot use the belongs to comparator. These limits directly shape audience definition. Establishing valid view criteria before the exit conditions separates records that should continue through follow-up from those whose scheduled steps should end.
Keeping photographs and complaints together
The number of file and image upload fields per module in Zoho depends on the edition: two in Standard, five in Professional, ten in Enterprise, and fifteen in Ultimate. Each file is limited to 20 MB, and an image field accepts no more than ten images in one upload. A file upload field inside a subform allows five files per field. These boundaries determine which named fields can hold follow-up photographs.
A record has no overall ceiling on its attachment count, but one upload accepts at most ten files totalling 100 MB. A note can carry up to five files totalling 20 MB. Note text is limited to 65,535 characters, and every note counts as a separate record. Profile permissions separately control viewing, creating, editing, or deleting notes and viewing, creating, or deleting attachments. Only an administrator can change those permissions.
A list does not alert the team
A custom view fills itself with records that match its criteria, but Zoho does not send a notification, create a task, assign an owner, or produce a reminder because of that list. The view only exposes files matching the current condition. An action requires either a workflow based on a date field or scheduled report delivery. The view is therefore a current slice of relevant records, not the mechanism that starts follow-up activity.
The list view offers nine bulk actions, and every one waits for a user click. A list opened each morning should not be treated as an automatic alert. The team needs to distinguish the list that provides visibility from the separate mechanism that produces action. Without that distinction, files may be grouped under the correct criteria while the required contact is still delayed. A current view does not mean that follow-up is running by itself.
Pair field counts with editions
When named upload fields are designed for photographs, their capacity should appear in the same specification: Standard permits two file or image fields, Professional five, Enterprise ten, and Ultimate fifteen. The 20 MB limit remains for each file. If the allocated field count is insufficient, record or note attachments can provide the fallback, avoiding a design based on unavailable field capacity. The limits for a single upload and attachments on one note still apply.
Zoho Cadences is available from Standard upward and is absent from Free. Creation limits are 20 in Standard, 40 in Professional, 60 in Enterprise, and 70 in Ultimate; active limits are respectively 10, 20, 30, and 50. No definite edition threshold is stated for recurring tasks and reminders, so their availability should be described as edition-dependent and verified before a proposal. Calendar and field design can then share one explicit edition assumption.
Duration tracking begins with the field
A report does not automatically calculate how long a record remains in a particular stage. To obtain that duration, history tracking must be enabled for the relevant picklist, with the duration column kept in the tracking-related list. Only one picklist per module can use this tracking. The feature is unavailable in the Tasks, Calls, and Meetings modules. Duration reporting must therefore begin by choosing the tracked field, before designing the report around it.
If the edition is downgraded while history tracking is enabled, that tracking data is deleted. The Stage component is also limited to Enterprise and Ultimate. These thresholds mean the duration view cannot be planned separately from the edition. The design should identify the picklist, its related duration column, and edition suitability in that order. This avoids attributing a stage duration to the report when the system has not generated it and keeps downgrade consequences visible.
What the clinic should see
The post-return screen should bring together notes and attachments in the shared file, images held in permitted named upload fields, the custom view showing matching records, and the chosen follow-up mechanism. Fixed checks can remain in recurring tasks, while response-driven contacts can run through Cadences. The custom view gathers visibility but produces no action. This structure shows which material is accessible and which follow-up remains open, rather than claiming a result it cannot measure.
Eksenium’s Clinical CRM Pattern Library includes the hasta-kabul pattern as a reference for gathering a patient file on one screen. The final Zoho screen should likewise expose its choices for notes, attachments, views, calendars, and edition limits, preventing the return journey from closing the file invisibly.
