Evo Copilot and Feed are features that enhance Access Care Planning within the Evo platform. Copilot uses AI to provide intelligent insights from your care data, while Feed delivers real-time notifications to help care teams work more efficiently.
Evo Copilot
Evo Copilot is an AI-powered assistant that helps care coordinators, registered managers, and care staff quickly access and understand critical care information.
Using natural language processing, Copilot answers questions about your care data in real-time, helping you prepare for visits, identify compliance risks, and quickly understand service user history.
Evo Skills are plugins that enable you to query your live database and provide insights. Access Care Planning uses the Care Planning Evo Skill to access your ACP data.
Key Capabilities
Pre-Visit Preparation: Quickly summarise recent visit notes and activities before attending a service user visit.
Risk & Compliance Monitoring: Identify visit notes containing high-risk terms (falls, medication issues, neglect concerns, harm indicators).
Activity Summaries: Review completed and outstanding activities for service users.
Care History Insights: Get concise overviews of recent care interactions and patterns.
Who Can Use Copilot?
Care Coordinators: Prepare for visits and review service user history.
Registered Managers: Monitor compliance risks and review flagged notes.
Nurse / Senior Carers: Identify staff-related risks and care patterns.
Business Owners: Analyse branch-level risk patterns and compliance trends.
Evo Feed
Evo Feed surfaces notifications and alerts from Access Care Planning directly within the Evo platform.
Feed provides a centralised view of ACP-generated notifications alongside other Access products, enabling care teams to act on critical updates within a shared workspace without needing to run reports or check multiple systems.
Feed integrates with two ACP modules:
Automation Engine: Configure automation rules to send custom Feed notifications using the "Send Evo Feed Item" action.
Alert Notifications: Missed visit alerts can be configured to appear in Feed (Branch Administrator users only).
Key Features
Automation Integration: Configure ACP automation rules to send notifications to Evo Feed using the "Send Evo Feed Item" action.
Real-Time Alerts: Receive immediate notifications for events configured in your automation rules.
Customizable Notifications: Define notification title and body content within Evo's formatting constraints.
Cross-Product Integration: View ACP alerts alongside notifications from other Access products you use.
Branch Admin Alerts: Missed visit alerts are available specifically for users with the Branch Administrator role.
Feed Notification Types
Feed can surface alerts from Access Care Planning:
Event Type | What You'll See | Access Level |
Missed Visits | Feed item showing who missed the visit and when | Branch Admin only |
Automation Rules | Configurable Feed item output from an Automation Rule using "Send Evo Feed Item" action | As configured in rule |
Note: Missed visit alerts via Feed are restricted to users with the Branch Administrator user type only.
Prerequisites
Active Access Care Planning account.
Access to the Evo Platform.
Copilot and/or Feed features are enabled for your tenant (contact your system administrator).
Functional cookies are enabled in your browser (Feed and Copilot require functional cookies).
Additional Prerequisites for Missed Visit Feed Alerts
To receive missed visit alerts via Feed, the following must be configured:
User Type: Must be a Branch Administrator.
Tenant Preferences: Alert & Notification Service Status must be enabled (Web Console Preferences section).
Account Preferences: Branch Administrator Access must include the Alert Notifications checkbox enabled.
Branch Configuration: For each branch, Alert Notification Settings must have Notification Type set to Access Feed or to ALL.
Cookie Requirements
Evo Copilot and Feed require functional cookies to operate. If you've rejected non-essential cookies, Copilot and Feed features will not work. To enable Copilot and Feed:
Click the hamburger menu (β°) in the top-left corner.
Go to Resources, then Cookie Policy, then Manage cookie preferences.
Enable Functional cookies.
Save your preferences.
For more information about cookie settings, see the Cookies guide.
Use Evo Copilot
Log in to your Evo Platform account.
Navigate to Access Care Planning through the Evo dropdown.
Look for the Copilot button/icon within ACP (location varies by interface).
Click to open the Copilot chat interface.
Example Queries
Copilot understands natural language questions about your care data. Here are examples of queries you can ask:
Visit Notes:
"Summarise the last three visit notes for [Service User Name]".
"Summarise all visit notes in the past 7 days that mention terms like 'harm'".
"Which care workers have been involved in the most flagged visit notes this month?"
"Show a breakdown of fall or medication issue flags logged per branch last month".
"List all visit notes containing neglect-related keywords across all branches in the last 7 days".
Activities:
"Give me a quick summary of all activities logged for [Service User Name] in the past week".
"What activities are due today that are still outstanding?".
"Show all completed medication-related tasks in the past 3 days".
"Has [Service User Name] had any activities closed as not completed this week?"
"Summarise all morning activities planned for tomorrow".
Important: Copilot provides read-only insights from your ACP data. It does not modify records or create new entries.
Configure Evo Feed notifications
Set up Feed in Automation Engine
Navigate to Configuration, then Services, then Automation.
Create a new automation rule or edit an existing one.
In the Actions section, you'll see "end Evo Feed Item as an available action.
Select Send Evo Feed Item and configure the Feed notification:
To: Define which users should receive the notification.
Subject: Short, descriptive title for the notification (50-character limits apply).
Body: Detailed message content (supports basic markdown formatting, 500-character limits apply).
Add title.
Save the automation rule.
Important: Feed delivery depends on users being linked to a valid Evo account. If users assigned to the rule's target roles are not connected to an Evo user profile, the Feed item cannot be delivered, and the recipient field will remain blank in the Rule Action log.
Set up missed visit alerts in Feed
Navigate to Configuration β Tenant Preferences in ACP.
Enable 'Show Alerts' in your Tenant Preferences.
Go to the relevant Branch, edit the alert under Alert Notification Settings.
Choose Access Feed or ALL under Alert Notification Type.
Click Save.
Note: Missed visit Feed notifications are restricted to the Branch Administrator user type only.
Frequently asked questions
Copilot Questions
Q: Why doesn't Copilot understand my query?
A: If Copilot doesn't understand your query:
Rephrase your question using different words.
Be more specific about service user names, dates, or data types.
Break complex queries into simpler questions.
Check that you're asking about data that exists in ACP.
Start a new topic.
Q: What happens if Copilot gives an incorrect summary?
A: While Copilot aims for accuracy, AI-generated summaries should always be verified against source documents for critical care decisions. If you notice consistent issues, report them to your system administrator so the underlying data quality or query patterns can be reviewed.
Q: Can I customise what Copilot searches for?
A: Copilot searches visit notes and activities based on your natural language queries. You can refine results by being specific in your questions (e.g., including service user names, date ranges, or specific keywords).
Feed Questions
Q: Why can I not filter by my Product in Feed?
A: Once a Feed item has been received from Access Care Planning, you will be able to filter by the product. The filter option becomes available after you've received at least one Feed item from that product.
Q: Why didn't my Feed item send to any recipients (Care Planning)?
A: Feed delivery depends on users being linked to a valid Evo account. If users assigned to the rule's target roles are not connected to an Evo user profile, the Feed item cannot be delivered, and the recipient field will remain blank in the Rule Action log. To resolve this:
Verify that recipients have Evo accounts.
Ensure users are properly linked between ACP and Evo.
Q: Can I send Feed notifications to external users?
A: Feed notifications are only visible to users with Evo accounts and appropriate ACP access. You cannot send Feed notifications to users outside your organisation's Evo environment.

