Integration

TelTel integration

TelTel is a Latvian cloud call center, VoIP and SMS provider. Send single or bulk SMS and read delivery reports and inbound SMS; run SMS campaigns to contact groups; build and start autodialer (predictive or call-flow) campaigns and their contact lists; start click-to-call calls; list calls with costs, recordings and transcripts; manage contacts, user statuses and caller IDs; look up numbers (HLR, billed) and manage rented phone numbers. Not exposed: ordering new numbers (a billed purchase with a multipart upload of registration documents), the inbox-side SMS write route (documented only as 'send a single message'), and the GET aliases of the SMS sends; users' own API keys are not returned. Authentication is the API key from Settings in the TelTel account, sent in the X-API-KEY header.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in TelTel.Built from the 67 TelTel tools below, on the connection you add once.

What you can do with TelTel

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Contact, 10 operations

  • add_autodialer_contactsAdd autodialer contactsPOSTAdds phone numbers to an autodialer campaign; a running campaign may dial them. Returns meta.created and meta.invalid counts.
  • create_contactCreate contactPOSTCreates a contact (phone and custom parameters 1 to 5) in a contact group. Returns its id and phone.
  • delete_autodialer_contactDelete autodialer contactDELETERemoves one contact, by its contact id, from an autodialer campaign. Returns meta.deleted.
  • delete_contactDelete contactDELETEPermanently deletes a contact. Returns meta.deleted.
  • get_contactGet contactGETReturns one contact: phone, contact group id and custom parameters 1 to 5.
  • list_autodialer_contactsList autodialer contactsGETLists the contacts (numbers to dial) of an autodialer campaign with call time, leg statuses, custom fields and operator. Page with limit (default 500) and offset.
  • list_contact_group_contactsList contact group contactsGETLists the contacts of one contact group with phone and custom parameters 1 to 5. Page with limit (default 500) and offset.
  • list_contactsList contactsGETLists contacts across all contact groups with phone, group id and custom parameters 1 to 5. Page with limit (default 500) and offset; filter by phone or id.
  • replace_contactReplace contactPUTOverwrites a contact with the fields sent (phone and group_id required). To change a few fields prefer update_contact. Returns meta.updated.
  • update_contactUpdate contactPATCHChanges only the fields sent on a contact; fields left out keep their current value. Returns meta.updated.

Group, 7 operations

  • assign_my_number_groupsAssign my number groupsPATCHAssigns a rented phone number to the given user groups. Returns the updated number with its users and groups.
  • create_contact_groupCreate contact groupPOSTCreates a contact group (a list SMS campaigns can send to). Returns its id and name.
  • delete_contact_groupDelete contact groupDELETEPermanently deletes a contact group. Returns meta.deleted.
  • get_contact_groupGet contact groupGETReturns one contact group: name, contact count and creation time.
  • list_contact_groupsList contact groupsGETLists contact groups (the lists SMS campaigns send to) with name, contact count and creation time. Page with limit (default 500) and offset.
  • replace_contact_groupReplace contact groupPUTOverwrites a contact group with the name sent. Returns meta.updated.
  • update_contact_groupUpdate contact groupPATCHRenames a contact group (changes only the fields sent). Returns meta.updated.

Autodialer, 6 operations

  • create_autodialer_campaignCreate autodialer campaignPOSTCreates an autodialer campaign (name, campaign_type, caller_id, agents, schedule, dialing and AMD settings). Returns its id; add numbers with add_autodialer_contacts and start it with run_autodialer_campaign_action.
  • delete_autodialer_campaignDelete autodialer campaignDELETEPermanently deletes an autodialer campaign. Returns meta.deleted.
  • get_autodialer_campaignGet autodialer campaignGETReturns one autodialer campaign with its type, status, caller IDs, agents, schedule, retry and AMD settings.
  • list_autodialer_campaignsList autodialer campaignsGETLists the autodialer (outbound dialer) campaigns with their type, status, caller IDs, agents, schedule and dialing settings. Use fields to return fewer columns.
  • replace_autodialer_campaignReplace autodialer campaignPUTOverwrites an autodialer campaign with the fields sent (name, campaign_type and caller_id required). To change a few fields, prefer update_autodialer_campaign. Returns meta.updated.
  • update_autodialer_campaignUpdate autodialer campaignPATCHChanges only the fields sent on an autodialer campaign; every field left out keeps its current value. Returns meta.updated.

