Kraya-AI Docs
Integrations

teleCRM

Two-way lead sync between Kraya and teleCRM — near-real-time push from Kraya, 5-minute reverse poll from teleCRM, stage/status matching, mapped custom attributes, call and note sync.

Overview

The teleCRM integration keeps your leads in sync between Kraya and teleCRM in both directions. Once connected, a lead you create or update in Kraya is pushed to teleCRM automatically, and leads you add or edit in teleCRM are pulled into Kraya on a regular schedule. This lets your team keep calling and working leads in teleCRM while Kraya stays up to date for WhatsApp follow-ups, AI qualification, and reporting — without any manual copy-paste.

The connection is organization-wide: one teleCRM account links to your whole Kraya organization, and it is set up by an administrator from the Integrations Hub.

What you can do

  • Connect your teleCRM account to Kraya using your Enterprise ID and API tokens
  • Automatically push new and updated Kraya leads to teleCRM in near real-time
  • Automatically pull new and edited teleCRM leads into Kraya every few minutes
  • Keep lead name, email, and phone consistent across both systems
  • Keep a lead's stage in Kraya aligned with its status in teleCRM (and vice versa)
  • Sync mapped custom attributes between the two systems
  • Import your existing teleCRM leads into Kraya as a one-time backfill when you connect
  • Update your API tokens or default country code, and disconnect at any time

How it works

After you connect teleCRM, Kraya sets the connection up in the background — it reads your teleCRM custom fields and stages so it knows how to map data between the two systems. Once setup finishes, the status shows Connected and syncing begins.

Sync direction and timing:

  • Kraya → teleCRM (near real-time): Whenever you create or update a lead in Kraya, the change is pushed to teleCRM within about half a minute. Only lead changes trigger a push — editing a lead's name, email, phone, stage, or a mapped attribute.
  • teleCRM → Kraya (every 5 minutes): On a schedule, Kraya checks teleCRM for newly created leads and for leads that were edited in teleCRM, and pulls those updates in. Because this runs on a poll, changes made in teleCRM can take a few minutes to appear in Kraya.

What gets synced:

  • Name, email, and phone — kept aligned in both directions.
  • Stage ↔ status — a Kraya lead's stage maps to a teleCRM status and back, matched by name. For the mapping to work, the Kraya stage name and the teleCRM status label must match (matching ignores upper/lower case).
  • Mapped custom attributes — any custom fields that were mapped during setup sync in both directions. Fields that are not mapped are left alone.

Initial import when you connect: Right after setup completes, Kraya runs a one-time import that pulls your existing teleCRM leads into Kraya. These imported leads are added quietly — they do not trigger WhatsApp sequences, Smart Triggers, or a re-push back to teleCRM — so connecting does not send a wave of messages to your existing contacts.

Prerequisites & basics

  • You must be an administrator in your Kraya organization. Integration setup is an admin-only task.
  • teleCRM is a paid-plan feature. On the free plan, opening the integration shows an upgrade prompt instead of the setup screen.
  • You need an active teleCRM account with:
    • Your Enterprise ID
    • A Sync token (Sync-type API token)
    • An Async token (Async-type API token)
  • Both tokens are generated inside teleCRM under Settings → API Tokens.

Step-by-step guide

Connecting teleCRM

  1. In the left sidebar, open the Integrations Hub.
  2. Under the Calling & Voice category, click the teleCRM card. The "Connect teleCRM" screen opens.
  3. Enter your Enterprise ID (required).
  4. Enter your Sync Token (required) — generate it from your teleCRM dashboard under Settings → API Tokens (Sync type).
  5. Enter your Async Token (required) — generate it from the same place (Async type).
  6. Optionally set a Default Country Code (for example, 91). This is used to normalize phone numbers that arrive without a country code prefix.
  7. Click Connect teleCRM.

After you connect, the status shows Setup in progress… while Kraya fetches your teleCRM fields and stages — this usually takes under a minute. Refresh the page to see the latest status. When setup succeeds, the status changes to Connected and the initial import begins.

Updating your settings

