When a contact asks for a time, Lumez helps the team organize the conversation, who is responsible, and the history. Confirmation of the appointment, availability and resources remain in the agenda or in the specific product adopted by the company.
Classify the conversation and define someone responsible
Use a tag to distinguish requests for information, new contacts and pending returns. Then assign the conversation to the person who can look at the official agenda and respond.
Classification organizes the service queue, but does not reserve or confirm a time.
Record context without duplicating data
An internal note may indicate that the conversation is awaiting consultation on another product. The rest remains in history. Avoid repeating personal or sensitive data unnecessarily.
- Reason for contact.
- Person responsible for return.
- System in which availability will be checked.
- Response deadline informed to the contact.
Confirm the appointment in the calendar product
Consult and record availability, reservation, changes and cancellations in the calendar system adopted by the company. These features are not part of the Lumez contacts and conversations plan.
After the decision, return to the conversation to communicate the result and maintain the service history.
Review conversations awaiting feedback
Look for conversations that are not responsible or are still awaiting a response from the team. The review must result in clear contact, not a parallel agenda within Lumez.