Mailbox part 1

Mailbox part 2

Working hours

Holidays and holidays

escalation

1. The escalation stage 1 defines the desired maximum reaction time (within the entered working times) between the lead input and reaction/response of the seller.
2. Reminder VK defines the period of a reminder of the seller before the expiry of escalation stage 1 .
3. The escalation stage 2 defines the period between the escalation of a request to the seller and the information/escalation to a supervisor.
4. The escalation stage 2 for resubmissions defines the period between the escalation of a request to the seller and the information/escalation to a supervisor.
   

1. Only escalation stage 1 refers to the entered opening hours. All other times are valid throughout - including Sundays and public holidays.
2. Information e-mails to users / supervisors will only be sent within the entered opening hours.
   

Configuration

1. Email From Name = Which name should be displayed when emails are sent?
   
2. How to display the name of users in the LMS overview / search
3. Distribute requests from existing contacts (who do not have an open request) normally = follow-up requests of known interested parties go outside the set up distribution to the assigned user of the interested party. If the checkbox is set, follow-up requests run into normal distribution.
   
4. Marketplace email redirects can be set separately from the general redirects
5. Trade-in CC E-Mail: To which email address should take-in requests be forwarded without vehicle reference? If forwarding takes place, core data of the payment will be attached to the forwarded e-mail via PDF. The full data can only be seen in the car manager, so the PDF contains corresponding links.
6. Fallback user: If a request cannot be assigned regularly, it is assigned to this defined user.
7. E-mail new unassigned request: For incoming e-mail from which leads cannot be generated, information is sent to the entered e-mail address.
8. Mailserver = Which email server is used (usually always mail server from pixelconcept)
9. Mailbox = Which email address is used (and must be entered on exchanges for requests to run into the LMS). Usually the set @dein.auto email address
10. Send emails: NO = no emails are sent outside. YES: Emails are sent outside
11. Lead tracking: YES = emails can only be viewed in the LMS. NO: Emails can be edited / answered via the LMS.
    
12. Use vehicle location for distribution: If this option is activated, leads are moved to the inbox of the vehicle location - settings e.g. to the autoresponder from this location, for example.
13. Consider opening hours when re-submission: NO = reminders / escalations also occur outside opening hours YES = reminders / escalations only take place within opening hours
14. Use vehicle location for forwarding rules: If this option is enabled, the vehicle site forwarding rules are used.
    
15. The change from lead tracking to car manager lead management can only be done through pixelconcept. Please take youContactup.

Pool solution

1. Even with a pool solution / a pool user, a supervisor setting should be made in order to be able to respond to requests that have been stopped.
2. In a pool solution, all users are automatically assigned the requests can access to requests in the pool account and can assign them to themselves to answer. A notification of the users does not take place unless this is entered / activated by the user management via the user management.
3. A pool solution cannot be combined with distribution groups.
4. For a pool solution, the checkbox "Receives requests" checkbox must not be activated for any other user, otherwise the requests will be distributed rolling between the pool user and the sellers with activated checkbox.

Users

1. User "receives requests" = If checkbox is set (and the user is not absent), the user receives requests rolling requests.
2. User "can be assigned requests" = If checkbox is set, the user can be assigned requests (or drag requests from the pool when pool solution is activated).
3. Checkboxes can also be done via theUser managementper user set per user.
4. Distribution groups = Here the distribution groups active for a user are listed. The change is only possible via the user management of the respective user. Distribution groups are created by pixelconcept - please take if you are interestedContactup.

1. At this point, it can be clearly checked how the request distribution is set up in the abbreviation / location.
   
2. We recommend not setting up solo distributions (e.g. Sales Manager receives all requests and then manually redistribute, or depositing only one user in a distribution group), as this leads to difficulties. In the absence of these persons - even with registered representatives - no user is entitled to accept inquiries, corresponding inquiries go to the administrator account in this constellation.