Enhancing Incident Management with SharePoint Ticketing

Visual representation of SharePoint ticketing system architecture

Intro

A robust incident management strategy is crucial for organizations aiming to maintain operational efficiency. With increasing reliance on technology, the need for an effective ticketing system becomes more apparent. A SharePoint-based ticketing system stands out due to its integrated framework, offering various advantages that enhance incident management processes. This article explores profound aspects of implementing such a system, providing valuable insights for decision-makers and IT professionals.

Software Category Overview

Definition and Importance

Incident management software is designed to assist organizations in managing IT incidents through systematic processes. It helps track, resolve, and report incidents efficiently. Business continuity relies heavily on minimizing downtime, and this software plays a pivotal role. Through automation and streamlined workflows, it allows teams to respond rapidly to issues, ensuring that critical services remain uninterrupted.

Key Characteristics

A SharePoint-based ticketing system embodies several key characteristics:

Integration with Existing Systems: Seamless compatibility with other SharePoint applications facilitates data sharing and collaboration.
User-Friendly Interface: An accessible and intuitive design simplifies ticket submission and updates for users at all competency levels.
Customizable Workflows: Organizations can tailor the ticketing process to suit their specific needs and operational intricacies.
Real-Time Reporting and Analytics: Ongoing performance metrics provide insights into incident trends and resolution times, assisting in strategic improvements.

Incorporating these features into incident management not only optimizes operations but also fosters a culture of responsiveness and accountability.

Comparative Analysis of Top Software Options

Feature Comparison

When choosing an incident management system, comparing features is vital. Key elements to evaluate include:

Ticket Tracking: The ability to easily track and prioritize incidents.
Collaboration Tools: Integrated communication channels among teams.
Knowledge Base: A repository of solutions and FAQs to assist users with recurring issues.

Each software solution may offer unique capabilities that warrant close examination based on organizational needs.

Pricing Models

Understanding the pricing structures of various ticketing systems is equally important. Costs can vary significantly depending on:

Subscription Plans: Monthly or annual fees that often depend on the number of users.
Per-Ticket Charges: Fees based on the volume of incidents managed.

Assessing costs against expected benefits ensures that organizations invest wisely in their incident management tools.

"Investing in the right incident management system not only enhances service delivery but also significantly reduces operational mishaps."

This article aims to address how a SharePoint-based solution can transform incident management, maximizing efficiency and improving overall service quality.

Prelude to SharePoint-Based Ticketing Systems

In an era where efficient incident management is crucial for operational success, SharePoint-based ticketing systems emerge as a strategic solution. By leveraging SharePoint’s capabilities, organizations can enhance their ability to manage incidents effectively. Ticketing systems are essential for tracking issues, managing requests, and maintaining communication between departments. They serve as a backbone for service delivery, ensuring that problems are resolved systematically and efficiently.

The use of SharePoint for ticketing not only streamlines processes but also improves collaboration among teams. It allows for centralized data management, enabling quick access to historical data. This is vital for decision-making, as it gives insight into patterns of incidents and areas that need improvement. Beyond just being a management tool, SharePoint can be customized to fit the specific needs of an organization. This ensures that the ticketing system aligns well with existing workflows, further enhancing productivity and user acceptance.

Understanding Ticketing Systems

Understanding the functionality and purpose of ticketing systems is essential for any organization wishing to optimize incident management. At their core, ticketing systems are designed to handle requests and incidents that arise within a business. They provide a structured way of logging issues, categorizing them for easier sorting, and assigning them to the appropriate personnel.

With ticketing systems, each issue is assigned a "ticket" that contains critical information, such as the description of the problem, priority level, and status updates. This organized approach ensures that nothing slips through the cracks. Furthermore, it enables teams to track their performance against service level agreements (SLAs).

Moreover, ticketing systems can improve communication with stakeholders by providing transparency. Users can see the status of their requests, and support teams can communicate directly through the ticket interface, avoiding unnecessary back-and-forth emails.

Overview of SharePoint Functionality

SharePoint’s functionality extends far beyond basic document management. It offers a robust platform for developing applications, including ticketing systems. One vital aspect of SharePoint is its ability to integrate with other Microsoft tools, which can enhance the ticketing experience. For instance, integrating Power Automate can automate workflows, reducing manual intervention.

