Before
The Hospitality Department manages about 60 residential complexes with 1000 residents. Two contact center operators received requests from them and company employees via email, a personal WhatsApp number, and from the receptionists of the residential complexes, who manually entered them into the task tracker. The tasks were assigned to Facility managers. This solution did not meet the Company’s growth strategy and digitalization and did not allow for the creating of an omnichannel contact center. In addition, it had the following limitations:
- If solving a resident's problem required creating several tasks, they were not linked. Only the operator knew they were related to the same problem.
- There was no integration with email. Requests had to be manually entered.
- The list of property owners and tenants was maintained manually by operators with no CRM integration.
- The list of residential complexes and real estate objects was also maintained manually in Excel.
Solution
Dynamics 365 for Customer Service was deployed in the existing Dynamics 365 environment:
- The Customer Service Hub app was configured for operators, and a simplified Team Member app was deployed for facility managers.
- Both apps added functionality that was present in the previous solution: co-executors and observers in tasks, comments, in-app and email notifications about new requests, the planned resolution date for the request, new comments, etc.
- Customer Service and Dynamics 365 for Sales, use a single Dataverse database. Data about residential complexes, real estate objects, and residents were not required to be integrated further.
- Developed integration with the mobile Community App for residents, allowing users to create requests, chat with the operator, attach files, and track the request status.
- Configured integration with the Hotline shared mailbox in Outlook for working with emails in the app and automatically creating requests.
- Requests are automatically created and assigned to the duty operator.
- Requests (from residents) and tasks (for executors) are separated. Now, a single request can create several tasks for different executors.
- Available out-of-the-box additional features for operators - knowledge base and AI-based similar request recommendations.
- Implemented access control with a role model and logging of changes made.