Skip to main content

How to Map Call Duration Fields in the RingCX (RingCentral) Integration (CRM)

Overview The RingCX (RingCentral) integration supports mapping duration-related fields — Ring Time, Agent Duration, and Queue Duration to the Duration field in CRM Call Logs. This lets call time data from RingCentral write directly into your CRM records.

Before You Begin

You will need:

  • Administrator access to Dazos CRM Settings.

  • The RingCX (RingCentral) integration already configured and active.

  • A decision on which duration metric you want stored in the CRM — Ring Time, Agent Duration, or Queue Duration.

Steps

  1. In Dazos CRM, navigate to Settings → CRM Settings → Integrations → VOIP Settings.

  2. Open the RingCX Contact Center configuration. [Screenshot: VOIP Settings page with RingCX Contact Center configuration highlighted] Caption: Navigating to the RingCX Contact Center configuration from VOIP Settings.

  3. Scroll to the CallLog Field Mapping panel.

  4. In the CRM Field dropdown, select Duration.

  5. In the RingCX Field dropdown, choose the duration value you want to store:

    • Ring Time (sec) — the time the call spent ringing

    • Agent Duration (sec) — the time the agent was active on the call

    • Queue Duration (sec) — the time the caller waited in the queue

  6. Click Add, then click Save. [Screenshot: CallLog Field Mapping panel with CRM Field set to Duration and RingCX Field set to a duration option] Caption: A completed duration mapping in the CallLog Field Mapping panel, ready to save.

💡 Tip: Only map one duration field to the CRM Duration field at a time. If you need to track multiple duration types, map them to separate custom CRM fields instead.

Full List of Default Mappable RingCX Fields

The fields below are available out of the box in the RingCX integration and can be mapped to CRM fields on Leads, Contacts, and Call Logs.

Contact & Lead Fields

  • ANI (Caller Number)

  • DNIS (Dialed Number)

  • First Name

  • Last Name

  • Full Name (first_name last_name)

  • Email

  • Lead Phone

  • Address

  • Aux Phone

  • Extern ID

Call & Interaction Fields

  • UII (Call / Interaction ID)

  • Pass UII

  • Call Start Time

  • Call Result

  • Dial Type

  • Ring Time (sec)

  • Queue Duration (sec)

  • Agent Duration (sec)

  • Recording URL

  • Cloud Connected Name

  • Gate / Queue ID (Voice)

  • Gate / Queue Name (Voice)

  • Campaign ID

  • Campaign Name

Agent Fields

  • Agent ID

  • Agent First Name

  • Agent Last Name

  • Agent Full Name

  • Agent Username

  • Agent Phone

  • Agent External ID

  • Agent Disposition (Voice)

  • Agent Notes

  • Agent Recording URL

SMS & Chat Fields

  • Chat Queue ID (SMS)

  • Chat Queue Name (SMS)

  • Chat Transcript (SMS Body)

  • Channel Type (SMS)

  • Disposition (SMS)

  • Enqueue Time (SMS)

  • Dequeue Time (SMS)

  • Source IP (SMS / Chat)

  • Browser Info (Chat)

  • HTTP Referer (Chat)

  • JSON Baggage (extra context)

⚠️ Note: This list reflects the updated RingCX integration. If you upgraded recently, some of these fields may not have been available in earlier versions.

Verification / Expected Result

After saving your mapping, the selected duration value from RingCentral is written to the Duration field in CRM Call Logs whenever a call event is received. Confirm this by opening a recent call record in the Call Logs module and checking that the Duration field is populated.

Troubleshooting / Common Errors

Symptom: The field I need isn't in the default list above. It may still exist in the RingCentral payload but not be exposed in the default mapping list yet. To resolve:

  1. Check the field name against the RingCentral documentation.

  2. Submit a support ticket to Dazos requesting the field be investigated and added to the mapping configuration.

Related Resources

  • Understanding the RingCentral VOIP Integration with Dazos CRM

  • What are the different VOIP system integration capabilities? (CRM)

  • How to stop CTM/CallRail Caller ID from populating or overwriting City, State, and Zip fields (CRM)

Did this answer your question?