On the connected screen you can:

  • Change the Default Country Code — update the field and click Save Settings.
  • Update your Sync or Async token — clear the token field, enter the new token, and click Save Settings. Updating a token reconnects the account with the new credentials, and the status briefly returns to Setup in progress… while it re-verifies. Leaving a token field unchanged keeps the existing token.

The Enterprise ID cannot be changed on a connected account. To use a different Enterprise ID, disconnect and connect again.

Disconnecting teleCRM

  1. On the connected teleCRM screen, click Disconnect.
  2. Confirm when prompted ("Disconnect teleCRM? This will stop all sync.").
  3. The connection is removed and all syncing stops. Your existing leads in Kraya are kept; only the sync is turned off.

To resume syncing later, connect again with your Enterprise ID and tokens.

Settings and configuration

  • Enterprise ID — identifies your teleCRM account. Set at connection time and shown read-only afterward.
  • Sync Token — the Sync-type API token used for live syncing. Can be updated later (updating reconnects the account).
  • Async Token — the Async-type API token used for bulk imports. Can be updated later (updating reconnects the account).
  • Default Country Code — up to 3 digits (for example, 91 for India). Used to normalize phone numbers that don't already include a country code. Optional.

Advanced: push-only mode

By default the integration syncs in both directions — Kraya → teleCRM in near-real-time, teleCRM → Kraya on the 5-minute poll. If you want your Kraya changes to flow into teleCRM but do not want anything (new leads, edits, call/note actions, or the initial import) coming back from teleCRM, ask your Kraya POC to enable push-only mode on your account. When on:

  • Kraya → teleCRM push continues exactly as before (lead create/update, attribute changes, stage changes).
  • teleCRM → Kraya poll and the connect-time backfill are skipped.
  • The connection status still shows Connected; there is no UI toggle for this yet, so it's an ops-managed setting.
  • Flipping it back on later resumes the poll from wherever it left off (no duplicates — matching is by phone / teleCRM lead ID).

Connection status

The connected screen shows a status badge:

  • Connected — the account is set up and syncing normally.
  • Setup in progress… — the connection was just created or its tokens were updated, and Kraya is fetching your teleCRM fields and stages. This usually clears in under a minute; refresh to check.
  • Error — setup could not be completed, usually because the Enterprise ID or a token is incorrect. Verify your details, then disconnect and reconnect.
  • Inactive — the connection exists but is not actively syncing.

Role-based behavior

  • Admins: Can see the Integrations Hub, connect teleCRM, update its settings, and disconnect it.
  • Members: Do not see the Integrations Hub; teleCRM setup is an administrator task.

Limits and quotas

  • One teleCRM account per organization. You cannot connect a second teleCRM account while one is already active.
  • Paid plans only. teleCRM is not available on the free plan.
  • teleCRM → Kraya updates arrive on a 5-minute poll, so edits made in teleCRM are not instant in Kraya.
  • Phone numbers cannot be changed after a lead exists. A lead's phone is set when the lead is first created and is not overwritten by later updates in either direction.
  • Call logs and notes from teleCRM now sync into Kraya. When a teleCRM agent logs a call outcome or adds a note against a lead, the poll picks it up and mirrors it onto the same lead in Kraya — call entries land on the lead's call timeline (status, duration, agent, disposition where available), and notes appear on the lead's notes.
  • Only mapped custom attributes sync. Custom fields that were not mapped during setup are ignored.

Common edge cases

  • A lead I edited in teleCRM hasn't updated in Kraya yet teleCRM → Kraya syncing runs every 5 minutes. Wait a few minutes and refresh. If it still hasn't updated, confirm the connection status is Connected.

  • I changed a lead's phone number but it didn't sync Phone numbers are fixed once a lead exists and are not changed by later syncs in either direction. To correct a phone number, handle it directly in each system.

  • A lead's stage didn't move to match teleCRM (or vice versa) Stage and status are matched by name. Make sure the Kraya stage name and the teleCRM status label are the same (spelling and spacing must match; upper/lower case does not matter). If no matching stage is found, an imported lead lands in your default "Leads" pipeline at the "New Lead" stage.

  • A custom field isn't syncing Only fields mapped during setup are synced. If a field you expected isn't syncing, it may not be mapped. Contact the Kraya team to review your field mappings.

  • A blank value in teleCRM didn't overwrite my Kraya data This is intentional. An empty name or email coming from teleCRM will not erase an existing value in Kraya.

  • Connecting flooded — or didn't flood — my contacts with messages The one-time import that runs when you connect adds your existing teleCRM leads quietly, so it does not start WhatsApp sequences or Smart Triggers for those leads. New leads that arrive from teleCRM after the initial import follow your normal automation rules.

