Skip to main content
Version: 2026.10.0

Receiving Recommendations

The Sales Executive can store a visit frequency in the supervisor record of the companies they supervise. Based on this, the system recommends visits.

Two screenshots are displayed one above the other. The upper screenshot shows the "Supervisor" tab in the Context "Company". In the "Supervisor" area, two supervisor records are captured. The supervisor record of Melanie Hueber with the visit frequency "Semi-annually" is outlined. An arrow points down from the outlined supervisor record to the second screenshot, which shows the visit records with supervisor "Melanie Hueber" and status "Recommended" in the Context "Visit".

Storing a Visit Frequency to Receive Recommendations​

A visit frequency can be stored in the supervisor record of a company (weekly, monthly, quarterly, semi-annually or annually) so that the system automatically recommends visits and ensures that companies are visited regularly where required. The field may also remain empty if no automatic recommendations are wanted for a company.

If a visit frequency is stored, the system checks whether a future visit record already exists for the company with the respective supervisor:

  • If this is the case, no new visit is recommended.
  • If this is not the case, the system automatically creates a visit with the status "Recommended".
    • The date of the last visit plus the visit frequency is used as the date of the next visit. If the calculated date of the next visit falls on a weekend, it is moved to a weekday.
    • If there is no previous visit record of the supervisor in connection with the company, today's date plus the visit frequency is used instead to calculate the first visit record. If the calculated date of the next visit falls on a weekend, it is moved to a weekday.
Note

The "Visit Frequency" field can also be maintained in the supervisor record in the district.

📖→ Further information on districts can be found here.

System Setting

For visits with the status "Recommended" to be created according to the logic described here, the server process "createVisitRecommendations_serverProcess" must be running.