Unifying multichannel demand in one patient record

When web forms, WhatsApp, email, and phone operate together, one person can enter through different routes and leave the team handling one enquiry through fragmented records. Zoho CRM has no ready-made rule that compares channels before creation and redirects a matching enquiry to an existing record. Single-record discipline therefore depends on unique fields, channel ownership, and planned merging decisions working together. Before automation, this is a data-management problem.

The approach separates two jobs: rejecting a second record through a reliable match and merging duplicates that already exist under controlled conditions. Consistent phone formatting, assigned ownership, and master-record selection support this discipline. The patient-intake pattern in the Clinical CRM Pattern Library brings the patient record onto one screen. The goal is visible responsibility and lifecycle decisions, not flawless automation.

What happens when one person uses three channels

The same person first completed the web form, sent a WhatsApp message the next day, and called over the weekend; three separate advisers worked on three records, each calculating a separate price for the same treatment. This separation fragments notes, activities, and ownership. Before continuing the conversation, the team must investigate which record carries the current context.

At month end, the channel report counted the same patient under both social media and web form sources; each source field was populated on a separate record, leaving the team debating which channel produced the enquiry. New-record prevention and existing-record merging must therefore remain separate jobs. One controls entry; the other is an irreversible data-management decision.

There is no ready-made pre-creation matching rule

The documented Zoho workflow actions do not include stopping a save or cancelling creation. A process that searches other records before creation, avoids opening a new record after a match, and adds the conversation and task to the existing record requires middleware. Actions by Zoho Flow cannot block the record, and one condition accepts one Flow action. Without middleware, created duplicates are merged later.

A unique field rejects the second record rather than warning and permitting continuation. Text, Email, Phone, Integer, BigInt, and URL fields can be unique, with case-insensitive comparison. The limit is two per module, or three in Leads, Contacts, Products, and custom modules. Checks cover manual creation, related lists, lookup dropdowns, web forms, imports, mobile applications, and API calls; a web-form duplicate goes for approval.

How to populate a normalized phone field

A country code, leading zero, space, parenthesis, hyphen, or dot can make one phone number appear as different values. A separate normalized phone field reduces these variations. However, a workflow field update cannot process strings; it writes only a predefined constant or empty value. It cannot remove characters, drop a leading zero, add a country code, or convert text to lowercase.

On Professional and above, a read-only formula field recalculates when participating fields change. When newly added, it may remain empty on existing records until one of those fields changes. On Enterprise and above, the alternative is a workflow-linked custom function. Below these options, phone formatting remains a written team rule, with deviations handled through regular data checks.

Set ownership and contact fields separately by channel

Do not assume that source, last-contact channel, and similar fields can be populated identically across channels. A field update changes the record's own fields and only documented parent-record combinations. It cannot write to another record through a relationship absent from the fixed table. For example, a rule in Calls cannot update a related lead field through a standard field update; that write requires a workflow-linked custom function.

Manage ownership and relevant fields within the web-form and email record flows. For calls and messaging, define a custom function or an explicit manual marking step. Whether a standard field update can write the dynamic execution time into a Date/Time field is unknown, so do not base the last-contact-time design on it. Separate rules, owners, and control points expose the source of missing channel marks.

What is provided for WhatsApp

The WhatsApp integration adds a module named Messages to the CRM. Incoming messages arrive in this module; once associated with a record, the messages appear in that record's related list in chronological order. The documentation does not define which field drives the association or when it happens automatically. Users at the record owner's role or above can view the conversation when they also have record-view permission. Ownership therefore affects message access.

A business cannot initiate a conversation outside a pre-approved template. Charging is conversation-based; during its 24-hour window, the customer can send unlimited messages. Zoho Business Messaging credits are purchased through the option shown after number activation, and automatic recharge can be configured. Existing numbers cannot be migrated, and a number used in another product cannot be connected. These limits put number and credit planning before setup.

Connect web forms and email to assignment rules

Web form setup binds ownership to one of two options: a single chosen user or an existing assignment rule. When the rule finds no eligible user, the record goes to the default assignee, which for a web form is the user who created the rule, or the super administrator if that user is deleted or inactive. Define the initial owner explicitly for each form. In the same channel design, decide where source and normalized matching fields are populated, but do not attribute an undocumented matching behavior to the form submission.

The email parser creates a record from an incoming email, assigns its owner by user, role, or assignment rule, and updates up to five fields at once. It processes messages from a permitted list of no more than five sender addresses, only an administrator profile can configure it, and it cannot be created for Deals. Its edition threshold is verified in the target account before a proposal. Before connecting a shared mailbox, agree on senders, ownership, and fields together.

Find duplicates with tools, not a list

Custom-view criteria assess each record by its own values; they cannot ask whether another record repeats a value. Therefore, a custom view cannot compare normalized phone fields and display duplicates. De-duplicate in the module list view accepts up to three fields, merges only when those values match exactly, and selects the master record according to the most recent Last Activity Time.

Find and Merge on the record detail page provides six criterion fields per module and lets the user select the master. Both tools are available only in Leads, Accounts, Contacts, Deals, Vendors, and custom modules, and in both, up to three records merge in one operation. The relevant profile permission is required. Assigning a weekly review to one owner keeps criteria consistent and places ambiguous matches under review before an irreversible action.

Choose the master record before merging

A merge cannot be undone; the secondary record is permanently deleted. Notes, attachments, and activities move to the master, and moved activities take the master record's owner. Creation time and creator information come from the oldest record. Do not choose the master merely by selecting the fullest row. Compare ownership, activity history, verified contact details, and surviving field values before proceeding.

During Find and Merge, delete-triggered workflows run when the secondary record is deleted, while edit-triggered workflows run when the master is updated. A deletion rule sending a closure notice may therefore run. These triggers do not run during an automatic De-duplicate merge, and no report lists merged records. If the correct master is unclear, postponing the operation avoids ownership and field losses that cannot later be corrected.

Where middleware fits

A design that searches and matches before creation is development work, not a simple setting. An incoming Zoho Flow webhook returns no CORS header, so a browser cannot call it directly. The request must pass through a server relay that returns this header and continue server to server; an unpublished Flow returns 410. Field API names vary between organizations, and unknown fields are silently ignored, so check the API name first when a target remains empty.

Professional adds formula fields and workflow record creation; Enterprise adds custom functions. Unique fields are edition-independent and require profile permission. Thresholds for the email parser, merging tools, WhatsApp Business Messaging, and web forms vary by edition and are verified in the target account before a proposal. Below supported options, the fallback is written phone-format discipline and manual channel marking.

Zoho CRM for clinics