Managing Orders For Prox Cards/Process

We get the occasional request for access control cards from clients for systems we did not install. Usually I can figure out the type of card but as we grow, this is a time consuming process for me, and I would like to have my office staff do it. Also as we expand more and more into access control, this request will come more and more.

For new installs, we log the part # and card range, so reorders on those is not an issue.

I am thinking once we touch a system, we should log the card range (card #'s issued), format, part # etc so if they call, we know what they need.

How do you train your office staff to get the right information? Or do you just have a technician get involved and double check everything?

Login to read this IPVM discussion.
Why do I need to log in?
IPVM conducts unique testing and research funded by member's payments enabling us to offer the most independent, accurate and in-depth information.

** *** **** * test ***** ** *** office, **** **** **** send *** * **** in *** **** *** decoding. * *** * technician **** ******* ** could *** ** **** and ****** * ********'* card ** *** **** bench, ** ******* ** took *** ** ***** to ****** *** *** format, *** **** ***** have ***** *** ****** test ***** **-** *******. Part ** *** ** hours *** ** ******* truck **** ** *** site ** ******* ** add ** **** *** system *** **** ** could *** ****** ** out ** **** *** card ****. ** **** case *** ******** ****** wanted ** *** *** 'buildings ****' (****** *** Bit) **** ***** ******. Now * ***'* *** here *** ***** ***** what *** *********** **, but **** **** *** stuck *** **** ***** with ** ****** ** I **** ***** **. The **** *** ** the ***** *****, ** called *** ******* * ******** *** ****** *** and *** ****** *** yes ******* ** ***** not **** ** ***** he *** ******** *** time ** ** ** return...I *** ** **** you.

*** ** *** ******** allows *** ** ****** into *** ******, * would ** **** *****. If ** ** ***** to **** **** **** to ******** **** **** them **** ** **. 1,2 **** ******* *** no *********** ******* *** service ******* ** ******* manager....* *** ****** ** out ***** *'* ***** onsite.*** ***** *********** **** can ** **** **** do **, ***** ** no ***** *** *****, the ****** *********** **** do **** *** *** attempting ** ** *** log ********** *** * potential ****** *****.

********, * **** **** all *****, ****** **** to ** ****. ******* in *** ***** ** can ** ***% ******* cloud *********** ***** * phone ** ***** ***** ID (**** ****). ***** ever ***** *****.

** ********* *** ****** 32 *** *** *** K32 (***** *******), **** are ****-**** ******* **** a * ****** ***** can ***** *** $**.

*************, * ***'* *****/ know ** ** **** answer.

** *** *** **** an ******* ****, *** can ***** ********* ***** format ** ** ***** on * (*******) **** reader *** **********, *** even **** ** *** take * **** **** and *** *** ** possible (**: ** *** system **** * ****** key).

******* *** **** ******** is ** ******** **** access ** *** ********** system *** ***** **** to *** ****** **** which ******/ ******** **** is ******.

** ***** *** *** card ****** ** **** it **** ** ****** out ********* **** ****. It's ******** ** ** can **** ** ****** easily.

*** ****'* ****** *****, care ** ***** * little ** *** *** built **?

** *** ****** ******** it, ***** **** ** these ****, ** **** started ***** **** *** HID ** *** ******. There ***'* * ******** code *** **** ******* the **** *******. **** takes *** *** **** out ** ******* ***** of **** *** ********* have.

******, ******* -- **** common ***** **** ** recommend *** *********.

************, **'* ***'* "******" format. ** ********** **** there **** ***** ** a ********* **** ******* by ***, *** ** takes *** "**********" ****** out ** *** ******** altogether.

***** *** ******** *** the *** *** *** the *********** *** **** is ** *** *****. As *** ******** *** tracking, * **** *** a ***********. ***** *** learn ** *** *** the ******* *** *** customer ******** **** *** have **** ***********. *** first ***** * ** is *** ** **** have *** *** *** to **** * ***** of *** ***** *** of *** **** ** a ****. ** ** is ** *** **** card *** *** *** the ******* **** *** (plus ** *** ********* their ******** *** *** identify **** ** *** information). *** **** **** is ******* *** **** number ******* ***********. *****, this ******** *** ******** to **** *** ** look ** ***** ****** or * ********** ** login *** ********* ***** they *** ** (**** what **** **** **** on *** *****).