EMAIL AGENT

Email Is Easyto Send.Make It Easierto Solve.

Employees already email support. Make those messages work for your team. The Email Agent automatically asks the right questions, guides employees through a fix when possible, and creates a fully triaged ticket when an analyst is needed.

Outlook email resolved by the Email Agent, with branches to Resolved in Email and Complete Ticket
SEE IT IN ACTION

What Happens After You Hit Send?

Follow a request from the first email through clarification, resolution, or a contextual handoff.

RESOLVED IN EMAIL

The Fix Happens in the Thread.

Not every emailed request needs an analyst. For missing work apps on a new iPhone, the Email Agent uses internal knowledge to guide the fix and confirm the outcome in the same thread.

Report the Issue
Describe the missing work apps in a familiar email.
Find the Right Guidance
Use internal knowledge to guide setup and app sync.
Confirm It Helped
Select “This resolved my issue” in the same email.
WORK IPHONE APPS. RESOLVED IN EMAIL.
01 / 03
FromEric Stevenson
ToLuma ServiceAide
Work iPhone shows no available apps

Hi,

I have just received a new work iPhone but cannot see any work-related Apps. How do I configure it.

Thanks,
Eric Stevenson

FromLuma Serviceaide
ToEric Stevenson
Re: Work iPhone shows no available apps

Hi Eric,

Based on what you described, here’s the most likely way to resolve it:

If this is a new work iPhone and no work apps are showing yet, the usual fix is to make sure the phone is enrolled in the mobile device management system and then connect it to Wi-Fi so it can sync.

Please try this:

1. Confirm the iPhone has completed its work device setup/enrollment.
2. Connect the phone to a reliable Wi-Fi network.
3. Leave it connected for a little while so the managed app sync can finish.
4. Refresh or recheck the app catalog/Home Screen afterward to see if the work apps appear.

Once the sync completes, your work apps should appear and either be available to install or install automatically, depending on policy.

If this fixes the issue, no further action is needed. If it doesn’t, reply to this email and we’ll continue from there with the right next steps.

Best regards, Serviceaide IT Support

Did this resolve your issue?
This resolved my issue
This did not resolve my issue
FromLuma ServiceAide
ToEric Stevenson
Re: Work iPhone shows no available apps
Did this resolve your issue?
This resolved my issue
This did not resolve my issue
Thanks! We're reviewing your details now and will follow up by email shortly.
Please open this message in Outlook to respond, or simply reply to this email.
Report the Issue
Eric reports missing work apps on his new iPhone.
Find the Right Guidance
Internal knowledge guides device setup and app sync.
Confirm It Helped
Eric selects “This resolved my issue” in email.
← Back
Next →
THE EMAIL AGENT DIFFERENCE

What Happens to a Vague Email?

“I’m having a problem with my laptop.” A ticket created from that email leaves an analyst asking what happened before work can begin.

Missing Information
An analyst must ask what happened before troubleshooting can start.
Clarifies the Request
Asks relevant follow-up questions within the email thread.
Every Email Becomes a Ticket
Even a straightforward issue enters the queue as a ticket.
Matches the Right Path
Offers step-by-step help or fulfills supported actions.
Context Lost in Handoffs
An analyst pieces together the issue from a slow email thread.
Brings the Full Story
Creates a fully triaged ticket with the employee’s answers and request context.
HOW IT WORKS

One Message. The Right Next Step.

The Email Agent works from the employee’s primary work email and keeps the request moving toward an answer, an approved action, or the right person.

Understand
Interprets the request and identifies what the employee needs.
Clarify
Collects specific missing details before work changes hands.
Resolve or Fulfill
Provides an answer or carries out supported workflows.
Track or Escalate
Creates a complete ticket or connects a human with the context.
MISSING INFORMATION

Get the Details Before the Queue.

A brief email should start the conversation—not a long chain of back-and-forth between an employee and an analyst.

