Overview

This page covers third-party integrations that do not have a dedicated settings page in the Kraya dashboard. These integrations are typically configured with help from the Kraya team and run automatically in the background once connected.

Each of the following lead-import integrations has its own dedicated guide:

• TagMango (course / community / event payments) — see TagMango integration
• Housing.com (real estate property leads) — see Housing.com integration
• Cratio (CRM webhook lead sync) — see Cratio integration
• TradeIndia (B2B buyer inquiries, polling-based, self-serve) — see TradeIndia integration
• Razorpay Leads (lead-per-payment via order.paid webhook, self-serve, HMAC-signed) — see Razorpay Leads integration

The remainder of this page covers MyOperator (cloud telephony / IVR), which currently has no dedicated guide.

---

MyOperator Integration

What it does

MyOperator is a cloud telephony and IVR (Interactive Voice Response) platform commonly used by businesses in India. When connected to Kraya, incoming call data from MyOperator is automatically synced into Kraya as leads. Each call is also recorded as a call history entry on the lead.

This is a one-way integration — call data flows from MyOperator into Kraya. Kraya does not push any data back to MyOperator.

What you can do

• Automatically capture incoming calls from MyOperator as new leads in Kraya
• View call details (duration, status, department, recording link, receiving agent) in the lead's call history
• Route new leads to specific pipelines based on which MyOperator agent answered the call
• See MyOperator-created leads in the Kraya Dashboard, Chrome Extension, and all existing views — they appear just like any other lead

How it works

Once connected, Kraya checks your MyOperator account for new call logs on a fixed schedule (about every five minutes). For each call:

1. New caller — If the caller's phone number does not match any existing lead in your organization, Kraya creates a new lead. The lead is placed in the "New Lead" stage of the appropriate pipeline (see pipeline routing below).

2. Returning caller — If the phone number already exists as a lead, Kraya moves that lead back to the "New Lead" stage within the same pipeline the lead is already in to bring it to your attention again. The pipeline is not switched based on who answered this new call.

3. Call logging — A call history entry is created on the lead regardless of whether the lead is new or existing. The entry includes:

   • Call status (Connected or Missed; calls with no answered agent are treated like missed)
   • Call duration (stored in whole minutes, rounded up from the length MyOperator reports)
   • Department name (if available)
   • Recording link (if available)
   • Name of the agent who answered (if connected)

4. Deduplication — Each call from MyOperator has a unique identifier. If the same call has already been processed, Kraya skips it. This prevents duplicate leads or call entries even if the sync windows overlap.

Pipeline routing

Kraya routes new leads to pipelines based on the MyOperator agent who answered the call:

• Connected calls — Kraya looks at the agent who received the call and searches for a pipeline in your organization whose name matches that agent’s name (case-insensitive). If a matching pipeline is found, the new lead is placed there.
• No matching pipeline — If the agent's name does not match any pipeline, the lead goes to your default Leads pipeline. If your organization does not have a pipeline literally named Leads, Kraya falls back to another pipeline in your account so the lead can still be created; ask Kraya support if you are unsure which pipeline is used.
• Missed or unanswered calls — If no agent answered (including voicemails that never show as “received” in the call data), the new lead goes to your default Leads pipeline (or the same fallback as above).

For this routing to work, name your pipelines to match your MyOperator agent names. For example, if your MyOperator agent is named "Rashmi," create a pipeline called "Rashmi" in Kraya.

Setup

MyOperator does not have its own screen under Kraya’s dashboard menus today. Connecting or changing settings is done with the Kraya team (or your organization’s technical administrator, if your rollout uses direct setup).

1. Provide your MyOperator API token securely to Kraya.
2. Kraya enables the integration for your organization and, on first connection, pulls your MyOperator user list and available log filters for reference.
3. Optionally agree on:
   • Default country code — Used when normalizing caller numbers (defaults to 91 for India)
   • Call filters — Which MyOperator log types to include (see Settings and configuration)
4. Once activated, new calls typically appear in Kraya within a few minutes of each scheduled sync.

To disconnect, contact the Kraya team (or your administrator). Your existing leads and call history stay in Kraya; only automatic syncing stops.

Where leads appear

MyOperator leads appear everywhere in Kraya just like manually created leads:

