📖
API Documentation
  • About
  • Version History
  • Introduction
    • Account Setup
    • Platform Features
    • Mid Call Divert/Mid Call Conference
    • Call Whisper
    • Conferencing
    • Percentage Distribution Algorthm
    • Call Queueing
    • Call Recording
    • Outbound Call
    • IVR Voicemail Retrieval Telephone Service
    • IVR Service Switcher Telephone Service
    • Web Service Security
    • Web Service Definition Language
      • Using a development environment other than the .NET Platform
    • Web Service Error Handling
    • Real-Time Multi-leg Call Data Records
      • Pseudo Code
      • Real-Time Multi-Leg CDR Call Types
    • Status Code Table
    • Default Audio
    • Development Guidelines
      • Development LAB Platform Test Harness
    • Post Call
    • DTMF Controlling Party
    • Data Rentention Policy
    • API Availability
    • Dynamic Call Agent (DCA)
      • Status Code Table
      • Call Outcome Table
      • Call Status Table
      • IVR Dynamic Call Agent Service
      • Apology Modes
    • JSON API
    • Emails
      • Custom Email Settings
      • Not Receiving Emails
      • Global Email Variables
      • Using Custom Service Variables within your emails
      • Email Content Type
      • Email Address HTML encoding
    • TimeZone Offset Setting
      • TimeZone Offset Table
      • Daylight Saving Time Changes
    • Public IP Addresses
    • Default Email Settings
    • Scheduled Call Feature
      • How to create a Scheduled Call request
      • What CLI be presented to the called parties
      • How to check the progress of a Scheduled Call request
      • How to retrieve the call statistics for my Scheduled Calls
      • How to delete a queued Scheduled Call request
      • How many simultaneous Scheduled Calls can be in progress
      • How many Scheduled Call requests can be created
  • Service Creation
    • Node XML structure
    • Service XML structure
    • Custom Service Variables
    • Variable Scope
    • Node Security
    • Graphical Representation of a Sample Service
    • Sample Service XML
    • Sub Plans
    • Sub Plan Example XML
  • Web Service Authentication
  • Service Audio
  • Node Reference
    • Start
    • Page 1
  • Security Methods
  • Service Management Methods
  • Audio Management Methods
  • General Methods
  • File Management Methods
  • Real-Time Data Methods
  • Service Number Activation Methods
  • Number Group Methods
  • Account Methods
  • Payphone Barring
  • Dynamic Call Agent Methods
  • Tiff to Fax Methods
  • Call Barring Methods
  • Platform Logging Methods
  • Platform Logging
  • Data Tables
  • Scheduled Call
  • External Number Management Methods
  • Phone Book Management Methods
  • Origin List Management Methods
  • Private SIP Management Methods
  • Bulk Configuration
  • Appendix
Powered by GitBook
On this page

Was this helpful?

  1. Introduction

Scheduled Call Feature

PreviousDefault Email SettingsNextHow to create a Scheduled Call request

Last updated 2 months ago

Was this helpful?

The Advanced Services Platform was designed primarily to handle inbound calls to geographic and non-geographic numbers, and offers simple 1-2-1 number translation services, as well as more complex services including queuing, automatic call distribution, pre-recorded audio, conferencing and call recording, as well as ‘logic’ functionality such as date, time, CLI routing and data tables.

Conversely, the ‘Scheduled Call’ feature allows customers with API access to initiate outbound calls from the Advanced Services Platform, where the Initial Target Destination (“First Party”) receiving the call might be a customer that requested a call-back for example. Scheduled Call requests can be submitted for immediate processing or can be scheduled for a future date.

A Scheduled Call must always be associated with an existing (and dialable) inbound Service Number (geographic or non-geographic) on your account or a sub account of yours in order that the call plan configuration assigned and active on it can be presented to the Initial Target Destination when the call is answered.

When the Initial Target Destination answers the call from the platform, they adopt the role of “inbound calling party” or “A-Party” – i.e. their call is handled in the same way as a normal inbound call – including the ability to call another number – the “called party” or “B-Party”. Scheduled Calls can contain any platform functionality (except Fax) – they don’t always have to result in an outdial – they can be simple audio services - they could direct the caller into a conference service or a queue and can even include the Post Call feature.

The following shows a simplified call flow with inbound-only functionality where the Scheduled Call feature is not active on the customer account:

The call flow ‘Start’ entry point node has an additional branch if the customer account has access to the Scheduled Call feature:

If Scheduled Call is not enabled in the Start Node’s properties, the branch will still appear in Service Designer but connecting further nodes to it is not mandatory.

Note that both inbound calls and scheduled calls can proceed through the same functionality – they don’t need to have separate call flows: