• SQL Server isn't an automation engine (or rather not a *general purpose* automation engine), and isn't going to have the hooks you would want to do telephony. You will end up having to do .NET and adding telephony libraries to that (or some such similarsolution), possibly pulling the phone #'s out of SQL if that's where they are stored.

    ----------------------------------------------------------------------------------
    Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?