Connect Neos to Chronicle

Connect a firm's Neos (Assembly Software) instance to Chronicle to sync ERE data into Neos. Plan for a 30-minute screen-share with the firm: several steps are easy to get stuck on.

Before you start

1. Open a ticket with Assembly Software asking them to enable the Chronicle integration on the firm's Neos tenant. Expect to follow up; provisioning has taken up to a few days.

2. Complete the intake form the Neos support team sends, and reply to confirm it's done.

3. Provide the Production Integration ID to Neos Support on the ticket: 2983557f-c266-4366-b70d-6fc9f48b8e1d.

4. Wait for Neos to confirm the integration is provisioned before scheduling the setup call.

Step 1 — Create the Chronicle integration user in Neos

This is the step most firms miss on their own. In Neos, go to Settings → Staff Profiles → Add and create a profile with:

• Name: Chronicle

• Staff code: anything

• Job title: required, and it must be picked from Neos's built-in list; free text returns "No results." "Information specialist" works.

• Time zone: the firm's time zone

• Password: have the firm set one

• "Neos User?" checkbox: leave unchecked so the firm isn't charged for an extra user license

If Neos offers to connect an Office 365 account, click Later.

The email field is greyed out on the create form. Save the profile first, then reopen it: the email field becomes editable. Enter the Chronicle integration email address, then click Connect now.

Step 2 — Grant permissions to the integration user

In Neos, go to Staff Profiles → Chronicle → Permissions and enable all permissions across the Case, Case → Name details, General, and Special sections (Special includes "Change case type"). Save after each section, and verify every toggle shows enabled before moving on.

We don't yet know which single permission unlocks case-type reads, so every setup so far has required enabling everything. Skipping this causes Chronicle to connect successfully but fail to pull case types.

Step 3 — Activate the integration in Neos

In Neos, go to Settings → Integrations. Chronicle should appear under CRM. Click Activate.

Chronicle often doesn't appear in the selector right away, and refreshing the page usually isn't enough. Have the firm log out of Neos and log back in, then check again.

Step 4 — Configure the integration in Chronicle

In Chronicle, go to Settings → Integrations → Neos.

1. Enter in the Neos Company ID in Chronicle and click connect

2. Confirm Sync health shows healthy.

3. Under Configuration, set the Case Type (for example, Social Security).

4. Click Save field mapping.

At this point the connection is live.

Step 5 — Run client matching

Launch client matching from Chronicle. Records are matched on last name + last four digits of SSN.

Failures land in two buckets, no match and multiple matches, both visible under the unmatchable filter.

The usual cause of an unmatchable record is a last-name spelling difference. Chronicle uses the spelling on file with the SSA and cannot change it, so the fix is to edit the name in Neos to match, then re-sync.

To re-run a match, wait for the full run to finish and click Resync, or use the sync option in an individual client's dropdown menu. Large books take a while: let the run complete before reviewing the unmatchable list.

Step 6 — Set up client field mappings

In Chronicle, go to Field mapping → Client field mappings → Add mapping.

Each mapping pairs a Chronicle field with a Neos field. Use the show descriptions toggle if the field names aren't self-explanatory. Neos-side options include case dates and user tab fields. See Client field mapping options for every Chronicle field.

Nothing flows until a mapping is saved. Once saved, Chronicle automatically updates those fields with ERE data going forward.

Firms often need to create new fields in Neos to receive Chronicle data, and most won't want everything pushed across. Treat this as a per-firm decision rather than a standard template.

Step 7 — Turn on the optional syncs

• Document sync: drops ERE documents into a Chronicle folder on each Neos matter

• Send back sync: pulls SSNs out of Neos into Chronicle so they don't have to be entered manually

• Contact backfill: pulls phone number, date of birth, and email out of Neos

Common issues