Deprecated: Return type of Requests_Cookie_Jar::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/www/users/datatvvwuz/wp-includes/Requests/Cookie/Jar.php on line 63 Deprecated: Return type of Requests_Cookie_Jar::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/www/users/datatvvwuz/wp-includes/Requests/Cookie/Jar.php on line 73 Deprecated: Return type of Requests_Cookie_Jar::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/www/users/datatvvwuz/wp-includes/Requests/Cookie/Jar.php on line 89 Deprecated: Return type of Requests_Cookie_Jar::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/www/users/datatvvwuz/wp-includes/Requests/Cookie/Jar.php on line 102 Deprecated: Return type of Requests_Cookie_Jar::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/www/users/datatvvwuz/wp-includes/Requests/Cookie/Jar.php on line 111 Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/www/users/datatvvwuz/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 40 Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/www/users/datatvvwuz/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 51 Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/www/users/datatvvwuz/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 68 Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/www/users/datatvvwuz/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 82 Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/www/users/datatvvwuz/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 91 How to access your List of Customers on DataTill – DataTill

1. How to access your List of Customers on DataTill

Introduction to datatill video:  https://youtu.be/FcOiEugWkcs

To find a list of your customers, you will need to go to “Customers” and then click on the “List Customers” option. 

Your next screen will consist of a list of all your customers.  Here you can search for the customer and open his or her profile. 

1.1. Viewing Additional information:

 If you are looking for specific details on the customer list – like the customer’s physical address or payment method – you can add it to the list by clicking on the “Show / Hide Columns” button.  

A drop-down menu will appear and here you can choose additional fields to add or fields that you want to remove.  All the options in blue, are options that you can currently view on your customer list.  To add or remove an option, just click on it.

* Should you leave the customer list and open it again later, you will see that the list has reverted back to the normal columns.  Should you wish to see the extra fields again, you will have to choose them again in the “Show / Hide” option.  

1.2. Filter functions:

The List Customers page offers cool search options that help you sort customers based on groups, billing, payment types, and more. To access these filters:

  1. Go to the List Customers screen.
  2. On the right side, you’ll see nine drop-down menus.
  3. Each menu acts as a filter.
Quick Tip: If you’re searching for specific customer and can’t locate them, make sure you’ve cleared all filters before reaching out to support for help.

Customer Groups:Select an option here if you only want to see customers in certain groups, for example, certain estates, contractors, High sites, No LOS Customers and so forth.
Billing Groups:This is used as an in-house monitoring system for processing debit orders.
  Payment Types:  Here you can view all customers that pay via Direct Debit (Debit Order), EFT, Credit Card or Cash.
Company / Individual:You can choose whether you only want to view individual customers or if you only want to view companies.
Normal / Prepaid   Customers:Some WISPS have customers that work on a pre-paid concept similar to Vodacom or MTN airtime.

Verified / Not Verified:
During the migration process, this can be used to mark customers whose details, radius account and billing have been checked.  This is only necessary if you plan to check each customer individually.
All / Suspended Customers:Here you can choose to view all customers or if you want to follow up on debt collection customers, you can choose to only see a list of all suspended customers.
All / VIP Customers:To view a list of all customers marked as VIP, you can use this drop-down menu.  VIP customers are usually high paying customers.

Normal / Deleted Accounts:
During the migration process, human error combined with a new system tends to cause confusion and small errors like duplicated accounts.  This will be the only time your financial manager is allowed to delete an account.