SharePoint also allows for the creation of customized forms and workflows, which can adapt to the unique requirements of an organization. These forms can be designed to capture the necessary information for incident resolution accurately. Adjustments can be made without extensive coding knowledge, which simplifies the management process.

In addition, SharePoint provides comprehensive reporting tools. Users can generate reports to analyze ticket volume, response times, and customer satisfaction levels. This data is crucial for decision-making and for identifying areas that require improvement. Essentially, SharePoint allows organizations to manage their incident resolution efficiently while maintaining flexibility in how they operate.

Benefits of Using SharePoint for Ticketing

The implementation of a SharePoint-based ticketing system introduces numerous advantages that can significantly enhance incident management processes. This article will detail how these benefits create efficiencies that improve overall service delivery in an organization. By leveraging SharePoint’s inherent capabilities, companies can streamline their ticketing operations, leading to effective resolution of incidents and better resource allocation.

Centralized Data Management

One of the primary benefits of using SharePoint for ticketing is centralized data management. This format means all incident-related information is stored in one location, making it easy to access and manage. When incidents are logged, the data can include the issue description, assigned personnel, and priority levels. This can minimize confusion and ensure that everyone involved has accurate information. A centralized system also reduces the risks of information loss and fragmentation, common in traditional ticketing systems that rely on disparate platforms.

Dashboard interface showcasing ticket management features

There is also an opportunity for integration with other systems. SharePoint can pull and share data with various applications used within the organization. This creates a unified view that enhances team collaboration and ensures everyone has real-time updates.

Customizable Solutions

Another significant advantage is the customizable solutions that SharePoint offers. Organizations can tailor their ticketing system according to their specific needs. The flexibility in designing forms allows for fields that are relevant to various departments or projects. For instance, an IT department might prioritize technical issues differently than a human resources unit would prioritize personnel-related inquiries.

Customization extends to the user interface as well. Stakeholders can create dashboards that showcase critical metrics, which align with their organizational goals. By allowing users to modify the system as needed, organizations foster user engagement and satisfaction, which is vital for successful incident management.

Enhanced Reporting Capabilities

The enhanced reporting capabilities of SharePoint also contribute to improved incident management. Built-in tools enable organizations to generate detailed reports that highlight trends, patterns, and areas for improvement. For example, if reports reveal recurring issues, management can analyze the root causes and take corrective actions.

These insights are not just retrospective; they can inform future strategies and enable better decision-making. Companies can optimize performance by utilizing data-driven insights to allocate resources effectively. Understanding recurring issues helps to reduce response times and improve service delivery.

"By using SharePoint for ticketing, organizations are not just answering incidents; they are building a knowledge base that fuels future improvements."

In summary, the benefits of a SharePoint-based ticketing system go beyond mere convenience. Centralized data management ensures efficiency, customizable solutions promote user buy-in, and enhanced reporting capabilities drive organizational growth. These features help align incident management processes with business objectives, making it an invaluable tool for IT professionals and decision-makers.

Key Features of a SharePoint Ticketing System

In any incident management strategy, a ticketing system plays a crucial role. The effectiveness of this system can significantly influence the overall operations of an organization. A SharePoint-based ticketing system brings various key features that are essential for optimizing incident management. These features not only enhance user experience but also streamline workflows and improve response times. Understanding these elements allows businesses to leverage the full potential of SharePoint for their needs.

User-Friendly Interface

A user-friendly interface is one of the most critical features of a SharePoint ticketing system. This attribute ensures that both users and support staff can interact with the system seamlessly. An intuitive layout minimizes the learning curve and fosters quick adoption.

Consistent Layout: A clear and consistent design helps users navigate easily.
Search Functionality: Effective search tools allow users to find tickets or information without unnecessary delays.
Easy Access: Users can create, view, and manage tickets from a central dashboard without confusion.

Such characteristics enhance user satisfaction and promote efficient communication between IT teams and users.

Automated Notifications

Automated notifications are another critical feature in a SharePoint ticketing system. These serve to keep users informed about the status of their requests and updates on ongoing issues.

Prompt Alerts: Users receive timely alerts when their tickets are updated or resolved, reducing the need for follow-ups.
Escalation Notices: Notifications can also alert managers when a ticket requires their attention, ensuring nothing falls through the cracks.
Customizable Settings: Organizations can tailor notification settings based on their needs, ensuring relevant stakeholders are always in the loop.

