Tags Passed via CRM Integrations
This article includes the tags which are passed as a part of Ruuster's direct API integrations with Follow Up Boss and Sierra Interactive.
The following are tags sent to and from Ruuster via the Sierra and Follow Up Boss API integrations. They are tags which are common for all Ruuster accounts. (This is in distinction from custom tags which are applied by individual clients to individual saved searches.)
Direction
Tag
Description
CRM → Ruuster | Ruuster | Applying this tag to a client in the CRM in order to also add that client to your associated Ruuster account. |
CRM → Ruuster | Ruuster Default Search | Applying this tag to a client in the CRM will apply the default saved search via AI Nurture inside of Ruuster. |
Ruuster → CRM | appClientInviteSent | An invitation to sign up/download your custom-branded mobile app was sent to the client. |
Ruuster → CRM | appClientOnboarded | The client has logged in to their account via the client portal. This is a one-time tag to signify that the client's account has been created. |
Ruuster → CRM | appViewedProperty * | The client viewed a property inside of the client portal. The specific property is not signified via tag, however, agents may view the client activity tab in the mobile app for the same (and also in the Ruuster widget inside of FUB). We also log specific property views as notes in the lead detail page in the integrated CRM. |
Ruuster → CRM | appPropertySearch | The client ran a property search inside the client portal. The specific search is not signified via tag, however, agents may view the client activity tab in the mobile app for the same (and also in the Ruuster widget inside of FUB). We also log specific property searches as notes in the lead detail page in the integrated CRM. |
Ruuster → CRM | pageViewedInApp * | The client viewed a page inside the client portal. This could be a property listing, a vendor portal page, the budget calculator, etc. |
Ruuster → CRM | clientRequestPreferredVendorContact * | The client selected to contact a vendor from within the client portal. The specific vendor is not signified via tag, however, agents may view the client activity tab in the mobile app for the same (and also in the Ruuster widget inside of FUB). We also log specific vendor contacts as notes in the lead detail page in the integrated CRM. |
Ruuster → CRM | clientInfoUpdatedFromApp | The client updated their info (name, email, and/ or phone number) from within the client portal. |
Ruuster → CRM | clientReassignedFromApp * | The client was manually reassigned by an admin to another agent from within the client portal. |
Ruuster → CRM | clientHasSignedUpOnLandingPage | The client has registered on a landing page provided via the Ruuster IDX. |
Ruuster → CRM | appChatMessage * | The client has sent an inbound chat message through the client portal. The specific message contents are not signified via tag, however, agents may view the client activity tab in the mobile app for the same (and also in the Ruuster widget inside of FUB). We also log specific chat message contents as notes in the lead detail page in the integrated CRM. |
Ruuster → CRM | appFavoriteProperty * | The client has favorited a property through the Ruuster IDX. The specific favorited property is not signified via tag, however, agents may view the client activity tab in the mobile app for the same (and also in the Ruuster widget inside of FUB). We also log specific favorited properties as notes in the lead detail page in the integrated CRM. |
Ruuster → CRM | appSavedSearch * | The client has saved a search performed via the Ruuster IDX. The specific saved search is not signified via tag, however, agents may view the client activity tab in the mobile app for the same (and also in the Ruuster widget inside of FUB). We also log specific saved searches as notes in the lead detail page in the integrated CRM. |
Ruuster → CRM | Stop notifications | The client has selected in the portal to no longer receive notifications, which means they will not receive any actively applied notifications via email, text message, and/ or push notification. This action will not impact any communication methods in the lead's connected CRM. |
Ruuster → CRM | appInitiatedCallWithAgent * | The client has placed a phone call to their agent via the client portal by selecting "Call Agent". |
Ruuster → CRM | appPropertyTourRequested * | The client has requested a property tour from within the client portal. The specific property and tour information is not signified via tag, however, agents may view the client activity tab in the mobile app for the same (and also in the Ruuster widget inside of FUB). We also log specific property and tour information as notes in the lead detail page in the integrated CRM. |
Ruuster → CRM | RuusterNewLead | When a new lead is created in the CRM from the Ruuster IDX or mobile app, this tag is added to the lead alongside a tag with the email address of the assigned agent. This tag will accompany a tag with the email address of the assigned agent. |
Ruuster → CRM | ruuster_e-alert_user_unsubscribed | The client has clicked on the unsubscribe button in a property alert sent via the client portal. This action will not impact any communication methods in the lead's connected CRM. |
Ruuster → CRM | ruuster_e-alert_auto_unsubscribed | The client has been unsubscribed from a property alert because of email bounce or another reason other than manually selecting to unsubscribe. This action will not impact any communication methods in the lead's connected CRM. |
Ruuster → CRM | Ruuster E-Alert | This tag is added to any client for whom we have imported searches from another service. |
*Please note: Any tag above with an asterisk* will apply more than once (when applicable) -- that is, every time one of the following tags fires from Ruuster to your API-connected CRM, if that tag is already applied, then the initially applied tag will be removed then added immediately after. Why? So you can theoretically run more than one automation based on that tag(s) without any manual action from your agent.