This is an example of a random teleport, as requested by cstrikeman. I hope I understood what you wanted to know.
The setup is as follows:
1 trigger_teleport named teleport_from_here 3 info_teleport_destination named destination1, destination2, destination3 3 trigger_changetarget named set_destination1, set_destination2, set_destination3 1 multi_manager to tie all the above to a coherent setup.
The multi_manager fires all trigger_changetargets in succession, one every 3 seconds.
When a trigger_changetarget (i.e set_destination2) is fired, it changes the destination of teleport_from_here to a new destination (destination2 in this example).
Since the player technically doesn't know when (or how often) the teleport is redirected to a new destination, entering the teleport results in a "random" destination.
The setup can be expanded to use more destinations, simply adding more info_teleport_destination with their corresponding trigger_changetarget.
There are also a number of meta-entities (appropriately hidden in the .rmf to avoid visual cluttering in Hammer) whose only purpose is to make the setup a bit more visual ingame.