The result is a system that not only improves user satisfaction but also enhances accountability and tracking processes.

Prioritization and Escalation Workflow

Effective incident management necessitates a robust prioritization and escalation workflow. SharePoint's functionality allows organizations to categorize tickets based on urgency and impact.

Custom Prioritization: Different criteria can be established. This helps support teams to focus on critical issues first.
Escalation Pathways: The system can automatically escalate unresolved issues to higher levels of support, timely addressing urgent requests.
Visual Indicators: Color-coding or icons can visually indicate ticket priority, simplifying management oversight.

This structured approach ensures that critical incidents receive the attention they deserve, increasing overall service efficiency and reducing downtime.

"A sound ticketing system doesn't just log issues; it orchestrates a finely-tuned workflow that prioritizes effectively."

Implementing these features leads to a more optimized incident management process, benefiting both users and IT staff alike. Each element — user interface, automated notifications, and prioritization workflows — contributes to a cohesive system that drives effective incident resolution. By leveraging these capabilities, organizations can expect to experience improved workflow efficiency and enhanced service outcomes.

Integrating SharePoint with Existing Systems

Integrating SharePoint with existing systems is a crucial aspect for optimizing incident management. This process not only ensures a smooth transition but also enhances the overall efficiency of the ticketing system. A well-planned integration allows organizations to leverage their current resources while minimizing disruptions during the implementation phase.

Understanding the existing systems in place is fundamental. Many businesses already have tools such as customer relationship management (CRM) systems, project management applications, or other ticketing solutions. By assessing these systems, organizations can identify what capabilities are needed and which features can be complementarily integrated into SharePoint. This analysis helps inform better decision-making and offers insights into potential limitations and opportunities for improvement.

Assessing Current Systems

Before integrating SharePoint, a comprehensive assessment of the current systems is necessary. This means reviewing the software in use, the workflows, and how they align with the new ticketing system. Evaluate the following:

Existing Software: Identify which applications are critical for daily operations. Determine their compatibility with SharePoint.
User Needs: Collect feedback from end-users on their experiences and challenges. This input can guide required changes during integration.
Data Complexity: Analyze the volume and complexity of the data involved. Understand data formats and transfer methods.

An effective assessment can reveal gaps in the existing infrastructure that SharePoint could fill, aligning processes with business goals more effectively.

Choosing Integration Methods

Choosing the right integration method is evidence of critical thinking and strategy. The method selected will vary based on factors such as the type of systems in use, the available resources, and desired outcomes. Common methods include:

APIs: Application Programming Interfaces enable seamless communication between SharePoint and external systems. This is often the most flexible option but requires technical expertise.
Third-Party Connectors: Some vendors provide tools specifically designed to link SharePoint with other applications. These can simplify the process greatly, though they may come with limitations.
Custom Solutions: For organizations with very specific needs, developing a custom integration might be necessary. This allows tailored workflows but can require significant investment and time.

Flowchart depicting streamlined incident management workflows

Make the choice based on a clear understanding of the business objectives and available technology.

Data Migration Strategies

Data migration is a vital step in the integration process. Effective migration ensures that information is accurately transferred from existing systems into SharePoint. Consider the following strategies:

Plan and Map Data: Begin with a thorough plan, mapping out what data needs to be moved and how. Prioritize datasets based on their importance to ongoing operations.
Testing Migrations: Conduct trial migrations. By testing with small data sets, you can identify issues and adjust your approach before full migration.
Continuous Monitoring: After the migration, keep an eye on the performance of data within SharePoint. This ensures that any potential issues are caught early, maintaining the integrity of incident management processes.

With effective integration, organizations can ensure that SharePoint supports rather than complicates existing workflows. Success in this area will yield significant benefits in incident management, enhancing both efficiency and user satisfaction.

Challenges in Implementing SharePoint Ticketing Systems

Implementing a SharePoint-based ticketing system is not without its challenges. While the advantages are substantial, understanding potential hurdles can make the integration more effective. Addressing these challenges ensures smoother transitions and improved outcomes for organizations. Failing to acknowledge these factors can lead to extensive disruptions and dissatisfaction among users.

User Training and Adaptation

