AI & AGENTS · IN-ERP HELP DESK

The colleague who actually remembers how you configured this.

Answers 'how do I post a credit memo'-style questions inside the system, grounded in your setup, not a generic manual.

THE JOB

The question gets answered where it was asked.

Not in a ticket queue three days later, inside the screen the user is stuck on.

1
A user hits a screen they don't recognise and gives up.Or does it wrong and finds out at month-end.
2
The question goes to Teams, then a ticket, then a queue.By the time it's answered, the moment's passed.
3
Whoever answers has to guess which customisations apply.Generic Microsoft documentation doesn't know about yours.
4
The same question gets asked every quarter by someone new.Nobody's tracking that it's the same question.

✓
Answers the question inside the system, on the spot.In plain language, not a support-ticket form.
✓
Grounded in your actual configuration.Your workflows, your field names, your approval chain.
✓
Walks the user through the exact steps for their setup.Not a generic tutorial written for a default install.
✓
Logs what gets asked and how often.Recurring confusion becomes a training fix, not a ticket backlog.

SCOPE

It's a memory aid grounded in your setup, not a second finance team.

1
In-app Q&A grounded in your D365 configuration.Workflows, approval chains, and field-level setup, not a generic manual.
2
Process guidance, the actual click-path for your setup."How do I post a credit memo" answered for your version of that screen.
3
Ticket-deflection reporting.What's being asked, how often, and by which role.
4
Read access to your configuration and documentation.Nothing else, it doesn't need write access to answer a question.

1
Make a transaction on the user's behalf.It explains the steps; the user still clicks them.
2
Change a workflow, permission, or setup.It describes configuration, it doesn't touch it.
3
Answer questions about data it hasn't been given access to.No access means no answer, not a guess.
4
Replace training for a genuinely new process.It's a memory aid for people who've already been shown once.

WHY IT MATTERS

Users who can't remember how to do something quietly stop trying, this attacks that directly.

In-context

answers appear on the screen where the user is stuck, not in a separate portal

Grounded

responses reference your actual configuration, not a generic Microsoft doc

Logged

every question becomes a data point on where training is actually needed

FAQ

Priced per engagement, based on user count and system scope, plus the Copilot Credits it consumes answering questions. We scope both before rollout.

It says so, and offers to raise a support ticket rather than guess at a process it can't verify against your configuration.

It absorbs the routine "how do I" questions so your help desk deals with the harder cases, it isn't meant to replace people for judgment calls.

Read-only access to configuration and documentation you grant it, scoped by role like everything else in the system.

It's grounded in your configuration from day one, so it's most useful exactly when new users need it most, right after go-live.

SEE IT WORK

We'll ground it in a sandbox of your configuration and let you try the questions that actually come up.

Watch it answer a real process question, grounded in a real setup.

→

Talk through how this fits your support model and rollout plan.

→