belter.app
Get started
CRM · 2 connectors

Evaluate the support thread inside your CRM.

HubSpot Service Hub and Salesforce Service Cloud both expose support tickets and email messages alongside the rest of the customer record. Belter pulls the conversation, scores it, and writes the score back so reps see QA signal in the same surface they sell from.

Connect-ready Pull · managed today Managed import UI shipping next
CRM connectors are connect-ready, not fully self-serve.
The API client and OAuth flow are shipped. The managed import wizard (the Zendesk-style filter UI) is in development. Talk to us to enable a managed pull while we finish polishing it.
Case #00041892 · Service Cloud
Acme Logistics — Renewal escalation
Closed
Subject
VPS migration — can't reach new IP
Email msgs
14
Duration
3d 4h
Belter QA · written back
87
Empathy 92 · Resolution 85 · Compliance 100
Coaching note drafted for AE
Connect-ready

HubSpot

The HubSpot service fetches tickets and the full conversation threads attached to them — chat, email, form submissions. Auth is a Private App token plus optional portal ID for multi-hub orgs. Managed import lives in our hands today; the wizard ships next.

  1. 1Create a HubSpot Private App with tickets, conversations, and crm.objects.contacts.read scopes.
  2. 2Drop the token into Belter's HubSpot connector.
  3. 3Tell us which pipelines and ticket statuses to pull — we'll run the import.
  4. 4Subscribe to evaluation.completed if you want scores written back into HubSpot.
Auth
Private App token + portal ID
Pulls
Tickets + conversation threads
Import UI
Managed today · UI in dev
Writeback
Via outbound webhook
Connect HubSpot Request early access →
HubSpot Private App · scopes Required
READ tickets ●
READ conversations.read ●
READ crm.objects.contacts.read ●
OPT crm.objects.owners.read recommended
We never request write scopes during import. Score writeback is a separate, opt-in outbound webhook.
Connect-ready

Salesforce Service Cloud

Cases plus EmailMessage records. Auth is your instance URL, an OAuth refresh token, and a Connected App's client ID/secret — exactly what your Salesforce admin already has provisioned. Belter handles the token-exchange dance; you supply credentials once.

  1. 1Create a Connected App in Salesforce with API + refresh-token scopes.
  2. 2Authorise once; Belter stores the refresh token (encrypted at rest).
  3. 3We pull Cases + EmailMessages bound to those cases — case origin, status, owner all preserved.
  4. 4Managed import today; self-serve filter wizard arrives next release.
Auth
OAuth · Connected App
Pulls
Cases + EmailMessages
Instance
my-domain.salesforce.com
Import UI
Managed today · UI in dev
Connect Salesforce Request early access →
OAuth flow · once per org ● Authorised 03 Jun
Salesforce
Connected App
Belter
stores refresh token
Instance
aurora-hosting.my.salesforce.com
SOQL scope
SELECT Id, Subject, Status FROM Case WHERE Origin IN ('Email','Web')
Why bother

When QA meets the CRM, sellers stop guessing.

The support thread is often the most candid version of the customer's relationship with you. Putting QA scores back into the CRM closes the loop with the team that owns renewal.

Renewal context

AEs see QA score + churn signal on the account before the renewal call. No more surprises.

CSAT in context

Bring CSAT survey results in (via the CSAT API) and Belter ties them to the underlying conversation automatically.

Compliance trail

PII flags, disclosure checks, and audit notes are written back so the case record itself proves it.

Keep exploring

Other integration categories

SupportZendesk, Intercom, FreshdeskSelf-serve ticket platforms. Live ChatLiveChat, ChatwootReal-time chat conversations. VoiceRingCentral, Amazon ConnectPhone calls transcribed and scored. OutboundWebhooksWrite scores back into your CRM.
Talk to us

Want first-look access while the CRM UI ships?

If HubSpot or Salesforce is your source of truth, get on the early-access list. We'll run the import managed and bring you onto the self-serve wizard the day it lands.

Request early access Start with another source