About Quiz Night Live
Quiz Night Live is a Call TV show (Now off air). The objective of
the show is to encourage viewers to call a premium rate phone number to
answer a question live on air. If a caller gets the question right,
they win some money. In order to stand a chance of getting through to
the studio, a caller must first be entered into a 'Call Queue'. They
stand a 1 in X chance of getting into the call queue. A caller can
enter into the call queue by either calling a premium rate phone
number, or by entering for free on a website.
 |
 |
Entry via the web / Caller registration
The objective of the project
The objective of this project was to create a complete IVR
(Interactive Voice Response) solution for the Call TV Show. In summary
this was a mission critical application for a live TV show, and
required the following functionality:
- Handling incoming calls from BT, and managing the status of these calls in a queue
- Handling call entries from the web, and making an outbound call to a viewer to add them to the queue
- Creating a studio application which enables the TV studio to put people live on air
- Creating a CRM system which collects data from callers either through a voice recording, or through an online registration
- Providing a detailed reporting system to feedback an analysis of a TV show, and the breakdown of every call made
- Error tracking and flagging
 |
 |
The studio application to manage the call queue / login via the web
Meeting the objectives
The site was created in PHP 5 + MySQL. The technology for the show
is based on making and receiving GET requests to a British Telecom
API, outbound HTTPS requests are made using cURL. Depending on the
paramaters sent with the request, different actions can be performed
such as adding callers to a queue, and connecting them to a studio
line. Security was a major issue, and all working classes were beyond
the reach of http requests, and APIs were locked down to IPs. All
functionality was separated from the front end using the Smarty
template engine.
The site was extremely resilient, and performed to an excellent
standard. The error flagging ensured that if any problems were
encountered e.g. with BT exchanges, they were flagged by the
application as such, enabling 100% transparancy of the technological
processes involved in the show.
About Quiz Night Live
Quiz Night Live is a Call TV show (Now off air). The objective of
the show is to encourage viewers to call a premium rate phone number to
answer a question live on air. If a caller gets the question right,
they win some money. In order to stand a chance of getting through to
the studio, a caller must first be entered into a 'Call Queue'. They
stand a 1 in X chance of getting into the call queue. A caller can
enter into the call queue by either calling a premium rate phone
number, or by entering for free on a website.
|
|
Entry via the web / Caller registration
The objective of the project
The objective of this project was to create a complete IVR
(Interactive Voice Response) solution for the Call TV Show. In summary
this was a mission critical application for a live TV show, and
required the following functionality:
- Handling incoming calls from BT, and managing the status of these calls in a queue
- Handling call entries from the web, and making an outbound call to a viewer to add them to the queue
- Creating a studio application which enables the TV studio to put people live on air
- Creating a CRM system which collects data from callers either through a voice recording, or through an online registration
- Providing a detailed reporting system to feedback an analysis of a TV show, and the breakdown of every call made
- Error tracking and flagging
|
|
The studio application to manage the call queue / login via the web
Meeting the objectives
The site was created in PHP 5 + MySQL. The technology for the show
is based on making and receiving GET requests to a British Telecom
API, outbound HTTPS requests are made using cURL. Depending on the
paramaters sent with the request, different actions can be performed
such as adding callers to a queue, and connecting them to a studio
line. Security was a major issue, and all working classes were beyond
the reach of http requests, and APIs were locked down to IPs. All
functionality was separated from the front end using the Smarty
template engine.
The site was extremely resilient, and performed to an excellent
standard. The error flagging ensured that if any problems were
encountered e.g. with BT exchanges, they were flagged by the
application as such, enabling 100% transparancy of the technological
processes involved in the show.
