Skip to main content

Ideas Status Pipeline

Filter by idea status

Filter by product

8805 Ideas

Net Metering: A Smart Way to Save on Electricity BillsNew Idea

Net Metering: A Smart Way to Save on Electricity BillsWith rising electricity costs, many homeowners and businesses are looking for ways to reduce their energy expenses. Net metering is an excellent solution that allows consumers to generate their own electricity using solar panels and sell excess power back to the grid.What is Net Metering?Net metering is a billing system that enables consumers to offset their electricity bills by producing their own energy. If your solar panels generate more electricity than you consume, the surplus energy is fed into the national grid, and you receive credits on your bill.How Does Net Metering Work?Install Solar Panels – First, a solar power system is set up on your property. Generate Electricity – The panels convert sunlight into usable electricity. Use What You Need – The generated power is used for household or business needs. Send Excess Power to the Grid – Any surplus energy is sent to the grid through a bidirectional meter. Receive Bill Credits – The utility company credits your account for the extra electricity supplied.Benefits of Net Metering✅ Lower Electricity Bills – Save money by producing your own power.✅ Earn from Surplus Energy – Get credits for unused electricity.✅ Eco-Friendly Solution – Reduce your carbon footprint by using renewable energy.✅ Energy Independence – Less reliance on the power grid.How to Apply for Net Metering?If you're interested in applying for net metering in Pakistan, visit FESCO Net Metering to learn more about the process, eligibility criteria, and required documentation.By switching to net metering, you can enjoy long-term savings while contributing to a greener, more sustainable future. Start your journey toward energy independence today!

adbi
Apprentice
adbiApprentice

Analytics discrepancy: Tickets are credited to the assigned agent instead of the actual resolverNew Idea

Hello everyone,I am facing what appears to be either a reporting limitation or a process compliance issue within Freshservice Analytics.ScenarioLet's consider the following example:Ticket is assigned to Agent A. Agent A becomes unavailable (vacation, sickness, etc.). Agent B investigates the incident. Agent B performs the fix. Agent B changes the ticket status to Resolved. Agent B closes the ticket.The ticket activity log clearly records that Agent B performed the resolution action.Example:Agent B → Set Status as ResolvedHowever, the Analytics reports appear to attribute the resolved ticket to Agent A (the assigned agent) rather than Agent B (the actual resolver).Why this is problematicFrom an ITSM and operational KPI perspective, these are two completely different metrics:Ticket ownership Actual ticket resolution effortIn the example above:Metric Expected Result Ticket owner Agent A Ticket resolver Agent B If Analytics only reports against the assigned agent, then the productivity metrics become inaccurate.For example:Agent A may be absent for several days. Agent B resolves multiple tickets assigned to Agent A. Analytics still credits Agent A.This can significantly distort:Individual performance statistics Capacity planning Team workload analysis Operational reportingInvestigation performedI searched throughout Analytics:Standard reports Custom reports Custom metrics Custom attributesI was able to find:Agent Name Agent Group Name Resolved Date Closed DateBut I could not find any field such as:Resolved By Closed By Resolver Last Updated ByThe information clearly exists in the ticket activity log, yet it does not seem to be exposed for reporting purposes.Questions Is there currently a supported way to report on the actual agent who resolved a ticket rather than the assigned agent? Is there any Analytics dataset exposing: Resolved By Closed By Ticket Activity Author Audit/Event Owner Is this expected behavior by design? Has anyone implemented a workaround that remains ITIL-aligned and preserves accurate technician productivity metrics? FeedbackMy concern is that Freshservice currently allows an agent other than the assignee to resolve a ticket (which is operationally correct), but Analytics may not provide a reliable way to measure who actually performed the resolution.This creates a potential mismatch between operational reality and reporting reality.I would be very interested in hearing how other ITSM teams handle this situation.Thank you.