The Portal service desk now triages email and tracks SLAs

What shipped

The service desk in the InsurEco Portal picked up four changes in the Portal deploys of 2026-10-08:

• Email intake. The service desk now routes email that arrives from Gmail and from relay forwarding.
• Triage and assignment. Incoming tickets are triaged and assigned into queues.
• SLA tracking. The desk tracks first-response time and resolution time for each ticket.
• A new report. Support activity can be filtered and exported to CSV.

The result is that a support team can take requests in, put them in front of the right people, and measure how quickly it answered and closed them, all inside the Portal. No separate helpdesk tool is required for that loop.

The change log entry is here: Portal deploys (2026-10-08).

Why this matters for insurance operations

Most support work in an agency, an MGA or a carrier operations team still starts as an email. A producer asks about a policy change. A partner asks why a file has not moved. A colleague forwards a thread and asks someone to pick it up. When that email sits in a shared inbox, three things tend to go wrong:

1. Nobody is clearly responsible for it.
2. Nobody can say how long it has been waiting.
3. Nobody can report, after the fact, how the team performed.

The new service desk addresses each of those directly. Email becomes a ticket. A ticket lands in a queue and gets an assignee. The clock on first response and resolution runs from the moment the ticket exists, and the report shows the result.

That is the same principle InsurEco applies to insurance data: every record has an owner, and what happens to it is visible. A support request is a small record, but it deserves the same treatment. If someone asked for help, someone should own the answer, and the team should be able to see whether it was given.

How email gets in

The service desk accepts email from two paths:

• Gmail. Teams that run their support address on Gmail can route that mail into the service desk.
• Relay forwarding. Teams that use a different mail setup can forward mail through a relay into the desk.

Either way, the starting point is the mail your customers and colleagues already send. Nobody has to learn a new form or portal to ask for help. The intake work happens on your side.

How tickets are triaged and assigned

Once a message arrives, the service desk triages it and assigns it into a queue. Queues let a team split work the way it is actually organised, so requests reach the people who handle them rather than waiting in one undifferentiated pile.

For an operations lead, the practical value is that ownership is explicit. A ticket in a queue with an assignee has a name on it. When someone asks "who is dealing with this?", the answer is in the Portal, not in someone's memory.

What the SLA tracking measures

The desk tracks two times:

• First-response time: how long it took for the requester to get an initial reply.
• Resolution time: how long it took for the ticket to be closed out.

These are the two numbers most support teams are asked about, and the two numbers most often estimated rather than measured. First response tells you whether people feel heard. Resolution tells you whether the problem actually went away. Tracking both separately matters, because a team can reply quickly and still leave issues open for a long time, or the reverse.

With both times recorded per ticket, a team can stop arguing from impressions and start working from its own data.

The new report: filters and CSV export

The new report brings that data together. Two capabilities shipped with it:

• Filters, so a team can narrow the view to the slice it cares about rather than reading every ticket at once.
• CSV export, so the data can leave the Portal in a plain, portable format.

CSV export is worth calling out. It means a support lead can take the numbers into whatever they already use for reporting, share them with management, or keep them alongside other operational records. The team's performance data is not locked inside the tool that produced it. That is a small, concrete example of the transparency we think insurance data should have by default: if the data is about your work, you should be able to see it and take it with you.

Who this is for

• Agency owners who handle client and producer questions through a shared inbox and want each one to have an owner and a clock.
• MGAs coordinating requests across underwriting, operations and partners, who need queues that match how the work is divided.
• Carrier and reinsurance operations teams who are asked to report on response and resolution performance and would rather export real numbers than assemble them by hand.

In each case the point is the same: one place to receive requests, assign them and measure the outcome, without adding another system to the stack.

What does not change

The service desk is part of the Portal. It does not ask requesters to change how they reach you; they keep sending email. It does not ask your team to adopt a separate helpdesk product to get queues and SLA reporting. And it does not hide the results: the report and its CSV export are there for the team to use.

Getting started

If your team already works in the InsurEco Portal, the service desk changes are live as of the 2026-10-08 deploy. A sensible first step is to route your support mail in through Gmail or relay forwarding, set up queues that match how your team divides work, and let a week of tickets run through. Then open the report, filter to the period you care about, and look at first-response and resolution times. Export the CSV if you want to share it.

That gives you a baseline built from your own tickets. From there, you can decide what to improve, and you will be able to see whether it worked.

Read this post online: https://blog.insureco.io/blog/idea-insureco-2026-w42-2