• Dashboard — Listed in the relevant pipeline and stage. Source is marked as "myoperator"
• Chrome Extension — Call history entries appear in the Calls tab of the lead sidebar
• Search and filters — Searchable by phone number and filterable by source

Settings and configuration

These settings are configured by the Kraya team during setup or change requests.

Limits and quotas

• Only one MyOperator account can be connected per organization
• Sync runs about every five minutes; allow a short delay after a call before it appears in Kraya

Common edge cases

• Caller with no phone number The call is skipped. A phone number is required to create or match a lead.

• Duplicate phone number in your organization Kraya treats it as a returning caller — the existing lead is moved to the "New Lead" stage and a new call entry is logged.

• Agent name does not match any pipeline The lead falls back to the default "Leads" pipeline. Consider renaming your pipelines to match your MyOperator agent names for accurate routing.

• Very short or system-level missed calls These may have no agent information. The lead is routed to the default "Leads" pipeline (or the fallback pipeline described under Pipeline routing).

• Voicemail or special outcomes If MyOperator does not record anyone as having received the call, Kraya treats the outcome like a missed call for status and routing.

• Lead name is blank MyOperator call logs do not include the caller's name. Leads created from MyOperator will have no name initially — you can update the name manually in Kraya afterward.

• Call duration display Duration is saved in minutes, rounded up. This may differ slightly from the exact second-by-second duration shown inside MyOperator.

Troubleshooting

New calls are not appearing in Kraya

• Cause: The integration may be inactive, or the MyOperator API token may have expired
• Fix: Contact the Kraya team to verify the connection status and re-enter the API token if needed

Leads are going to the wrong pipeline

• Cause: The agent who answered the call does not have a matching pipeline name in Kraya
• Fix: Ensure your pipeline names match your MyOperator agent names exactly (matching is case-insensitive). Missed calls always go to the default "Leads" pipeline

Duplicate call entries on a lead

• Cause: This should not happen — each call is deduplicated by its unique MyOperator call identifier
• Fix: If you see duplicate entries, contact Kraya support

Call recording link is missing

• Cause: Not all calls have recordings in MyOperator (e.g., very short calls or missed calls)
• Fix: This is expected behavior. Check MyOperator directly if a recording should exist

Decision tree

• Calls not syncing at all → Contact Kraya team to verify integration is active → Re-enter API token if needed
• Calls syncing but leads in wrong pipeline → Check pipeline names match MyOperator agent names
• Call details incomplete (no recording, no department) → Check the call details in MyOperator; Kraya syncs whatever MyOperator provides
• If none of the above → Contact Kraya support

FAQs

• Does Kraya send any data back to MyOperator? No. This is a one-way integration. Call data flows from MyOperator into Kraya only.

• Can I pause the integration temporarily? Yes. Contact the Kraya team to deactivate the integration. Your existing leads and call history remain in Kraya.

• Will reconnecting create duplicate leads? No. Kraya deduplicates by phone number for leads and by call identifier for call entries. Re-syncing the same calls will not create duplicates.

• What happens if I rename a pipeline? Future calls will be matched against the new pipeline name. Existing leads remain in their current pipeline.

• Can I change which types of calls are synced? Yes. Contact the Kraya team to update the call filters (e.g., sync both incoming and outgoing calls).

• Are outgoing calls synced? By default, only incoming calls (as defined by your filter settings) are synced. Contact the Kraya team if you need outgoing or other log types included.

• Why is call duration in Kraya different from MyOperator? Kraya stores duration in whole minutes, rounded up, while MyOperator may show hours, minutes, and seconds.

Tips and best practices

• Name your Kraya pipelines to match your MyOperator agent names for automatic pipeline routing
• Set the correct default country code during setup to ensure phone numbers are normalized consistently
• Check the lead's call history in the Chrome Extension or Dashboard to see full call details including recording links
• Since MyOperator leads have no name initially, set up a workflow to update lead names as you engage with them

Related features

• Dashboard — Where MyOperator leads appear in pipelines and stages
• Chrome Extension — Call history entries are visible in the lead sidebar Calls tab
• TagMango integration — Payment webhook leads (no dashboard settings page)
• IndiaMART Integration — Another one-way lead integration (webhook-based)
• JustDial Integration — Another one-way lead integration (webhook-based)

Screenshots