Troubleshooting

Status shows "Error" after connecting

  • Cause: Kraya could not verify your teleCRM account — usually an incorrect Enterprise ID, Sync token, or Async token.
  • Fix: Double-check your Enterprise ID and regenerate your tokens in teleCRM (Settings → API Tokens) if needed. Then disconnect and connect again with the correct details.

Status is stuck on "Setup in progress…"

  • Cause: Setup runs in the background and usually finishes within a minute, but the screen does not refresh on its own.
  • Fix: Refresh the page to load the latest status. If it stays in setup for much longer than a minute, disconnect and reconnect; if it still doesn't complete, contact the Kraya team.

Opening teleCRM shows an upgrade prompt instead of the setup screen

  • Cause: teleCRM is a premium feature and your organization is on the free plan.
  • Fix: Upgrade your plan to use the integration.

A new teleCRM lead never appeared in Kraya

  • Cause: The 5-minute poll may not have run yet, or the connection is not active.
  • Fix: Wait a few minutes and refresh. Confirm the status is Connected. If the lead still doesn't appear after several poll cycles, contact the Kraya team.

Decision tree

  • Can't reach the setup screen (upgrade prompt) → The integration is premium; upgrade your plan.
  • Connected but data isn't syncing from teleCRM → Wait for the next 5-minute poll and refresh; confirm status is Connected.
  • Stage/status not aligning → Check that the stage name and teleCRM status label match.
  • None of the above → Contact the Kraya team.

FAQs

  • How quickly do my Kraya changes reach teleCRM? Almost immediately — a lead you create or update in Kraya is pushed to teleCRM within about half a minute.

  • How quickly do teleCRM changes reach Kraya? teleCRM changes are pulled in every 5 minutes, so allow a few minutes for new or edited teleCRM leads to appear in Kraya.

  • Does connecting import my existing teleCRM leads? Yes. A one-time import runs right after setup and brings your existing teleCRM leads into Kraya. It runs quietly, so it won't start WhatsApp sequences or Smart Triggers for those leads.

  • Can I connect more than one teleCRM account? No. Each Kraya organization can have one active teleCRM connection at a time.

  • Where do I get my Sync and Async tokens? From your teleCRM dashboard under Settings → API Tokens. The Sync token is used for live syncing and the Async token for bulk imports.

  • Can I change a lead's phone number through the sync? No. A lead's phone number is fixed once the lead exists and is not changed by later syncs in either direction.

  • Why isn't a custom field syncing? Only custom fields that were mapped during setup are synced. Unmapped fields are ignored. Contact the Kraya team to review your mappings.

  • Do my teleCRM call logs and notes show up in Kraya? Yes. Call outcomes (status, duration, agent, disposition where available) and notes added inside teleCRM sync into Kraya on the same 5-minute poll as lead updates — calls appear on the lead's call timeline and notes appear on the lead's notes.

  • What happens to my leads if I disconnect? Your leads stay in Kraya. Disconnecting only stops the sync; it does not delete any leads.

Tips and best practices

  • Use the same stage and status names in Kraya and teleCRM so stages and statuses map cleanly between the two systems.
  • Set your Default Country Code if your teleCRM leads are stored without a country code prefix — this keeps phone numbers consistent for matching.
  • After connecting, spot-check a few known teleCRM leads in Kraya to confirm names, phones, and stages line up.
  • Keep your API tokens private. If a token is ever exposed, regenerate it in teleCRM and update it on the connected screen.

Screenshots

On this page