TelTel
MessagingConnect AI agents to TelTel, a Latvian messaging and call center platform. Agents send single, bulk, and two way SMS, run SMS and autodialer campaigns, manage contacts and phone numbers, and create click to call requests so outbound campaigns and customer follow up run automatically.
What This Integration Enables
TelTel is a Latvian call center and messaging platform, and the catalog description of it as calls and SMS undersells what the API actually is. One key reaches SMS in both directions, SMS campaigns, click to call and call history, a contacts CRM with groups, agent users and their statuses, phone number purchasing across countries, HLR number lookup, and a full autodialer with its own campaigns, live statistics, custom dispositions and contact list. Sixty nine actions is a lot of surface for something filed under messaging, and the reason to care is that the SMS and the voice sides share one contact database and one number inventory. A sequence that texts a prospect, gets no answer, and then places a click to call from the same owned number is a single flow here rather than an integration project.
Two design choices in this connector are worth knowing before you build on it. TelTel offers GET variants of three of its send routes as a convenience for callers who cannot issue a POST, and they are deliberately not built, because a GET that dispatches a billed SMS is a trap for anything that retries, prefetches, previews a link or replays a log. And the vendor maintains a strict split between partial and full writes throughout, so every resource that supports both ships as two named actions: Update changes only the properties supplied, Overwrite replaces the whole record and clears anything omitted. On an autodialer campaign that difference is the schedule, the assigned agents and the retry rules, so the verb is pinned per action and every overwrite says in its own description what it destroys.
The sender is picker backed, which is rarer in this category than it should be. Most gateways publish no route that lists the numbers you own, which leaves the From field as free text and leaves a typo indistinguishable from a configuration change. TelTel has one, so every send here chooses from the account's real inventory. There are no triggers: across all seventy one documented operations there is not one webhook, callback or subscription route, and the callback URL is configured in the TelTel account interface. List Inbound Messages is the supported substitute and this vendor is unusually well equipped for it, with inbound messages as a first class filterable list, so a poller that sorts by descending id and keeps the highest id seen reads only what is new. Failures and unreachable numbers surface as automation exceptions rather than as quiet gaps in a campaign report.
Without FlowRunner
With FlowRunner
Use Case Scenarios
A follow up sequence that can answer back
A sales team runs a text first follow up on inbound leads. The agent matches or creates the contact with Create Contact, adds it to the right group, and sends with Send Two-Way SMS from a number the account owns. Because the number is real and inbound is a first class list, List Inbound Messages returns the answers with enough filtering to attribute each one, and the reply goes back into HubSpot against the right record. Where a reply reads as a request to talk, Create Click-To-Call rings the rep and the prospect together, which is a materially different follow up experience from asking the prospect to book a slot and hoping. Anything ambiguous lands in Slack with the outbound message and the reply shown together rather than being classified by guess.
A campaign changed without being destroyed
Marketing operations wants to shift a running SMS campaign's window and swap its message. The agent reads the current record with Get SMS Campaign, calls Update SMS Campaign with only the two properties that change, and leaves the rest alone. That sounds unremarkable until you notice the alternative available on the same resource: Overwrite SMS Campaign replaces the record and clears everything omitted, and on a campaign assembled over weeks that is a silent loss rather than an error. List SMS Campaign Actions and Perform SMS Campaign Action then start or stop it, and starting a campaign dispatches to a whole contact list with no further call, which is why the start verb is treated as a send rather than as a state change.
Cleaning a list before it costs money
Before a large outbound push, the agent runs Look Up Numbers over the target list to find disconnected and mis formatted numbers. The route is a GET and it is billed at a small per request fee, which is a useful reminder that a read verb is not proof a route is free. Numbers that fail the lookup are written back to Salesforce as bad contact data rather than being sent to and counted as reach. Get Account Balance gates the send itself. What remains goes out through Send Bulk SMS, capped at a thousand messages per request and enforced before dispatch, so an oversized batch is refused rather than partially delivered.
Human-in-Loop Highlight
The gate on TelTel is the number inventory, and specifically the fact that releasing a number is disguised as a billing preference. Update My Number carries auto renewal. Turning it off does not reduce a subscription, it releases the number at the end of its term, and once released it is gone. The reply path is dead, and every message the business already sent that said reply to this number becomes a dead end for the customer who trusts it. On the other side of the same inventory, Create Number Order spends real money and creates a recurring monthly charge for as long as the numbers are held, priced by List Available Number Groups and multiplied by the count. Both directions of the number lifecycle are consequential and neither of them looks it in an action list.
So an agent doing cost review can gather every fact and still not be allowed to act. It can call List My Numbers, count how many outbound messages left each number with List Outbound Messages. It can count how many replies came back to it with List Inbound Messages, and check whether any campaign or user is still assigned to it through Assign Number To Groups and Assign Number To Users. Then it stops, and into Slack it says: "Number +371 2XXX 4419 has sent 11,400 messages in the last six months and received 812 replies, most recently four days ago. It is assigned to the Renewals group and to two users. Turning off auto renewal on this number releases it at the end of its term and the release is permanent. Release it, or keep it and trim a different one?"
That is the digital andon cord placed where an agent's own logic is most likely to be confidently wrong: the number looks underused on a monthly cost report and looks load bearing on a reply report, and only a person knows which of those the business actually cares about. It is worth naming what this gate is not. It is not an approval on outbound copy, and it is not a spend approval on an individual send, both of which an agent can settle from Get Account Balance. It is a gate on a change to the identity the company has already published to its customers, which is exactly the class of decision Orchestration as a Service exists to keep in human hands while the rest of the sequence keeps running.
Agent Capabilities
69 actionsSMS
3- Send SMS Sends one message from a number the account owns, chosen from the real inventory rather than typed as free text. The POST form is used always, because the vendor's GET variant would let any retry, prefetch or log replay send the message again.
- Send Bulk SMS Sends up to a thousand messages in one request, with the ceiling enforced before dispatch so an oversized batch is refused rather than partially delivered.
- Send Two-Way SMS Sends a message set up to collect replies, which is the form to use whenever the next step in a flow depends on the recipient answering rather than on the message simply arriving.
SMS Reports
4- List Outbound Messages Returns sent messages with filtering, which is the surface for reconciling what actually left against what a campaign intended.
- Get Outbound Message Returns one outbound message in full, for when a specific delivery needs explaining rather than a batch summarizing.
- List Inbound Messages Returns received messages as a first class filterable list with five parameters. This is the supported substitute for the trigger TelTel does not offer, and sorting by descending id while keeping the highest id seen reads only what is new.
- Get Inbound Message Returns one inbound message in full, which is what a flow attaches to a CRM record or hands to a person alongside the outbound text it answers.
SMS Campaigns
8- List SMS Campaigns Returns the account's SMS campaigns, paged, which is how a flow finds the campaign it needs to read or change.
- Create SMS Campaign Creates a campaign against a contact list. Creating does not dispatch; the start action does, which is the separation that makes a campaign reviewable before it costs anything.
- Get SMS Campaign Returns one campaign in full. Run it before any update, because it is the only way to know what an overwrite would clear.
- Update SMS Campaign Changes only the properties supplied and leaves everything else alone. This is the safe verb and the one to reach for by default.
- Overwrite SMS Campaign Replaces the whole campaign record, clearing anything omitted. Use it deliberately when the intent really is to redefine the campaign rather than adjust it.
- Delete SMS Campaign Removes a campaign. Messages already dispatched are unaffected, but the campaign's own configuration and its association with the contact list are gone.
- List SMS Campaign Actions Returns the actions available on a campaign, which is how a flow discovers the start and stop verbs rather than hardcoding them.
- Perform SMS Campaign Action Runs one of those actions. Starting a campaign dispatches to the whole contact list without any further call, so this is a send in everything but name.
Calls
2- List Calls Returns call history, which is what pairs a voice attempt with the SMS thread that preceded it on the same contact.
- Create Click-To-Call Rings two real telephones and connects them, which is how a text conversation becomes a live one without asking the customer to dial anything.
Account
3- Get Account Balance Returns the account balance. This is the cheapest proof the credential works and the natural gate before any bulk dispatch.
- Look Up Numbers Runs an HLR lookup over a comma separated list of numbers to find disconnected and mis formatted ones. It is billed per request despite being a GET, so a read verb here is not proof a route is free.
- List Devices Returns the devices registered on the account, which is the inventory behind the platform's voice side.
Contacts
7- List Contacts Returns the contacts CRM, paged up to five thousand records with the offset ceiling enforced before the request.
- Create Contact Adds one contact, which is what turns an inbound lead into something a campaign and a group can address.
- Create Contacts In Bulk Adds many contacts in one request, for importing a list rather than looping a single create.
- Get Contact Returns one contact in full, including the fields an overwrite would clear.
- Update Contact Changes only the properties supplied. The default verb for enriching a record from another system.
- Overwrite Contact Replaces the whole contact record and clears anything omitted, which on an enriched contact means losing every field the writing system did not know about.
- Delete Contact Removes a contact from the CRM. Message history against the number is not what is being deleted here, but the record the campaigns address is.
Contact Groups
7- List Contact Groups Returns the groups, which are the audiences campaigns and autodialer campaigns are pointed at.
- Create Contact Group Creates a group, which is the unit a campaign dispatches to and therefore the unit worth getting right before a campaign starts.
- Get Contact Group Returns one group with its configuration.
- Update Contact Group Changes only the properties supplied.
- Overwrite Contact Group Replaces the whole group record, clearing anything omitted.
- Delete Contact Group Removes a group. Campaigns pointed at it lose their audience, so check what references it first.
- List Contact Group Contacts Returns the contacts inside one group, which is the read that answers who a campaign is actually about to reach.
Users
3- List Users Returns the agent users on the account with their state, which is what a flow uses to route work to someone who is actually working.
- Get User Caller ID Groups Returns the caller ID groups a user belongs to, which decides what number their outbound activity presents as.
- Set User Status Sets an agent's status, which is how availability can be driven from a shift schedule rather than from each person remembering to toggle it.
User Statuses
5- List User Statuses Returns the status vocabulary configured on the account, which is what Set User Status accepts.
- Create User Status Adds a status to that vocabulary, for teams whose availability states are more specific than available and away.
- Update User Status Changes only the properties supplied on a status definition.
- Overwrite User Status Replaces the whole status definition, clearing anything omitted.
- Delete User Status Removes a status definition. Anything currently set to it needs a destination, so read the users first.
Phone Numbers
10- List My Numbers Returns the numbers the account actually owns, and it is what backs the From parameter on every send. This is why an unowned sender cannot be typed into a flow here.
- Get My Number Returns one owned number in full, including its renewal state, which is the fact that matters most and looks least important.
- Update My Number Changes a number's settings, including auto renewal. Turning auto renewal off releases the number at the end of its term, which is a destructive change to a published identity rather than a billing preference.
- Assign Number To Groups Assigns a number to caller ID groups, which decides which teams present as it.
- Assign Number To Users Assigns a number to specific users, for the same reason at the level of an individual.
- List Available Countries Returns the countries numbers can be ordered in, which is the first read of any expansion into a new market.
- Get Available Country Returns one country's detail, including what the platform requires before a number there can be issued.
- List Available Number Groups Returns the number groups available to order with their price. Read it before ordering, because the count multiplies the price into a recurring charge.
- List Number Orders Returns the account's number orders, which is the record of what has been bought and what is still in progress.
- Create Number Order Buys phone numbers. It spends real money and creates a recurring monthly charge for as long as the numbers are held, and it is the only multipart route in this service because it can carry registration documents.
Autodialer
13- List Autodialer Campaigns Returns the autodialer campaigns configured on the account.
- Create Autodialer Campaign Creates a dialing campaign with its schedule, agents and retry rules. Two settings inside its settings object matter more than the rest: whether the campaign stops once every contact is processed, and whether answering machines are detected at all.
- Get Autodialer Campaign Returns one campaign in full, which is the only way to know what an overwrite of it would clear.
- Update Autodialer Campaign Changes only the properties supplied, leaving the schedule, agents and retry rules alone.
- Overwrite Autodialer Campaign Replaces the whole campaign and clears anything omitted, which on a dialing campaign means losing its schedule, its agents and its retry rules.
- Delete Autodialer Campaign Removes a dialing campaign along with its configuration.
- List Autodialer Actions Returns the actions available on a dialing campaign, which is how the start and stop verbs are discovered rather than assumed.
- Perform Autodialer Action Runs one of those actions. Starting a campaign begins dialing a whole contact list without any further call.
- Get Autodialer Live Stats Returns the live state of a running campaign, which is the read a supervising flow polls rather than a report it runs afterwards.
- List Autodialer Custom Statuses Returns the custom dispositions configured for dialing outcomes.
- Create Autodialer Custom Status Adds a disposition, which is how call outcomes become something a downstream flow can branch on.
- Overwrite Autodialer Custom Status Replaces a disposition definition, clearing anything omitted.
- Delete Autodialer Custom Status Removes a disposition definition. Calls already dispositioned with it need somewhere to go.
Autodialer Contacts
4- List Autodialer Contacts Returns the contacts loaded into a dialing campaign.
- Add Autodialer Contacts Adds contacts to a dialing campaign. If the campaign is already running they are dialed too, so this is not a staging operation.
- Delete Autodialer Contact Removes one contact from a dialing campaign by its identifier.
- Delete Autodialer Contact By Phone Removes a contact from a dialing campaign by phone number, which is the form to use when a suppression request arrives with a number rather than an id.
Frequently Asked Questions
What can FlowRunner do with TelTel?
FlowRunner agents can run Send SMS, Send Bulk SMS, and Send Two-Way SMS in TelTel, plus 66 more actions.
Does connecting TelTel to FlowRunner require OAuth?
No. TelTel connects to FlowRunner with an API key, no OAuth flow required.
Can TelTel trigger a FlowRunner workflow automatically?
TelTel doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with TelTel
$100 in credits. No card required. Connect in minutes.