Campaign, 6 operations

  • create_sms_campaignCreate sms campaignPOSTCreates an SMS campaign that texts the contacts of the given contact groups (NORMAL) or texts contacts on their birthday (BIRTHDAY). Returns its id; start it with run_sms_campaign_action.
  • delete_sms_campaignDelete sms campaignDELETEPermanently deletes an SMS campaign. Returns meta.deleted.
  • get_sms_campaignGet sms campaignGETReturns one SMS campaign: title, sender ID, contact groups, message, rate, unicode flag, state, type and creation time.
  • list_sms_campaignsList sms campaignsGETLists SMS campaigns with title, sender ID, contact groups, message, rate, state and type. Page with limit (default 500) and offset.
  • replace_sms_campaignReplace sms campaignPUTOverwrites an SMS campaign with the fields sent (title, from, contact_groups and message required). To change a few fields prefer update_sms_campaign. Returns meta.updated.
  • update_sms_campaignUpdate sms campaignPATCHChanges only the fields sent on an SMS campaign; fields left out keep their current value. Returns meta.updated.

User status, 5 operations

  • create_user_statusCreate user statusPOSTCreates a user (agent) status such as Out for lunch, optionally marked offline so users in it receive no calls. Returns its id.
  • delete_user_statusDelete user statusDELETEPermanently deletes a user status. Returns meta.deleted.
  • list_user_statusesList user statusesGETLists the user (agent) statuses: id, name, enabled, whether it counts as offline, and whether it is editable (system statuses are not).
  • replace_user_statusReplace user statusPUTOverwrites a user status with the fields sent. To change one field prefer update_user_status. System statuses are not editable. Returns meta.updated.
  • update_user_statusUpdate user statusPATCHChanges only the fields sent on a user status; fields left out keep their current value. System statuses are not editable. Returns meta.updated.

Action, 4 operations

  • list_autodialer_campaign_actionsList autodialer campaign actionsGETLists the actions history of an autodialer campaign (each action with its id and time).
  • list_sms_campaign_actionsList sms campaign actionsGETLists the actions history of an SMS campaign (each action with its id and time).
  • run_autodialer_campaign_actionRun autodialer campaign actionPOSTPerforms an action on an autodialer campaign; start begins dialing its contacts, which places billed calls. Returns the action id and name.
  • run_sms_campaign_actionRun sms campaign actionPOSTPerforms an action on an SMS campaign; start begins sending its billed messages. Returns the action id and name.

Custom status, 4 operations

  • create_autodialer_custom_statusCreate autodialer custom statusPOSTCreates a custom status (text up to 32 characters) that agents can set on autodialer contacts. Returns its id.
  • delete_autodialer_custom_statusDelete autodialer custom statusDELETEPermanently deletes an autodialer custom status. Returns meta.deleted.
  • list_autodialer_custom_statusesList autodialer custom statusesGETLists the custom statuses agents can set on autodialer contacts (id and value). Pass their ids in customized_statuses when creating a campaign.
  • replace_autodialer_custom_statusReplace autodialer custom statusPUTReplaces the text of an autodialer custom status. Returns meta.updated.

Report, 4 operations

  • get_received_smsGet received smsGETReturns one inbound SMS: sender, recipient, state, reception time, text and the handler e-mail or URL it was forwarded to.
  • get_sent_smsGet sent smsGETReturns the delivery report of one outbound SMS: state, detailed state, delivery time, parts, price, country and operator.
  • list_received_smsList received smsGETLists inbound SMS received on the account's numbers (newest first) with sender, recipient, text, reception time and the handler e-mail or URL. Page with limit and offset.
  • list_sent_smsList sent smsGETLists outbound SMS (newest first) with sender, recipient, country, operator, delivery state, parts, price and campaign id. Page with limit (default 500) and offset.

