Introduction

WorkIQ is a game changer when you talk about collaboration and automation, in today’s business. WorkIQ just not empowers organizations with intelligent workflow automation, it actually simplifies approvals, routes tasks to the right people, and provides actionable insights in real time. By reducing manual effort and streamlining collaboration, WorkIQ helps teams operate with greater speed, accuracy, and efficiency, accentuating a high proficiency W.R.T. but not limited to

• Automates workflows → reduces manual effort with smart task routing

• Guides decisions → delivers real‑time, actionable insights

• Boosts collaboration → ensures the right people act at the right time

   

Imagine you have a general-purpose Agent, that caters to various requests like:

a. Finance requests: for loans, salary advances, settlements, per diem requests, etc.

b. HRMS requests: any request that needs to be handled by HRM team

c. IT request: any IT service request

d. Ethics and compliance issues

With WorkIQ in place, this collaboration has got very easy. Implement WorkIQ on your agent and let it route it to the correct department, let the decisions be taken easily, let the classifications be simplified. Let your agents understand all of it wisely and let it take up all the pain on your behalf.

Not sure of what I am saying? Here is a step-by-step example:

Prerequisites 

To make use of WorkIQ, you must enable the following and assign as a license to the necessary user/agentic account: Microsoft 365 Copilot

And in your PPAC >> Environment >> Settings >> Dataverse intelligence >> check the following settings are turned on, to let your agent interact with your Cowork MCP servers:

Teams and groups

And here are the teams that are created for the purposes described above:

These are all shared groups and is having one/more than one members, managers in them. Our agent should be able to recognize any incoming email that comes and be able to route it to the proper channel.

And here is a shared mailbox that our agentic flows is going to make use downstream:

The agent

For our demo purposes, I have kept an agent that is very easy to use, and that simply looks like the following:

Let me take out the instructions for you:

You are a general-purpose employee helper agent, who can seek permission from the respective departments and then proceed with subsequent steps:‌.

Please note the name of the requester in a variable: vRequester, and the email of the approver in a variable called vApprover.

a. In case of IT assets request, you need to prepare a word document , that must contain the following, that should contain the following fields:​ ‌<Include the requesting employee name>:

1. Name of the associate/requester: <vRequester>

2. The asset requested for: <Include the asset requested>

3. ETA for fullfillment ‌: <Include the date by which the request is needed to be fullfilled>

4. Comment​:‌ 

5. Signature​: 

b. In case of a travel request, you need to prepare a word document that should contain the following fields:​ ‌<Include the requesting employee name>

1. Name of the associate/requester: <vRequester>

2. Travel requisiton is for: <Include the reason for which the travel requisition is raised>

3. Destination: <The travelling location>

4. Travel date: <Proposed date of travel>

5. Comment​:‌

6. Signature‌:

In both the cases, Call the ApsaraIQ In flows to send the same as an email, you must be asking approver to fill it up, take a printout of the same, sign it and send as an attachment, mentioning that when they reply they must attach while approving. Upload the generated file into SharePoint site: General using the SharePoint MCP server.

Inputs to the flow should contain, the file URL (generated above), the approver = the approver of the respective team who would approve the request (vApprover), the subject = the gist of the activity that you carried out. It should be in an Email friendly format, and the Requester =the person who has requested for the approval (vRequester).

Send an acknowledgement to the sender, saying that the request has been received and would be reviewed and responded. This should be in an email friendly response (HTML).

C. Any ethics issue, you have to behave complascent with the user, understanding what's the matter, and send accross a notification to ethics team, by making use of WorkIQ MCP.​‌

Anything that is beyond the scope of these options, politely refrain from replying.​‌​‌​‌​‌​‌​‌​‌​‌​‌​‌​‌

And then in the tools I have added the following:

• SharePoint

• WorkIq 

• Word MCP server

The word MCP server is responsible for generating the attachment as explained above for reverting back with signature from the approver.

Calling the agent

To deal with the agent I am making use of two flows: 

When a new email arrives

I am triggering this flow as to whenever a new email arrives, and then it calls the Agent from here, wait for its response, gets the response and mounts it into an email:

Look at the call to the first agent:

This is where I am evaluating to whom this email be routed to, by making use of WorkIQ MCP server. And it splits up the input into three parts

Body = input to the agent

From = requester email (this will be set as requester variable in the agent, as per the instructions).

Approver = target mailbox (this will be set as the approver variable in the agent, as per the instructions)

Now let us look at the second agent for formatting:

• This will get the response from the previous step and there will be two parts of the response

• The part that sends the request to the proper team

• The part that sends acknowledgement to the sender/requester.

• This agent grabs the second component of the response and sends an email to the sender/requester:

Forwarding the request

An almost similar event happens when your agent calls a flow to process the forwarding of the requests to the correct channel:

When the agent calls the flow, it calls with the following input –

Hence, I needed another agent to decode the response into following parts:

1. The content of the main response of the agent: this contains the action to be conducted by the target team (sanction an advance payment/accept a leave/accept a service request for antivirus update).

2. To whom should this email go (recipient)

3. The requester details.

And hence my new agent is doing this:

And it generates the following outputs:

And rest part is very simple:

I am going to send the response as an email:

Demo

I am going to request a Bluetooth headset, as my old one is not working anymore:

It triggered the workflow >> to the agent >> to the Group email >> IT Approver:

If you open the link embedded, it will show you the word document generated (it used Word MCP server to generate it):

And then it sent me an acknowledgement, saying that:

This is expected as this gets called from the flow:

See how it evaluates the recipient, email body, subject line and the embedded link for the document.

Conclusion 

WorkIQ, when combined with Copilot Studio, ensures intelligent runtime evaluation — dynamically selecting the correct recipient through agentic decisioning. This synergy closes the loop on workflow automation, making approvals and task routing not only faster but context‑aware, so collaboration flows seamlessly from initiation to completion.

Talk to you soon, take care, love and namaste 😊