User training is perhaps the most significant obstacle in the adoption of a SharePoint ticketing system. People often resist change, particularly when it requires learning a new system. The intricacies of the SharePoint interface may overwhelm some employees. To mitigate this issue, organizations should invest in comprehensive training programs. These sessions should cater to various user levels, ensuring everyone understands their roles in the ticketing process.

Additionally, adaptive learning techniques can prove beneficial. For instance, incorporating hands-on workshops and interactive tutorials allows users to familiarize themselves with the system easily. Gradually introducing features can also reduce the learning curve. Success hinges upon users feeling confident in utilizing the platform.

Technical Configuration Issues

Technical configuration issues often arise during the setup of the SharePoint ticketing system. These challenges can range from network connectivity problems to integration with existing tools. Often, the complexity of the SharePoint environment can complicate configurations.

To address these issues, organizations should conduct a thorough assessment prior to implementation. Evaluating existing IT infrastructure can highlight incompatibilities. Forming a technical support team specializing in SharePoint configurations also helps ensure a smoother transition. Continuous monitoring post-implementation is also essential. It allows the team to promptly address any technical glitches that may surface.

Maintaining Security Protocols

Maintaining security protocols is crucial, especially in an age where data breaches are rampant. SharePoint’s flexibility can pose risks if not appropriately managed. Organizations must ensure that sensitive information remains protected throughout the ticketing process.

Establishing user permission levels can help. By controlling who has access to specific data, organizations can significantly reduce the likelihood of data exposure. Regular audits are also essential. They can identify potential vulnerabilities within the system. Adhering to established regulations, such as GDPR, is not just a requirement but a best practice. Organizations must stay ahead of security threats by continually evolving their security strategies.

"The success of a SharePoint ticketing system hinges not just on its features, but on how well an organization prepares its users, technical infrastructure, and security measures."

Best Practices for Successful Implementation

Implementing a SharePoint-based ticketing system requires careful consideration of several best practices. These practices ensure that the system will not only function correctly but also meet the needs of the organization. By applying these strategies, organizations can maximize the benefits of their ticketing solutions.

Engaging Stakeholders

Engaging stakeholders effectively is fundamental for the successful deployment of any system, especially a ticketing system. Stakeholders encompass everyone who interacts with the system, from IT staff to end-users. Their input can shape the tickets' functionality, priority settings, and reporting structures. It is vital to involve them in the initial planning stages.

Key strategies for engaging stakeholders include:

Conducting surveys: Gather opinions and expectations from users about what they need from a ticketing system.
Holding workshops: Facilitate workshops where stakeholders can discuss their requirements and challenges.
Creating feedback loops: Establish mechanisms for ongoing feedback once the system is operational.

By actively involving key stakeholders, organizations can build a ticketing system that is aligned with their specific needs and expectations. This user-centered approach fosters buy-in, leading to smoother adoption and enhanced satisfaction.

Iterative Testing and Feedback

Iterative testing is crucial for refining a SharePoint ticketing system before its full-scale launch. This process involves testing system features in cycles, enabling teams to identify issues early on and make adjustments based on real user feedback.

Steps in the iterative testing process include:

Pilot testing: Run the system with a small group of users to gauge functionality and usability.
Collecting feedback: Utilize surveys or focus groups post-testing to gather insights from users regarding their experience.
Making adjustments: Analyze the feedback and make necessary changes to improve the system.

This continuous loop of testing and feedback allows organizations to perfect their implementation. It ensures that the system evolves according to the users' needs, ultimately resulting in a more effective ticketing solution.

Continuous Improvement

Continuous improvement is an ongoing commitment that involves regularly revisiting the ticketing system's performance. This practice is essential to adapt to changing organizational needs and technological advancements. By maintaining a focus on improvement, organizations can ensure their ticketing system remains relevant.

Some effective ways to promote continuous improvement include:

Regular audits: Assess system performance against established Key Performance Indicators (KPIs).
User training: Offer ongoing training sessions to keep users informed about new features and best practices.
Stakeholder reviews: Conduct periodic reviews with stakeholders to evaluate the system's effectiveness and gather suggestions for enhancements.

Investing in continuous improvement creates a culture of growth and responsiveness. Organizations can capitalize on feedback and emerging trends, driving the ticketing system toward optimal performance.

Real-World Applications of SharePoint Ticketing Systems

Performance metrics analysis related to service delivery

