Sluice — demonstration

CRM connection

Connect the CRM the firm already uses. The database stays the record; the CRM is kept in step with it, both ways.

Loading the connection…

The database is the record. Every change in the app is saved there first, as before.
Every save is pushed. Once connected, each household saved is upserted into the CRM (the household, its people, its accounts). The topbar says Synced to the CRM; a CRM failure never loses the save, it shows here as the last error.
Import pulls. Import reads the CRM's households into the database, merged: what the CRM holds wins, what it does not (tax ids, the profile, beneficiaries) is kept.
Acceptance writes back. When the custodian accepts an account, its opportunity closes won with the account number, through the same connection.

Connect the CRM the firm already uses. The database stays the record; the CRM is kept in step with it, both ways.

Loading the connection…

The database is the record. Every change in the app is saved there first, as before.
Every save is pushed. Once connected, each household saved is upserted into the CRM (the household, its people, its accounts). The topbar says Synced to the CRM; a CRM failure never loses the save, it shows here as the last error.
Import pulls. Import reads the CRM's households into the database, merged: what the CRM holds wins, what it does not (tax ids, the profile, beneficiaries) is kept.
Acceptance writes back. When the custodian accepts an account, its opportunity closes won with the account number, through the same connection.