Normally Megadialer automatically optimises the order in which contacts are called for you, based on a range of factors. But if you put something inside that field then contacts will be called exactly in the alphabetical order of the value in that field, otherwise if you leave that field empty there will be no change in how Megadialer behaves.

You are in full control. That means that other prioritisation or dialing rules do not affect the contacts with $call_order. Only the absolute restrictions of the dialing attempts (call limitation in "total") and the approx. 20 minutes dialing interval apply.

After each call attempt the field will be emptied by default, but you are free to set a new value inside the onUpdate function of the call task script tab. That way you can fully overwrite the built-in call prioritisation by your own scheme.

Using a timestamp in $call order

You can optionally add a timestamp to the value with the hash sign as separator to postpone the dialing of that contact until that time is reached.

The time stamp format for the $call_order field follows the same format as all other date fields in Megadialer:

For example 2019-10-29T06:30:28.851Z ----> Date - T - Time (UTC 0) - Z

Don't forget to enter a T after the date and before the hour, and a Z after the milliseconds.

The records are sorted alphabetically. So you have to make sure that the order values (value before #) are equal.

A sample value for the $call_order field with date can be: A#2019-10-29T06:30:28.851Z in this case the lead must not be called before 2019-10-29T06:30:28.851Z.

The processing order of the available leads is: 

available automatic follow-ups > available contacts with $call_order > available contacts.

Typical use cases:

Call fresh leads in the order they were created:

Simply put the creation timestamp inside $call_order and the calls will go out exactly in the order the leads came in.

Enforce that any available A-lead is called before any B-lead:

Put the lead priority “A” or “B” inside the field, followed by a hash sign, followed by a timestamp at which at earliest this contact is allowed to be called again.

In combination with timestamp the system supports the use of up to 10 priority levels.

How does $call_order prioritisation relate to other contacts in the system?

The dialer will look for dial-able contacts in the following order:

  1. the first call attempt for a scheduled callback that has just become due
  2. any contact with the field $call_order filled that does not violate the minimum call interval of 20 minutes and does not have a timestamp set or for which the timestamp has been reached
  3. any other contact which is chosen based on the built-in prioritisation

For any further assistance please contact us at