Recognize What Is Missing
Identify the details needed to act on the request.
Ask a Focused Follow-Up
Keep the conversation in the familiar email channel.
Carry Context Forward
Preserve answers for resolution or the human handoff.
A SIMPLE EMAIL. A CLEAR WAY FORWARD.
01 / 05
FromEric Stevenson
ToLuma Serviceaide
Application very slow, CPU at 100% from mfetp.exe (McAfee) on a workstation

Hi,

One of our users' application has been responding slowly with delayed navigation and screen changes. Task Manager shows CPU pegged at 100%, and mfetp.exe (McAfee Threat Prevention Service) is using most of the CPU. It is a single Windows workstation and the slowness comes and goes. The machine is not down and it is not urgent; we would like to resolve it ourselves. What can we do?

Thanks,
Eric Stevenson

FromLuma Serviceaide
ToEric Stevenson
Application very slow, CPU at 100% from mfetp.exe (McAfee) on a workstation

To help us pinpoint the cause of the CPU spike, please provide these details.

Workstation hostname or asset tag
Locate this in system info or on a physical label.
McAfee endpoint product name and version
Find in the McAfee console About/version screen.
Engine/DAT/AMCore versions (if shown)
List these if visible in the McAfee console.
When does the CPU spike happen?
Choose the closest option or select 'Other (describe)':
Select an option
Name of specific application (if applicable)
If spike happens using a particular app, name it.
How long and how often do the spikes occur?
E.g., '10–15 minutes, a few times per day'.
Is a McAfee on-demand/full scan shown as running (or in scan history)?
Check McAfee interface or scan history.
Select an option
FromLuma Serviceaide
ToEric Stevenson
Application very slow, CPU at 100% from mfetp.exe (McAfee) on a workstation

To help us pinpoint the cause of the CPU spike, please provide these details.

Workstation hostname or asset tag
WIN-HR-0427
McAfee endpoint product name and version
McAfee Endpoint Security (ENS) 10.7.0
Engine/DAT/AMCore versions (if shown)
AMCore content 5700.xxxx, Engine 6700.xxxx
When does the CPU spike happen?
Choose the closest option or select 'Other (describe)':
When opening/using a specific application
Name of specific application (if applicable)
ClaimsPro (internal claims app)
How long and how often do the spikes occur?
About 10-15 minutes at a time, a few times per day, mostly mid-morning
FromLuma Serviceaide
ToEric Stevenson
Application very slow, CPU at 100% from mfetp.exe (McAfee) on a workstation

Hi Eric,

It sounds like the slowness is being caused by the McAfee Threat Prevention Service (mfetp.exe) pegging the CPU.

Self-service checks to try

1. Confirm it’s happening right now: when you notice slowness, open Task Manager and verify mfetp.exe is the process driving CPU to ~100%.
2. Restart the workstation: this often clears a temporary/stuck background scan and brings CPU back down. After reboot, re-test the application and confirm navigation/screen changes are responsive again.
3. If it returns, apply the vendor-recommended McAfee/endpoint protection update: repeated high CPU from mfetp.exe is commonly addressed by updating the endpoint protection client/engine. After updating, reboot and monitor to see if mfetp.exe CPU usage normalizes.

Expected outcome

After the reboot (and especially after any McAfee update), CPU should stop staying pinned at 100% and the application should respond normally instead of lagging intermittently.

If this fixes the issue, no further action is needed. If it doesn’t, reply to this email and we’ll continue from there with the right next steps.

Best regards,
ServiceAide IT Support

Did this resolve your issue?
This resolved my issue
This did not resolve my issue
Please open this message in Outlook to respond, or simply reply to this email.
FromLuma Serviceaide
ToEric Stevenson
Application very slow, CPU at 100% from mfetp.exe (McAfee) on a workstation

Hi Eric,

Thanks for the additional detail. I’ve created support incident IR-0000053 for your request: WIN-HR-0427: mfetp.exe (McAfee ENS 10.7) high CPU during ClaimsPro use; scans running. The issue has been captured and routed for follow-up, and our support team will continue from here.