The practical use of SharePoint-based ticketing systems reveals their true potential within organizations. This section elucidates how these systems can be implemented across various sectors, showcasing specific applications and tangible benefits. The focus is on demonstrating how real-world applications improve incident management by streamlining processes, enhancing communication, and ensuring effective resolution of issues.

Case Studies

Several organizations have successfully adopted SharePoint-based ticketing systems and have shared their experiences, providing valuable insights into the implementation stage and operational efficacy. One notable example is a large healthcare provider that integrated SharePoint into its incident management workflow. The organization faced challenges with tracking and resolving IT issues in a timely manner. By using SharePoint, they established a centralized ticketing system that allowed seamless communication between staff and IT support teams.

The healthcare provider reported a significant reduction in response times. Tickets were categorized based on urgency, enabling appropriate prioritization. The interface was user-friendly, encouraging employees to report issues promptly. Staff feedback highlighted that the ability to track their ticket’s status fostered a sense of ownership and responsibility over problem resolution.

Another relevant case study comes from a financial services company. By utilizing SharePoint, they could automate notification processes for urgent tickets. This integration streamlined their communication and led to a marked improvement in service delivery. Adjustments made over time based on user feedback also enhanced the system’s functionality, demonstrating the adaptability of SharePoint systems in response to evolving needs.

Sector-Specific Implementations

The flexibility of SharePoint-based ticketing systems allows them to be tailored for various sectors. Each industry has unique requirements that can be addressed effectively. For example, educational institutions utilize these systems to manage student IT support requests. Here, SharePoint serves as a platform to manage incoming tickets from students and faculty, ensuring that issues are resolved swiftly. The system also offers comprehensive reporting features, enabling institutions to analyze common technical issues and proactively address recurring problems.

In the manufacturing sector, SharePoint can manage incidents related to equipment malfunction or operational delays. This ensures that issues are logged and addressed quickly, thus minimizing downtime. Integrating maintenance schedules with ticketing systems allows organizations to prioritize incidents based on their impact on production capabilities.

The versatility of SharePoint ticketing systems is not limited to these sectors. Many organizations across different fields report enhanced efficiency and improved collaboration due to the shared access to real-time information. The common thread across these implementations is the ability of SharePoint to facilitate better communication and a clearer workflow.

"Real-world applications of SharePoint ticketing systems show that tailored solutions can effectively resolve specific industry challenges, leading to better operational outcomes."

Measuring the Success of Ticketing Systems

Evaluating the effectiveness of ticketing systems is essential for organizations looking to enhance their incident management processes. SharePoint-based systems offer specific metrics that can provide insights into their performance. Focusing on the right criteria helps decision-makers understand how well the system addresses organizational needs. This evaluation leads to informed adjustments to optimize future operations.

Key Performance Indicators

Key Performance Indicators (KPIs) serve as the foundation for assessing the success of a ticketing system. Selecting relevant KPIs ensures a nuanced view of system performance. Some important KPIs to consider include:

Ticket Resolution Time: This measures the average time taken to resolve tickets. Shorter times indicate efficiency.
First Contact Resolution Rate: This KPI reflects the percentage of tickets resolved on the first interaction. Higher rates signify effective problem-solving capabilities.
User Satisfaction Scores: Collecting user feedback after ticket closure provides insights into satisfaction levels. This metric can guide user experience improvements.
Volume of Tickets: Analyzing the number of tickets generated can highlight trends in workload. It helps in capacity planning and resource allocation.

Tracking these KPIs can pinpoint strengths and weaknesses of the SharePoint ticketing system. They enable organizations to be proactive in managing issues and improving service delivery.

Feedback Collection Mechanisms

Feedback mechanisms should be integral to the ticketing system. They provide the data needed to refine processes and meet user expectations. Several methods exist to gather valuable input from users:

Post-Ticket Surveys: After resolving a ticket, sending out a brief survey can gather focused feedback. Questions might concern user satisfaction, ticket resolution effectiveness, and overall experience.
Focus Groups: Organizing discussions with users can uncover insights into the ticketing system's usability. These sessions encourage detailed feedback that surveys might miss.
Regular Check-Ins: Periodic follow-ups with users can help gauge long-term satisfaction and engagement with the ticketing system.

