← Marketplace
Kustomer logo

ConnectorSupport & comms

Kustomer

Kustomer data in BearScope, with supported-note behavior bounded by the live product path.

Ask how Kustomer fits what you run.

Answers are based on this listing. For anything it can't answer, our team can.

For anything this page can't answer, talk to us.

About

The Kustomer connector reads conversations, messages, and customer records as governed events: every thread stamped with its tenant, its source, and the moment it changed. Satisfaction scores, SLA state, and reopen history come with it, so an operator sees the conversation the way your best agent would.

BearScope uses a governed Kustomer product path over live conversations. Supported writes use stable-key controls and recorded outcomes, but a retry is not an unconditional downstream no-op. This listing is the target connector contract, not a public installable artifact.

Highlights

  • Reads conversations
  • Writes notes back idempotently
  • Live in production
  • Writes use idempotency keys and single-flight controls to suppress duplicate effects on retry
Kind
Connector
Category
Support & comms
Publisher
Fibric
Availability
Live in production
In production since
2026-03
Delivery
Managed by Fibric; nothing to install
Data direction
Reads and writes
Pricing
Free
Sold by
Fibric
Support
Developed and supported by Fibric
Tags
support, cx, conversations, tickets

Authentication

A Kustomer API key with the scopes you grant, stored in your tenant's secret store.

What it reads

  • Conversations and messages as they arrive and change
  • Customer records with order and contact history
  • SLA state, satisfaction scores, and reopen events

What it can do

  • Writes notes to a conversation, idempotently
  • Updates conversation status and assignment
  • Syncs call status from your voice platform onto the customer timeline

How it works

1

Sense

Conversations and messages as they arrive and change.

2

Reason

Operators reason over this connector's signals next to the rest of your stack, so decisions are grounded in the same records you run on.

3

Act

Target capability: Writes notes to a conversation, idempotently. Actual authority, duplicate controls, and recovery depend on the validated deployment and downstream system.

Pricing

Live in BearScope · no public self-service offer

This source is evidenced in BearScope through a governed product path. Provisioning, supported capabilities, limits, and commercial terms are managed and deployment-specific.

Deployment engineer
Wires and verifies the integration with you during onboarding
Managed validation
Review maturity, authority, supported records, and deployment boundaries before go-live
Execution records
Supported reads, proposals, policy decisions, and reported outcomes kept for review
Support from the builders
Developed, run, and supported directly by Fibric

Requirements

System requirements
  • A Kustomer instance and an API key with conversation read and note write scopes

Your deployment engineer verifies each line with you during onboarding.

Support and resources

Supported by the people who built it

This connector is developed, run, and supported by the same Fibric team. Support starts during onboarding with a named deployment engineer and doesn't hand you off afterward.

Works with

Listings this is designed to pair with. Each listing has its own live or managed early-access state.

Operator by Fibric

Order Risk

BearScope has a live governed order-risk path. This listing expresses that capability as a target operator contract, not as a public pack or generalized runtime claim.

View details

Operator by Fibric

Operations Analyst

Ask what is happening in plain language and get an answer grounded in your real data. Then turn that answer into a vetted action.

View details

Support & comms connector

Amazon Connect

Brings live and recorded call context into the operational picture, with status sync back to your CX platform of record.

View details

Commerce & orders connector

Magento

Reads orders, line items, and proof approvals as they happen: the upstream signal that an order is about to go wrong.

View details

Put Kustomer to work on your operation

Onboarding starts with what you run and what you want handled. Your deployment engineer wires the connectors with you.