Call Request Form Samples (ASP)

By adding three pages to your web rather than one you have the ability to add your corporate style to the success and failure report pages, integrating WebCallback more closely with your site.

After reading these notes you will want to get the forms which accompany these technical notes.

The difference between the ASP pages included in this directory and the simpler HTML sample pages is on the use of programming to pass information between the pages. For a description of this technique, look at the implementation notes.

Changes You Must Make

Note that all pages should work correctly, calling the WebCallback offices at GlobalPhone, as they are delivered to you. Since we cannot always control how these files are distributed we strongly urge you to verify that the code works as delivered before attempting to modify it for your own web.

To put this more complex processing into your webs you need the source of the appropriate call form page, and also of the Success.htm and Failure.htm pages from the same directory.

Just take the ASP source of three pages and put it into your webs, adding appropriate look-and-feel and removing text you don't want your readers to see.

The pages you will need are a call form (we give you a choice of four), a success page and a failure page.

We include links to each page here, but you should not use your browser to get the page sources: the pages are programs, and should be copied from your filestore into your web server's filestore for editing.

SingleCall1.asp Simple form for making calls to a single number, country code input as text
MultiCall1.asp Page with multiple call forms, each calling a separate number, country code input as text
MultiCall2.asp Page with a single call form, call recipient selected by pull-down, country code input as text
MultiCall3.asp Page with single call form, call recipient selected by radio button, country code selected by pull-down
Success.htm Standard call success page
Failure.asp Standard call failure page

Then call GlobalPhone, or have us call you via WebCallback, to set up a called number, obtain a site identifier, and authorize test calls from your web if you haven't already done so. (The site identifier can be obtained by signing up online).

You will need to change the ASP code to use your number rather than GlobalPhone's.  You do this by replacing "globalphone" with your own site identifier in the part of the code which reads:

<input type="hidden" name="SiteId" value="globalphone">

The call forms capture, where possible, the URL of the page the user clicked on to bring up the form. Some browsers don't provide this "HTTP_REFERER" information, and so a default is established as a part of the code.

If you don't want your successfull calls to end up at the Web Callback home page, you should edit the part of the code which reads:

If Referer="" Then Referer="http://www.webcallback.com/"

so the Callback processor returns to a page inside your web.

You will also need to edit the values of two other hidden parameters: SuccessPage and ErrorPage. These values should be URLs pointing to the pages where you have located them in your in your site. The code looks like this:

<input type="hidden" name="SuccessPage" value="http://www.webcallback.com/Success.asp">
<input type="hidden" name="ErrorPage" value="http://www.webcallback.com/Failure.asp">

In fact, if you drop the WebCallback pages into your web's home directory, you should just be able to replace www.webcallback.com with www.yoursitename.com.

The ReturnPage, SuccessPage and ErrorPage fields should be complete URLs, with or without the leading http:, such as //www.microsoft.com/. If you do not provide a success or a failure page the system will normally use a default page, but this behavior should not be relied upon.

The multiple-call examples we give introduce a feature of WebCallback which has not been mentioned before: you can put call recipients into several subgroups, each of which has its own telephone number.

The examples use two individuals, Guy and Steve, each of whom have their own number, and a subgroup called any which has been set up to treat all available WebCallBack numbers as a hunt group.

If you think you might need this valuable additional service, please have us call you to discuss it further.

We plan to add other languages (Perl and Cold Fusion, for example) as demand emerges.