Confirm the mapping was saved, the source value exists in Chronicle and the integration user can modify the destination tab. Check the field result before using the shared resync guide.
Use the Neos integration
Use matched Neos cases for client-field updates, documents and the optional return of client details to Chronicle. Complete Connect Neos to Chronicle first.
What syncs
Available capabilities and enabled settings are different. Review the options your firm wants to use.
Capability | Direction | What it does |
|---|---|---|
Client fields and case dates | Chronicle to Neos | Update saved Case, Party, case-date and supported user-tab mappings. |
Documents | Chronicle to Neos | Upload selected SSA documents and organize them with Chronicle tags. |
SSN back-sync | Neos to Chronicle | Fill missing full SSNs from matched Neos cases. |
Hearings and CEs | Chronicle to Neos | Create calendar appointments as the Microsoft 365 integration user. |
Contact details | Neos to Chronicle | Pull configured date of birth, phone and email sources. |
Matching | Links existing records | Use the case links verified during setup. |
Client messages | Chronicle to Neos | Log new Dispatch texts and replies as case notes under a selected topic. |
Case ownership | Neos to Chronicle | Make eligible teammates follow cases for the selected staff roles. |
Open the integration
A Chronicle administrator or account owner can manage these settings.
In Chronicle, open Settings > Integrations.
Open Neos.
Use Overview for settings and Sync for status and run results.
The Neos Sync tab's Status view.
Move from matching to everyday use
If the app checklist is still open, the remaining choices control how your firm uses the integration.
Use Open mapping to configure destination mappings when offered, or Skip for now to leave them for later.
Open Choose what to sync and review the capabilities below.
Click Finish setup after reviewing the choices.
During first-time setup, documents and hearings start on unless the Microsoft 365 requirement blocks them. Skip for now in Choose what to sync completes the app checklist without turning those defaults off. Review the switches before finishing.
Client fields and case dates
Choose only the fields your firm wants us to maintain. Neos has a client-field mapping view, without a separate stage-mapping tab. We fill mapped fields going forward as new SSA information arrives; syncing does not backfill earlier data.
The Mapping panel. Edit mapping opens the mapping editor; matching runs again with every sync.
In Overview > Mapping, click Edit mapping.
Click Add Mapping.
Choose a Chronicle field and the destination Neos field.
Use Show descriptions when needed.
Click Save mapping.
Use Refresh fields from Neos for new definitions. Supported destinations include case fields, party fields, case dates and entry-style User Tabs 6–10. List-style User Tabs 1–5 are not supported.
Fields and definitions depend on the selected case types. Your Neos administrator can create destination fields your firm needs before refreshing the list in Chronicle.
Client field mapping options lists the Chronicle fields.
Re-add tasks after a case-date change
Enable Re-add completed tasks when a case date changes in the mapping editor only if you want Done and N/A tasks re-added when we later update a mapped date, including a reschedule. Tasks are added the first time a case date is filled regardless of this switch.
Click Save mapping after changing the mapping settings.
The client-field mapping view with ten mappings configured. The re-add completed tasks option is set in the mapping editor.
Documents
File SSA documents already available in Chronicle on the matched Neos case.
In Overview > What syncs, turn on Documents.
Click Change sections.
Select the sections to include.
Click Save.
Document sync runs every 15 minutes. For failed filing, use Resync integration data. Turning Documents off or unchecking a section stops new filing for that scope; existing files remain in the destination.
Where your documents appear
Chronicle adds documents to each case's Docs tab in Neos. You'll find them under the Chronicle ERE tag, along with a tag for each section of the file, such as "A. Payment Documents/Decisions". If you've created a Chronicle document type, they'll use that too.
If documents aren't showing up
If hearings are syncing but documents aren't, the Chronicle user most likely needs access to your SharePoint documents site. Once your IT team grants it, documents will start appearing on their own, with nothing else to do.
When you first turn on document sync, Chronicle adds your existing documents gradually, so it may take a few days for everything to appear.
SSN back-sync
Fill a missing full SSN in Chronicle from the standard SSN source on the matched Neos case. There is no source-field selector, and an SSN already present in Chronicle is not replaced.
In Overview > What syncs, find SSN back-sync.
Turn on SSN back-sync.
Check the client's monitoring eligibility after the full SSN has been filled.
Hearings and CEs
Neos creates appointments as the licensed Microsoft 365 integration user. There is no separate calendar organizer to choose.
Confirm the integration user is connected to Office 365 in Neos.
In Overview > What syncs, click Change beside Hearings and CEs.
Set Sync hearings and Sync CE appointments independently.
Check an upcoming appointment in Neos after the next sync.
Changes save automatically. Reschedules and cancellations follow the synced appointments.
The Hearings and CEs dialog. Set Sync hearings and Sync CE appointments independently.
Contact details
Pull selected contact details from Neos into Chronicle. This is separate from destination fields sent in the other direction.
In Overview > What syncs, click Change beside Contact details.
Turn on Sync contact details from Neos.
Select a source for Date of birth, Phone number and Email, leaving fields blank when you do not want to pull them.
Changes save automatically. Valid values can update existing Chronicle details; blank incoming values do not clear them. A field pulled from the provider is excluded from the outbound mapping picker.
Available sources depend on the selected case types and readable fields. If no date-of-birth source is available, check the integration user's Advanced Search access and refresh the Neos options.
Example sources. Phone is selected, Email has no source, and no date-of-birth source is available in this configuration.
Client messages
Dispatch access and Neos note permissions are required. New outbound texts and client replies are filed as text-message case notes.
In Overview > What syncs, click Change beside Client messages.
Select an active Note topic.
Turn on Sync client messages.
The topic saves automatically. Only new messages after syncing is enabled are included. A deactivated topic pauses message syncing; choose an active topic to resume it.
Case ownership
Eligible Chronicle teammates automatically follow cases associated with the provider roles your firm selects.
In Overview > What syncs, use Set up beside Case ownership, or Change roles when configured.
Select the ownership roles your firm uses.
Review the provider-user matches and choose the correct Chronicle teammate where needed.
Click Save roles.
Neos roles can include Primary staff, Intake staff and the staff-assignment roles available for your case types. The Staff Directory must be readable.
Restricted and view-only teammates can be matched to provider users but do not automatically follow cases through ownership. Removing a role or turning ownership off removes follows supplied only by that ownership rule.
Example role choices. Ownership is off and the recommended role has not been saved.
Grant access for the features you enable
Use this table to review the read and write actions your firm needs. Grant Modify access to the tabs receiving mapped data. If the corresponding permission is unclear in your profile, ask Neos Support to identify it for that action.
Feature | Access needed | Scope |
|---|---|---|
Field mapping setup | Read case setup and user-defined field definitions | We load definitions for the Case tab, Party tab, case dates, and User Tabs 6–10 for each selected case type. |
Mapped case fields | View and Modify on the Case tab | Update fields mapped in Chronicle. |
Mapped party fields | View and Modify on the Party tab | Update user-defined fields on the existing client party. This is separate from changing the contact's name or contact details. |
Mapped case dates | Read and update case dates | Read existing dates before applying mapped date updates. |
Mapped user-tab fields | View and Modify on the relevant user tab | Entry-style User Tabs 6–10 are supported. List-style User Tabs 1–5 are not supported for field mapping. |
Case ownership | Directories → Staff Directory → Enabled, plus read access to case staff assignments | Match staff to Chronicle users. We do not add or modify staff-directory entries. |
Contact backfill | Read access to the Party tab and contact/name details | Read client phone numbers and email addresses. Date-of-birth backfill also needs Advanced Search. |
Client-message sync | Read note topics and add case notes | Required only when syncing Chronicle Dispatch messages into Neos. We do not create a note for every case-field update. |
Document sync | Read document types and document metadata; add documents; modify document metadata; read and add document tags | Required when document sync is enabled. We upload ERE documents, organize them with tags, and update filenames when needed. |
Hearing and CE sync creates calendar events in Neos as the integration user. There is no separate calendar organizer to choose.
We do not use checklist, provider, intake, insurance, negotiation, time, or value writes in the Neos integration. Adding ERE documents also does not require generating documents from Neos templates.
Restore Microsoft 365-dependent syncs
We check the Neos integration user at connection, when you use Check again and daily. If the user is no longer connected to Microsoft 365, document, hearing and CE sync are turned off.
In Neos, connect the integration user to Office 365 using a licensed Microsoft 365 account. Complete the connection rather than choosing Later.
In Chronicle, open the Neos Connection panel and click Check again.
After the user shows Microsoft 365 connected, turn on the document, hearing and CE switches your firm wants.
A successful check does not turn those switches back on automatically.
The What syncs switches on the Neos Overview.
Shared sync and matching guides
Check integration sync status: review capability status, run results and one client's activity.
Resync integration data: choose a retry scope or retry an individual item.
Fix a client's integration match: resolve missing or ambiguous matches and correct an existing link.
Usage troubleshooting
Mapped fields show no data
No active note topic is available
Create or activate a topic in Neos, then reload the client-message settings. If topics cannot load, check note-topic read access and case-note creation access.