INBOUND CALLS

Someone dials your number. Your code decides what happens next.

Teler routes the call to your own endpoint the moment it arrives. Your agent can just listen and respond, no keypad menu required.

USE CASES

Build inbound flows that answer, route and escalate on your terms

An agent that answers immediately

No hold music, no queue. The call reaches your logic the moment it connects, so your agent can greet the caller from the very first second.

Routing by number, not by menu

Give each product line, region, or team its own number, all landing in the same codebase. Your code reads the dialed number to tell calls apart.

A fallback to a human, on the first ring

Route straight to a person for numbers where your agent shouldn’t be the first point of contact, set per number, alongside the ones your agent answers.

Inbound and outbound on the same integration

Handle calls coming in the same way you handle calls going out: one codebase, one set of call-control tools for interrupting, transferring and recording.

Built for calls that arrive on your terms

Per-number routing

Every inbound call lands on the exact endpoint set for that number.

Streaming or SIP

Incoming Call URL for Voice Apps, inbound SIP URL for SIP Trunks.

No menu tree

Your endpoint decides what happens, so callers can just start talking.

One codebase

Point many numbers at one endpoint and tell calls apart by number.

What our customers say about us

“Our experience with FreJun Teler has been outstanding – stable SIP connectivity, excellent call quality, and developer-friendly APIs that helped us build and scale our AI voice solutions efficiently.”

Yadu Nath

Co-Founder, Vertivox

“We were using Twilio, but it didn’t support Indian numbers for what we needed. We moved to FreJun and built Voizly’s outbound calling on Teler’s SIP trunking – we’re now running up to 15 concurrent calls and about 150,000 calls a month.”

Aniruddh Kukadiya

CEO, Artistry Solutions

“We use Teler to redirect calls straight into our ElevenLabs SIP trunk, so every call to that number continues the conversation there without any extra setup on our side.”

Saif Ali

Head of Engineering, Ajjas

We built a calling agent for our recruitment business on Teler – this is the first time we’re using telephony at all, and we’re already running about 5,000 minutes a month.

Anoop Jain

CEO, gnxt systems

“We switched to FreJun Teler from Vobiz and had it in production within two days – we’re now running about 25,000 calls a month.”

Arpit Soni

Associate Product Manager, Dvara E-Registry

Related Features

AI Voice Agents

SIP Trunking India

You bring the model. We handle the phone line. Indian numbers provisioned by API. Elastic SIP trunking. Live call audio

Vobiz alternative

Both give your AI voice agent the SIP trunk and voice API it needs to take Indian phone calls. On

Frequently Asked Questions

Have more questions? 
Reach out to us at support@frejun.com.

How does Teler know where to send an incoming call?

Through the routing configured on that number - an Incoming Call URL for a Voice App, or an inbound SIP URL for a SIP Trunk.

Can I route different numbers to different endpoints?

Yes - each number's routing is configured independently, so different numbers can land in entirely different places.

Does inbound work the same way for Voice Apps and SIP Trunks?

The mechanism differs - Incoming Call URL for Voice Apps, inbound SIP URL for SIP Trunks - but both deliver the call to your own infrastructure the same reliable way.

Do I need a menu tree for inbound calls?

No - your endpoint can connect straight to an AI agent that just listens, without a keypad menu first.

Can the same number handle both inbound and outbound calls?

Yes - inbound and outbound both run through the same call-control tools on the same number.

Let your code decide what happens
when the phone rings

✨ Building an AI voice agent? Get 25,000 free calling credits on your first upgrade with Teler →

FreJun Dialer

FreJun Teler