Receiving user feedback is critical for continuous improvement. Systems like SharePoint thrive when they adapt to the needs and preferences of their users. By understanding how to effectively collect and analyze feedback, organizations can foster a responsive approach.

"The effectiveness of a ticketing system hinges on how well it adapts to feedback from its users."

In summary, measuring success through KPIs and feedback collection mechanisms provides the data needed to make informed decisions. This approach not only enhances ticketing system performance but also aligns it more closely with the expectations of users.

Future Trends in Ticketing Solutions

Understanding future trends in ticketing solutions is essential for organizations aiming to streamline incident management effectively. In an ever-evolving digital landscape, staying informed about technological advancements can significantly impact the efficiency and effectiveness of support systems. As businesses continue to adapt to varying demands, integrating modern ticketing solutions becomes critical to maintaining a competitive edge.

Emerging Technologies

Emerging technologies are reshaping the landscape of ticketing systems, opening doors to innovative solutions that enhance user experience and improve incident management.

Artificial Intelligence: AI is increasingly utilized in ticketing systems, providing capabilities such as predictive analytics and natural language processing. By analyzing historical data, AI systems can predict potential incidents before they occur, allowing organizations to proactively address issues. Additionally, AI-driven chatbots can assist users in real-time, directing them to relevant solutions without human intervention.
Machine Learning: Automation of ticket categorization and prioritization is becoming common through machine learning. As users interact with the ticketing system, these algorithms learn from the input and improve the classification accuracy of incoming tickets. This efficiency helps in routing issues to appropriate teams faster.
Cloud Computing: The shift toward cloud-based solutions is evident in ticketing systems, allowing for greater flexibility in accessing ticket data remotely. A SharePoint-based ticketing system hosted in the cloud ensures that stakeholders can manage incidents from anywhere, promoting a responsive service delivery model.

"Emerging technologies like AI and cloud computing are crucial for optimizing incident management, enabling faster response times and better resource allocation."

The Role of Automation

Automation plays a pivotal role in modernizing ticketing systems, reducing the manual workload on teams and enhancing overall operational efficiency.

Automated Ticket Creation: Many ticketing systems can automatically create tickets from incoming emails or service requests. This minimizes delays in incident logging and ensures that all relevant data is captured immediately.
Self-Service Options: Organizations are adopting self-service portals where users can resolve simple issues without needing to contact support. With a well-structured knowledge base, users can access solutions quickly, further reducing the ticket volume for support teams.
Workflow Automation: Automation extends to the entire workflow of incident resolution. By setting predefined rules for ticket assignment, priority levels, and escalation protocols, teams can respond to incidents more effectively. For instance, urgent tickets can be automatically escalated to senior staff for immediate attention.

Finale

In any organization, efficient incident management is a cornerstone of maintaining service quality and operational integrity. This article has examined the merits of implementing a SharePoint-based ticketing system, emphasizing its capacity to enhance workflow, consolidate data, and streamline collaboration among teams. Transitioning to such a system is not merely a technological upgrade; it involves rethinking how incidents are managed and resolved.

Summary of Key Points

Centralized Management: A SharePoint system centralizes ticket tracking, making it easier to monitor progress and prioritize issues.
Customization: Users can tailor the system to fit their specific needs, creating workflows that mirror their internal processes.
Automation: Automated features reduce the time spent on manual entries and ensure that notifications are sent promptly.
Reporting and Analysis: Enhanced reporting capabilities facilitate data-driven decisions, highlighting trends and areas needing improvement.
Integration: The ability to integrate with existing systems allows for a seamless transition into the new ticketing structure, minimizing disruptions.
User Training: Adequate training helps teams adapt to the new tools, ensuring better resource utilization.

Final Thoughts on Implementation

Implementing a SharePoint-based ticketing system is an iterative process that requires careful planning and execution. Organizations must consider aspects such as user engagement, feedback loops, and continuous improvements. Failing to adequately address these elements may lead to underutilization of the system's capabilities. Evaluating performance through key performance indicators assists in determining success and areas to adjust. Ultimately, the goal is not just to install a new system but to cultivate a responsive and effective framework for managing incidents.

By adopting a SharePoint ticketing system, organizations position themselves to improve service delivery significantly. This systematic approach can aid decision-makers and IT professionals in building a robust incident management framework that meets their specific needs.

More Amazing Stuff:

A detailed overview of a property manager's duties in managing rental houses