Transactional Data:

To create or update a Transaction in Sisu, Brivity User must add a trigger Tag to a Brivity contact (the SynchBot is automatically created with default Buyer and Seller Tags, which mirror the Sisu statuses).

Buyer Tags:

Seller Tags:

  • For example, adding the Appt Set tag to a Buyer Lead in Brivity would create a Transaction in Sisu and increment your Appointment Set dial by one:

  • Adding the Appt Met tag to the same Buyer, would then update the status of the Sisu Transaction and increment your Appointment Met dial by one:

Note: You can customize any of the tags on your SynchBot to match the Brivity tag you want to use in its place. Once a new tag is added in your SynchBot, you can delete the preset tag.

Required Fields for New Brivity Contacts:


Brivity Call Logging:

  • Brivity Users are able to Log a Call on a Contact in one of two ways.

  • You can Log a Call using the "Brivity Dialer", which calls the User and then rings the Contact number and saves the duration at the end of the call.

  • Log an "Off-App" call (via mobile or other device - effectively zero duration).

  • In either case, a Call Outcome must be selected in Brivity.

  • Either call type causes the SynchBot to increment the Number of Dials counter in Sisu.

  • The integration also allows you to customize your SynchBot's Source Options to select how to increment your Sisu Connects and Conversations activity counters based on your call durations in Brivity.

  • The third option controls how Zero Duration ("Off App") call logs where the outcome is Talked are counted in Sisu. Options are Conversation, Connect, or No Credit:


Setup: Brivity to Sisu SynchBot


Did this answer your question?