How to set renewal reminders for Botox and filler sessions

A client calls after remembering the clinic six months later, but has already visited another clinic. The record contains the last procedure date, yet nowhere states when the next contact should happen. This gap shows that renewal tracking depends on staff memory. The missed call is not the underlying problem. The record lacks a shared, visible, and traceable date that could initiate contact.

A sound renewal process connects the procedure type and your organization’s chosen interval to the record. It then calculates the next date, separates approaching records, and applies the chosen follow-up channel. Zoho does not recommend a medical interval here. That decision belongs to your organization. Views, calculations, and automation are also distinct. Understanding each boundary prevents a tracking process from failing silently.

A renewal interval is data, not habit

When the renewal date exists only in an experienced employee’s memory, the team cannot act from a shared decision. Recording the last procedure date is not enough. The procedure type, the interval adopted by the organization, and the next contact date must remain separately understandable. A new employee can then read why a record deserves attention without relying on an undocumented routine.

The team keeps recurring procedures in a spreadsheet. Its date is updated manually. After one week without an update, the list quietly becomes inaccurate, and nobody notices when it changed. The risk is not the spreadsheet itself. The calculation depends on whoever updates it. Without a visible connection between the record and follow-up date, a current-looking list does not prove accuracy.

Procedure types and intervals in the record

Consistent procedure names connect each interval decision to the correct category. When a value is added, renamed, or deleted in a local picklist, that change reaches records using it. Naming and removal decisions therefore affect more than screen organization. They change how existing records are read, making it important to inspect the affected scope before altering the list.

If the list uses a global set in Zoho, a deleted value disappears from related lists but remains in existing records. The option to replace values also disappears. Multi-select picklists cannot use global sets. The choice between a local list and a global set should therefore consider not only reuse, but also historical records and the way future value cleanup will be handled.

Limits of the next-date calculation

A formula field can use nested conditions to select different day counts by procedure type and add the result to a starting date. The result is read-only. It recalculates when participating fields change, but cannot freeze a value at its current state. Treat the formula as a dynamic application of your organization’s interval decision, not as a permanent archive of past renewal dates.

A newly created formula field produces values for records created after the field is added. It may remain blank on older records until a participating field changes manually or automatically. A Zoho workflow field update writes only a predefined fixed or blank value; it performs no calculation. Another calculated write requires a custom function, which is available in Enterprise and higher editions.

Finding clients whose time has arrived

A custom view fills itself with records matching its criteria. Due in Days and Age in Days comparators are available for date and date-time fields. However, it is not confirmed that a formula-type field producing the renewal date works with this view criterion. Test this critical connection in the live organization before assuming that calculated renewal dates will reliably surface the right records.

A view only separates records. It does not send notifications, create tasks, assign owners, or produce reminders. The nine bulk actions in list views are different because each waits for a user click. Instead of describing a Zoho view as automation, define it as a work queue refreshed by verified criteria. Assign responsibility separately for calls or any other action taken from that queue.

The component that carries automatic reminders

A workflow rule uses one trigger type, and that choice cannot be changed later. Documented types cover record actions, date field values, record scores, Zia recommendations, notes, and competitor mentions. Rules based on date or date-time fields carry only instant actions, not scheduled actions. Whether a custom renewal field can serve as the date trigger still requires verification in the live organization.

A record-action rule can carry up to five scheduled actions that run after a defined period. Zoho's documentation gives a limit of five emails, tasks, functions, and webhooks for each scheduled action, but conflicts between three and five for field updates. Therefore, verify the exact field-update limit in the live organization. Instant-action limits differ. Record creation is available from Professional upward, once per rule. Criteria allow five conditions in Standard and Professional, and ten in Enterprise and Ultimate. Zoho's documentation states no edition threshold for recurring tasks and reminders, so treat that point as edition-dependent and verify it in the target account before a proposal.

A sequence that stops after a response

Cadences is a multistep follow-up sequence using email, task, call, and WhatsApp steps. A targeted response removes the record from the sequence. Removal can use custom-view criteria, step criteria, a date, or record criteria, and is evaluated before a step triggers. Audiences can be selected manually or through a custom view, although related-module criteria and some comparators are unavailable there.

Zoho Cadences is available in Standard and higher editions. Created and active step limits are respectively 20 and 10 in Standard, 40 and 20 in Professional, 60 and 30 in Enterprise, and 70 and 50 in Ultimate. Re-enrollment defaults to three times per sequence. Because the covered modules are not documented as a closed list, verify your selected module separately.

Channel rules for message reminders

A business cannot start an unrestricted WhatsApp conversation. It can send only a template approved by Meta, and only to a Lead or Contact record. The template may be added as an action in a workflow, Blueprint, or Journey Builder, or sent manually from a record. An incoming message can be answered within 24 hours. After that window closes, approved templates govern renewed contact.

The integration is available in the trial and every paid edition, while Meta charges for messages. These product boundaries do not determine whether communication is legally permitted. Your organization must complete its own assessment of permissions and applicable rules. Do not present a Zoho setting as proof of compliance. Document which record, stage, and responsible person govern the approved template’s use.

Where the setup stops working by edition

Formula fields are available in Professional and higher editions, not Standard. Cadences begins with Standard and is absent from Free. The record-creation action is available from Professional, once per rule, while custom functions require Enterprise or higher. Workflow-rule criteria are limited to five conditions in Standard and Professional and ten in Enterprise and Ultimate. These thresholds mean one Zoho automation design cannot be transferred unchanged across every edition. Do not assume automated calculation and follow-up on lower tiers.

In Standard, the next date can be calculated outside the system from the organization’s decision and entered manually. In Free, a documented routine can use tasks and reminders instead of Cadences, once their edition availability is verified in the target account. Remember that views create no action, and name the responsible person. Finally, verify in the live organization that the chosen date field, view criterion, and automation trigger actually work together.

Zoho CRM