If not for customers you would not have requests. So before entering any requests you may want to manually add or import customer information. Also, for those organizations that want to allow customers to submit requests the user in Membership Manager must have a corresponding customer record before he/she will be able to submit support requests. The screen shot below shows a grid of sample customers.
In the next screen shot I am adding a new Customer. Note that the Customer Name is required. The Customer Name should match the User Name in the Users Table in case you ever want customers to be able to login to add their own requests, or view requests that have been entered on their behalf by you or your staff. All other fields are optional.
In the next screen I have added more customer information.
In the next screen I have saved the new customer record and am viewing the record in Grid view. So far I have not added address information. In fact, many organizations will not even need to record address information. They may be using the program for only local users inside their organization.
However, other organizations may want to record address information and if so the program can automatically connect to Google and automatically do geo-coding so they can be displayed on a map. NOTE: You will need your own Map API Key but this should be free unless you have thousands of customers.
After saving this address information when switched to Map view with that single customer selected the pages looks like the below.
When the filter is removed and you have a some customers added or imported you might want to check out Chart View.
Now once a Customer has requests submitted (by staff or by the customer) a Customer Record will show related requests in a grid as in in the screen shot below.