đNote: This feature is available to Advanced users on Evo Everywhere, and to all users on Evo Enterprise. It is not available to Base users on Evo Everywhere, or to users on the Standard tier. If you are unsure of your user type or tier, see understanding Evo tiers.
The communications available to Researcher depend on the Evo Comms connector configuration and your permissions.
When communications build up, it can be difficult to separate genuine actions from updates, background information and messages that can wait. Evo Researcher can review the flow and give you a useful first pass over what needs attention first.
PeopleXD is the specialist context for this workflow, but it is not the limit of the use case. The aim is to review your wider business-as-usual (BAU) workload and turn communications into a short, source-linked action list in a few minutes.
Create the Manage My Comms project
Create a dedicated Evo Researcher project for this workflow. The project keeps the communications connector and the chats used to review your workload together.
Sign in to the Evo platform, click the Evo button, open the Products menu and select Evo Researcher. Open the projects dashboard.
Create a new project. Click + Create your first project, or + New Project if you already have projects.
Complete the Basics step. Set Project Name to Manage My Comms. Add a description such as: Review communications and organise PeopleXD and wider BAU actions. The project flow also shows Instructions, Uploads, Connectors, Actions and Collaborators; you can leave those for now.
Create the project. Click Create Project to open the workspace. If the guided flow takes you through the optional tabs first, continue to the Connectors step instead.
Open Connectors. In the project workspace, select the Connectors tab on the right-hand tab strip. It is represented by the plug icon.
Choose 3rd Party Connectors. This is the connector category that contains Evo Comms.
Search for Evo Comms. Use the search box and select Evo Comms.
Add and connect it. Click Add, then click Connect. This adds the connector to the Manage My Comms project and starts authorisation.
Authorise Microsoft 365. Sign in to the Microsoft 365 account you want Researcher to use and approve the requested access. You only need to complete this connection once.
Check the connection. Return to the project's Connectors tab and confirm Evo Comms is listed as connected. If the connector is present but not connected, select it and click Connect.
Start the first chat. Start a new chat in Manage My Comms and use the prompt below. The connector is now available for Researcher to search your communications.
Copy the prompt
Copy the prompt below into a new chat in the Manage My Comms project. Replace the text in square brackets with details from your own role and workload, and adjust the period covered when needed.
Using the Evo Comms connector, review my communications from the last [x] days and identify anything that requires action. I am a PeopleXD Administrator, but include both PeopleXD-related work and wider business-as-usual (BAU) tasks. Prioritise items based on urgency, customer or business impact, explicit deadlines, and whether someone is waiting for me to respond or take action. My manager is [manager name]. Highlight any messages from my manager in a separate section. One known priority is [known priority], due [deadline, date or meeting]. Identify any communications that support, affect or depend on this work. Group the results into: 1. Act first 2. Requests from my manager 3. Other PeopleXD tasks 4. Wider BAU tasks 5. Delegate, clarify or monitor 6. For information For each action, include the recommended next step, sender and subject, deadline or timeframe only if stated or clearly indicated, the reason for the priority, and a reference to the source communication. Do not invent deadlines, owners or actions. Call out anything ambiguous, duplicated or missing information.
What Researcher should return
The result should be a concise triage of your workload, not a summary of every message. Look for the following sections:
Act first â items with an immediate deadline, clear business or customer impact, or a dependency that could hold up other work.
Requests from my manager â messages from your manager, kept visible even where the requested action is not the most urgent item.
Other PeopleXD tasks â administration, reporting, support or data requests connected to PeopleXD.
Wider BAU tasks â customer actions, project work, meeting follow-ups, internal requests and other work outside PeopleXD.
Delegate, clarify or monitor â items that need more information, could be passed to someone else, or should be watched rather than acted on immediately.
For information â messages that do not currently require action.
Every recommended action should point back to its source communication. This makes it easier to check the context before you act and helps prevent an urgent-sounding message being treated as an urgent task without evidence.
Turn the result into a working list
Once you have reviewed the triage, ask Researcher to turn the useful items into a short plan you can work through:
Create a concise action plan from the items in Act first, Requests from my manager, Other PeopleXD tasks and wider BAU tasks. Keep only actions I need to own or progress. For each action include: - Priority: High, Medium or Low - Next step - Due date, if stated - Source message - Status: Not started, In progress or Waiting for information Put actions with no clear deadline into a separate Needs confirmation section. Do not merge different actions unless the source messages clearly refer to the same work.
You can then ask Researcher to produce the plan as a Word, Excel or other finished document, depending on how you want to manage the work.
Check the output before acting
Researcher gives you a fast, useful starting point. You still decide what to do and when. Check that:
The source message genuinely contains an action or request.
The deadline is stated in the source, rather than inferred from the tone of the message.
[known priority] has been linked to the correct communications.
Your manager's messages have been identified correctly.
Duplicate messages have not created duplicate actions.
Any missing owner, deadline or context is clearly marked for clarification.
Why this is not limited to PeopleXD
This workflow starts with a PeopleXD Administrator because the role has a clear operational context. However, the same approach can help with the wider work that fills the day:
Customer requests and follow-ups.
Internal project updates and actions.
Meeting follow-ups and decisions.
Requests from your manager or team.
Policy, process or operational communications.
Work that needs to be delegated, clarified or monitored.
PeopleXD may be your specialist area, but Evo Researcher can help you organise the wider BAU workload around it. That makes this a useful first project: the value is visible quickly, and the same prompt pattern can be reused whenever your communications start to build up.
đ¤Tip: After running the prompt, you should have a short list of what to do first, a separate view of your manager's requests, and a clear distinction between PeopleXD work and wider BAU actions. Once you have confirmed the first action, why not use Researcher to help you resolve it? It can investigate the source communications, draft a response, prepare a checklist or create a first version of the document you need.
Examples of follow-up prompts
Try prompts like these after the initial triage. Replace the square-bracket fields and check the result against the source communications before sending or acting on it.
Help me draft an email reply to my manager explaining the delay to [project or work item]. Use the source communications, keep the tone factual and professional, explain the current position, propose a realistic next step, and flag anything I need to confirm before sending.
Review the communications about [task or issue] and create a short action plan with the next step, owner and deadline. Use only details stated in the source messages and put anything unclear in a Needs confirmation section.
Draft a reply to [customer or colleague] about [request]. Summarise what has been agreed, answer what can be answered from the source messages, and list any points I need to confirm before sending.
Turn the information in these messages into a concise briefing note for [meeting or audience]. Include the current position, key risks, decisions needed and recommended next actions.
Create a checklist for completing [task]. Use the communications as the source of truth, separate confirmed steps from assumptions, and identify anything blocking progress.
Find the latest communications about [project or priority] and draft a status update for my manager. Include progress, delays, dependencies, risks and the next action.