Best regards,
ServiceAide IT Support

From: Eric Stevenson
To: Luma Serviceaide
Subject: Re: Application very slow, CPU at 100% from mfetp.exe (McAfee) on a workstation

additional_details: Already rebooted and updated McAfee; no change. Only this one workstation is affected, no recent software changes. The spike lines up with opening ClaimsPro.
application_name: ClaimsPro (internal claims app)
cpu_spike_timing: When opening/using a specific application
hostname_or_asset_tag: WIN-HR-0427
mcafee_engine_versions: AMCore content 5700.xxxx, Engine 6700.xxxx
mcafee_product_name: McAfee Endpoint Security (ENS) 10.7.0
on_demand_scan_running: Yes
spike_duration_and_frequency: About 10-15 minutes at a time, a few times per day, mostly mid-morning
top_cpu_processes: ClaimsPro.exe ~12%, chrome.exe ~6%, System ~5% (mfetp.exe is the top at ~70–80%)

Report the Issue
Eric reports application lag and high CPU on one workstation.
Ask for the Missing Details
The agent uses internal knowledge to ask focused questions.
Capture Eric’s Answers
Workstation, app, timing, and scan details stay in the thread.
Guide Troubleshooting
Clear checks help Eric try the fix before a handoff.
Create a Ticket with Context
The incident includes the answers and steps already tried.
← Back
Next →
AFTER THE HANDOFF

Support Gets the Full Story. Employees Stay in the Loop.

When a request needs an analyst, the Email Agent submits a ticket with the details already gathered. Employees can check progress from their email thread or Microsoft Teams.

REQUEST HISTORY
The Original Request Stays in View.
The conversation record keeps what the employee asked visible to support, alongside the details gathered before the analyst takes over.
CONTEXTUAL HANDOFF
A Complete Ticket for Support
The original email and collected details move together, so an analyst can pick up the request without starting over.
FOLLOW-UP
Status in Email or Teams
Employees can ask for an update in the email thread or check the ticket and next actions in Microsoft Teams.
For Employees

Ask for help through a familiar channel, then continue working with a clear next step for the request.

For Analysts

Spend less time piecing together the basics and more time on the work that needs human expertise.

Support lead with Permissions and Response Guidance controls
HUMAN OVERSIGHT

Support Stays in Your Team’s Hands.

Set the paths the Email Agent can take. Keep people involved where decisions, exceptions, or judgment call for them.

Supported Actions
Fulfillment follows the workflows your team makes available.
Context Preserved
The request history travels with a tracked or escalated case.
People Make the Call
Human support handles work that requires review or judgment.
SERVICE INSIGHT

Let Email Conversations Improve Support.

Questions and follow-ups show where employees need clearer answers, where request intake needs work, and which topics deserve attention.

Common Requests
See the themes employees ask about most often.
Missing Details
Notice which requests repeatedly need clarification.
Knowledge Opportunities
Spot answers or instructions that could be easier to find and use.
PRICING

One Familiar Channel.A Better Support Path.

Connect your employees’ work email to a more complete support experience.

BEFORE WE TALK

Your Questions.Clear Answers.

Do employees need a new portal to use Email Agent?

They can request help through their primary work email. The Email Agent responds in that familiar channel and can provide relevant check-ins or updates through email or Microsoft Teams.

Does every email become a ticket?

No. Routine requests may be answered or fulfilled when supported. A ticket can be created when formal tracking is needed.

What happens when a request is missing information?

The Email Agent can ask for the specific details needed, then carry those answers forward before an analyst becomes involved.

When does a person step in?

A human can take over when a request needs judgment, an exception, or direct support. The handoff includes the request and relevant context already gathered.

Can our team decide which actions are supported?

The experience follows the support paths and workflows your team makes available. We can discuss the fit for your environment in a consultation.

NEXT STEPS

Make Your Work Email a Better Path to Support.

Tell us how employees ask for help today. We’ll discuss how the Email Agent can clarify requests, handle routine work, and bring people in with the right context.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.