My number, 3 operations

  • get_my_numberGet my numberGETReturns one rented phone number with its description, prices, renewal and payment dates, SMS handler URL and e-mail, spam score and the users and groups it is assigned to.
  • list_my_numbersList my numbersGETLists the phone numbers (DIDs) the account rents: number, country, monthly price, SMS support, renewal, payment dates and spam score. Page with limit (default 50) and offset.
  • update_my_numberUpdate my numberPATCHChanges a rented number's auto renewal, description, or where its inbound SMS go (webhook URL or e-mail). Returns the updated number.

Call, 2 operations

  • create_click_to_callCreate click to callPOSTStarts a click-to-call: TelTel calls caller_number first (your agent) and, once answered, dials destination_number and bridges them. Places a billed call. Returns status and message.
  • list_callsList callsGETLists calls (newest first) with direction, type, status, durations, cost, caller and callee, hang-up side, transfer and recording URL; optionally transcripts. Page with limit and offset.

Country, 2 operations

  • get_number_countryGet number countryGETReturns one country where numbers can be ordered: prefix, SMS support, verification need, setup and monthly prices and number types.
  • list_number_countriesList number countriesGETLists the countries where new phone numbers can be ordered, with prefix, SMS support, whether verification is needed, and setup and monthly prices. Use an id with list_number_price_groups.

Text, 2 operations

  • send_bulk_smsSend bulk smsPOSTSends several SMS in one request (billed; the vendor recommends at most 1000). Full success: data is a list of {id, index}. Partial failure (HTTP 207): data.success lists the sent messages, data.errors the refused ones.
  • send_smsSend smsPOSTSends one SMS (billed) from a sender ID to a number in international format. Returns the message id; check delivery with get_sent_sms.

User, 2 operations

  • assign_my_number_usersAssign my number usersPATCHAssigns a rented phone number to the given users. Returns the updated number with its users and groups.
  • list_usersList usersGETLists the account's users (agents) with login name, real name, e-mail, admin flag, internal number, state, online devices and access groups. Users' API keys are not returned.

Balance, 1 operation

  • get_account_balanceGet account balanceGETReturns the account's money position: credit (negative means an amount owed), credit_limit and the available balance.

Bulk, 1 operation

  • create_contacts_bulkCreate contacts bulkPOSTCreates several contacts in one request. Full success: data is a list of {id}, one per new contact. Partial failure (HTTP 207): data.success lists the created contacts, data.errors the refused ones.

Cidgroup, 1 operation

  • get_user_caller_id_groupsGet user caller id groupsGETReturns a user's caller ID setup: all caller ID groups, the user's own caller IDs and groups, the account's DIDs and CIDs, and whether dynamic caller ID is on.

Device, 1 operation

  • list_devicesList devicesGETLists the account's SIP devices (extensions): owner user, online state, latency, registration URI and time, device and PBX IP addresses and server location.

Livestat, 1 operation

  • get_autodialer_campaign_live_statsGet autodialer campaign live statsGETReturns live stats of a running autodialer campaign: calls waiting, calling and talking, longest waiting time, busy agents percent, boost and agent counts.

Lookup, 1 operation

  • lookup_phone_numbersLookup phone numbersGETLooks up phone numbers in the mobile network (HLR): whether each is valid and reachable, with status and API status details. Billed per request; the price is not published.

Order, 1 operation

  • list_number_ordersList number ordersGETReturns phone number orders with status, creation time and details (country, price group, count, prices). Filter by status only.

Phone, 1 operation

  • delete_autodialer_contact_by_phoneDelete autodialer contact by phoneDELETERemoves a contact from an autodialer campaign by its phone number. Returns meta.deleted, the number of contacts removed.

Price group, 1 operation

  • list_number_price_groupsList number price groupsGETLists the number groups (city or type, e.g. mobile) available in a country, with setup and monthly price, SMS support and registration requirements. Page with limit (default 100) and offset.

Status, 1 operation

  • set_user_statusSet user statusPATCHSets a user's (agent's) current status, such as an away status from list_user_statuses. An offline status stops the user receiving calls. Returns meta.updated.

Use TelTel from Claude Code, Cursor or Codex

Connect TelTel in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its TelTel operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect TelTel

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect TelTel once

    Add your TelTel connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

TelTel integration FAQ

What can you do with the TelTel integration?

LiveContext exposes 67 operations on TelTel, covering contact, group, autodialer and campaign.

Popular integrations

Browse the whole catalog