Between nine and eleven in the morning, four front desk lines ring together. The employee answers three and misses one. Later, the manager asks who called. The switchboard log shows a number, but CRM shows no trace. A manual search returns nothing because the caller is not yet a record. Even a simple callback has become uncertain.
Zoho CRM is not a switchboard. It is the record layer in front of the phone system. Capturing call duration and outcome consistently requires three parts: a provider connected through Telephony, a decision about the fields used in the Calls module, and workflow rules built on that module. Without this combined design, purpose, duration, and outcome do not form a dependable call record.
What remains after the conversation
A patient calls four times within three weeks. A different employee answers each conversation, so the patient explains the same question again. On the fourth call, the patient hangs up. A record and an appointment exist, yet none of the four conversations appears under that record. The calls remain elsewhere without regular review, leaving the team unable to recover their context.
This gap creates more than a memory problem. The manager cannot see which conversation needs follow-up, while the employee cannot determine how an earlier discussion ended. Several people may return the same call, or nobody may respond. When purpose, duration, and outcome do not share a record structure, phone traffic stops being measurable work and shift changes make information dependent on personal notes and verbal handovers.
CRM is the screen in front of the switchboard
The phone line, audio, and routing remain in the switchboard. In Zoho CRM, the team decides which relationship and outcome fields will hold information about a call. Telephony connects the systems. Users with an administrator profile can access setup. The provider must be installed by opening View Marketplace through Setup, Channels, and Telephony. Starting directly from the provider returns an error saying Telephony has not been enabled by the administrator.
This distinction clarifies the purchasing decision. CRM does not replace the infrastructure that carries the number or routes audio. It supplies the working layer where call information becomes a record. Marketplace is therefore not an optional catalogue stop; it is the required installation route. Connecting an existing cloud PBX or contact centre provider is one path, while configuring the built-in phone system is a separate choice.
Separate the two setup paths early
The first path connects your cloud PBX or contact centre provider through Telephony Marketplace. The second uses Zoho built-in telephony, which runs on Twilio infrastructure. For the built-in option, you first purchase a number. You then add phone users and configure outbound calling. The final step sets up inbound routing. This sequence keeps a provider integration project distinct from establishing a new phone system.
Built-in telephony uses credits. One credit equals one US dollar and is converted into local currency. Purchasing a number, making calls, and increasing recording storage consume credits. Number purchase and maintenance carry monthly charges. The remaining balance appears on the Built-In Telephony page, where automatic top-ups can be configured. An organisation may connect several providers, but changing a user's provider is manual: an administrator removes the user from one and adds them to another.
Choose the fields that form the call record
Call records reside in the Calls module. The standard Log a Call fields include Subject, Call Type with Inbound or Outbound values, From Number, To Number, Related To, Call From and To, Call Purpose, Call Result, Time Details, Call Start Time, Call Duration, and Description. Call Start Time and Call Duration cannot lose their required status. Custom fields cannot be added to this screen; existing fields are adjusted through page layout customisation.
When phone integration is enabled, From Number and To Number are added automatically to the Calls layout after a call record is created from the phone, and they become active in Calls Preferences. Once marked as required, these fields cannot be disabled. To Number must remain enabled for booking an appointment through the calendar. The team should therefore decide beforehand how it will use purpose, outcome, start, and duration information.
Connect automation to call events
A Calls workflow may react when an inbound or outbound call is completed, ringing, answered, modified, or logged. Scheduled-call events include creation, modification, delay, postponement, reassignment, and deletion. A deleted call or every call may also serve as the trigger. Ringing and answered appear only when a phone provider is integrated. Conditions can use duration, purpose, outcome, and whether the caller is a lead, contact, account, or unknown.
Immediate actions include email notification, task creation, field update, webhook, and custom function. They perform defined work after a recorded event rather than preventing a call. Turning an unknown caller into a new record is not a separate feature either. Record creation does not appear in the documented instant-action list for Calls workflows, so the step runs through a custom function, available in Enterprise and above, or through a manual step. The record type should be selected without making undocumented assumptions about how phone numbers are matched to existing records.
Structural limits of the Calls module
The Calls module imposes firm boundaries on record design. It cannot receive a lookup relationship field, user field, unique field, or summary field. Picklist history tracking is unavailable as well. Consequently, adding a new user field to connect every call directly to a particular physician is not an available approach. The design has to remain within the existing standard fields and permitted page layout changes.
If these boundaries are missed during setup, the team may define reporting and follow-up expectations around a data model that cannot be implemented. The assumption that a new custom field can be placed on Log a Call must also be removed. If Related To, Call Purpose, Call Result, Description, and the other existing fields cannot hold the needed information meaningfully, the scope should be reconsidered instead of masking a structural limit with an automation promise.
Decide what you want to measure
Measurement is not merely a reporting task to consider after connecting the phones. Values for Call Purpose and Call Result, the interpretation of duration, and the expected content of Description should be decided at entry. Scoring rules can use every call made, answered and unanswered calls, inbound calls, call duration, and missed calls as signals. The Calls module is required, while phone integration is optional for using these signals.
Call insights such as sentiment, intent, and keywords have a different scope. They require Voice of Customer and Zia transcription in addition to the Calls module. No further conclusion about language support should be drawn. This distinction prevents basic call signals from being confused with advanced conversation insights. Consistent use of purpose, outcome, and duration should come first; deeper analysis is considered only when its own conditions are met.
Minimum setup checklist
The minimum structure combines four decisions. A user with an administrator profile connects the provider through Zoho Telephony Marketplace, or completes the three-stage built-in setup. The team selects the standard fields used in the Calls layout and the number fields that remain enabled. At least one workflow rule is attached to call events. If an unknown caller should create a record, plan that step separately: record creation is absent from the Calls workflow action list, so it requires a custom function or a manual step.
Edition details should be checked individually before quoting. The Telephony and built-in phone thresholds are unknown, so availability may vary by edition; the administrator-profile requirement is established. Calls is a standard module, and the documentation defines no edition restriction for it. Free has workflows with limited actions. The workflow record-creation action starts with Professional but is not listed for Calls workflows, while custom functions start with Enterprise. Workflow criteria are limited to five in Standard and Professional, and ten in Enterprise and Ultimate. Voice of Customer dashboards require at least fifteen user licences in Enterprise, Ultimate, CRM Plus, and Zoho One organisations. Built-in phone cost depends on credit usage, not edition. The connection decision is complete only when the fields and rules used to track calls are defined.
