CallClerk logo


CallClerk automatically manages and logs all your calls.


FireDaemon Pro. This allows you to start and run the script automatically when Windows boots and before login. FireDaemon Pro also allows you to start multiple instances of the application, monitoring them and automatically restarting those instances in the event they crash. FireDaemon Fusion can also be used to manage your CallClerk service, plus other Windows services via your web browser.


CallClerk Setup Under FireDaemon Pro


Step 1: Download CallClerk

  • Download and install CallClerk from here.


Step 2: Configure CallClerk

Manually run CallClerk and configure all the settings. In particular, on the "Misc" tab uncheck the 3 checkboxes in the "Startup" section.


CallClerk Settings

Step 2: Set Up CallClerk as a FireDaemon Pro Service

Download and install FireDaemon Pro. Double click the FireDaemon Pro icon on your desktop, then click on the New (i.e. +) button in the toolbar (or type Ctrl + N) to create a new service.:


FireDaemon Pro Example Service Program Tab


Next, click on the FireDaemon Pro Settings tab:


FireDaemon Pro CallClerk service settings

Enter appropriate values in the fields on the Settings tab as follows:

  • (Required) Logon Account: Enter the Windows account under which the application is to be run, e.g. the current user account. This must be the same account that was used to configure the settings.
  • Password / Confirm Password:  Enter the logon account's password twice.
  • (Optional) Interact with Desktop: Interact with Desktop: If this setting is enabled (default), the applications' output messages can be seen in the console window on Windows Session 0. To switch to Session 0, it may be necessary to install FireDaemon Zero and ZeroInput. Alternatively, this setting may be disabled, in which case the application's messages will be hidden.
  • (Optional) Priority: To allocate more CPU time to the application, select a higher scheduling priority in this field.
  • (Optional) CPU Bindings: To run the application on a specific CPU, specify the appropriate CPU in this field.

Next, click on the FireDaemon Pro Lifecycle tab:

FireDaemon Pro CallClerk Lifecycle tab

Change "Max Shutdown Delay" to 60000


Step 6: Verify that CallClerk is Running Correctly

CallClerk's status can easily be checked on the main FireDaemon Pro Services List - look for a Running Status value and a numeric Process ID (PID) value.


FireDaemon Pro Services list


If the service's Interact with Desktop setting is enabled, CallClerk status can also be verified by switching to Windows Session 0 to view CallClerk's messages.