OUTBOUND CALLS

Dial from your code. Run as many calls at once as your day needs

One API call places an outbound call. Your channel limit decides how many can run at the same time.

Container (FreJun Illustrations — All Pages) (12)

USE CASES

Build reminder, verification and win-back campaigns from one API

A reminder campaign that runs itself

Dial through a list of appointments or renewals, with your agent delivering the same message on every call, one calls.create() request per contact.

A reminder campaign that runs itself
Verification calls at volume

Verification calls at volume

Confirm a one-time code or a booking, across as many calls as your channel limit allows at once. Your status callbacks report how each call went.

Recovery and win-back calling

Reach a list of lapsed customers with the same agent, one call after another. Your status_callback_url tracks the progress of every call.

Recovery and win back calling
A dialer for your own product

A dialer for your own product

Let your application trigger outbound calls programmatically, the same way a human dialer would, without any manual dialing involved.

Built for campaigns, not just single calls

One API, any volume

The same calls.create() request that places one call runs a campaign.

Shared concurrency

Outbound draws from the same channel pool as inbound: one limit.

Sized for your peak

Your channel limit covers calls running at once, not your list size.

Per-call status

Your status callback URL reports each call's progress as the call runs.

What our customers say about us

Related Features

Both give your AI voice agent the SIP trunk and voice API it needs to take Indian phone calls. On
Local, toll-free, and mobile numbers in 50+ countries, live in seconds from the API or the dashboard. Point every one
Teler gives your code a phone line - place and receive calls, stream audio both ways while the call is

Frequently Asked Questions

Have more questions?

Reach out to us at support@frejun.com.

How many outbound calls can I run at the same time?

As many as your channel limit allows, shared across everything running on your account - inbound and outbound both draw from the same pool.

No - the same calls.create() request that places a single call is what a large campaign is built from.

Your status_callback_url reports on individual call progress, so a large campaign stays visible call by call.

No - size it to your busiest concurrent moment, not the total number of calls you'll eventually place.

Any of them - the dial API and concurrency model are the same regardless of what's running your agent's speech.

Dial from your code, at whatever
scale your day needs