How ChabadOne sync works
Every new person arrives as a ChabadOne Web contact for your team to review. Attendance becomes Event campaign members, and money becomes Income booked as a Charge and a Payment.
On this page
Ovante writes into ChabadOne the way ChabadOne's own web forms do. A new person arrives as a Web contact with a Form Submission, and ChabadOne's merge rules and your team decide who that person is. Ovante does no matching of its own.
People
- The first time Ovante sends something about someone (a registration, a gift or a purchase, as your switches allow), it creates a Web contact with their name, email and mobile, Lead Source Web, and a Form Submission with status Pending for your team to review.
- Ovante doesn't match by email on purpose. Families share email addresses, and ChabadOne's own scoring gets that right more often.
- When your team merges the Web contact into an existing person, Ovante follows the merge. Later check-ins and gifts land on the person who survived the merge.
- If a Web contact is deleted rather than merged, the next activity creates a new one.
- Ovante writes no Ovante id on the contact, because the Web contact is a draft your merge replaces. The records Ovante writes about the person carry the ids instead, and Salesforce moves those to the surviving contact in a merge.
- When
- Someone registers, gives or buys while ChabadOne is connected
- Then
- Ovante creates a ChabadOne Web contact with a Form Submission for your team to review, and ChabadOne's own rules decide who it is. Once ChabadOne merges it into a person, later check-ins and gifts follow to that person.
Events
With Track attendance as Event campaigns on, each event becomes a Campaign with the Event record type and its start and end times.
| In Ovante | In ChabadOne |
|---|---|
| A guest registers | A Confirmed member, with Source Web |
| The guest is checked in | Attended is ticked |
| The check-in is undone | Attended is cleared |
| Not going, or a refund | Declined |
The Campaign's status follows the event's dates, as it does in Salesforce.
Money
ChabadOne books money as an Income record, so Ovante books each payment the same way: a Charge for what was owed, with one line against the event's Campaign, and a Payment for what was paid.
| Ticket purchase | Donation | |
|---|---|---|
| Type | Event | Donation |
| Tax-deductible | No | Yes, unless the gift is marked not deductible |
| Payment type | External Service | External Service |
Money you recorded as collected yourself, on an order you added by hand, books as Cash or Check when your ChabadOne has those payment types, with the method in the memo. A free order books nothing.
Refunds
A refund deletes the Payment and keeps the Charge as a trace: Cancelled, $0 paid, with a note saying when it was refunded. ChabadOne's giving totals add up Payments, so the refund comes off them.
Good to know
- Ovante never books the same money twice. It writes an Ovante id on each Charge and looks for it before writing, which is also how a replay or a reconnect finds what it wrote before.
- ChabadOne creates the Family Account for a new Web contact; Ovante reads it back because Income needs it.
- Membership dues don't sync to ChabadOne.