Frequently asked questions

A ticket's subject and description are sent to Google Cloud Vertex AI for classification. The four scores are written back to your CRM. SentimentSync does not store the ticket body; it keeps only the four scores, a confidence value, a short rationale, and a content fingerprint used to skip re-scoring.

No. It creates its own 'sentimentsync' property group with four custom properties (sentimentsync_sentiment, sentimentsync_category, sentimentsync_intent, sentimentsync_priority) and writes only to those. Your built-in ticket fields, such as hs_ticket_priority, are untouched.

Two: tickets and oauth. Nothing more. It reads a ticket's subject and description and writes the four custom properties back.

A ticket is scored when it is created and when its subject or description changes. Unchanged tickets are skipped by a content fingerprint before a credit is used, so you are not charged twice for the same text.

SentimentSync backfills your most recent tickets, newest first, up to your plan limit (50 on Free, 1,000 on Pro). It does not re-score your entire ticket history.

Scoring stops. The custom properties and the values already written to your tickets are your data and remain in your HubSpot portal.

By scored ticket per month. Free covers 50 scored tickets a month with no card; Pro is 39 EUR a month for 1,000. Billing runs on our own Stripe, not through HubSpot. See the pricing page for the full comparison.

Processing runs on Google Cloud Vertex AI under Google's data-governance terms, which state that customer data is not used to train Google's foundation models.