Destination Dispatch

How to ensure the profiles we create in your access control system successfully trigger your Destination Dispatch system.

Andy Orwell avatar
Written by Andy Orwell
Updated over a week ago

Destination dispatch systems are typically already integrated with the access control system. To ensure this all flows smoothly when managing visitors, we can enter user profiles into the access control system in the way the DD system requires. This means that user profiles can contain the information required to trigger DD to take them to the required floor.

We achieve this via two methods - either may be used as required by your DD<>ACS integration.

Option 1 - Custom Access Levels

More info on custom access levels can be found in our "How we manage access" help article.

The same method can be used for destination dispatch. A multiple choice custom field named "Floor" (or similar, the name is defined by you) can be created in Proxyclick and the options included will be a list of each floor:

Once this is set up, the Proxyclick access control team can then map this custom field to create custom access levels. These access levels can then be set in the DD system so they will trigger DD to direct that user to the required elevator.

ℹ️ It's possible to use the above custom access level options for both DD triggering as well as allowing custom access for different visitor types. These features do not conflict.

Option 2 - Custom Field in User Profile

Similar to the above, this option uses the same custom field method. Instead of mapping this field to create custom access levels, we instead map it to the field in the access control system user profile (typically the home/default floor field) that is used to trigger DD.

Simply configure the custom field in Proxyclick then let us know the name of the field in your access control system that we should map this to.

Did this answer your question?