Black-Bay AICX · Integrations
Read-only integrations and launch acceptance
AICX connects approved customer support journeys to operator records through a read-only connector specification and SDK. Compatibility depends on the source system, permissions and accepted field mapping; a connector is not permission to change customer accounts or transactions.
Reviewed 21 October 2026
Request a private demoChoose the first journey and its source of truth
Begin with a recurring question, such as a pending withdrawal, a KYC status or an account-access issue. Identify which system owns the relevant record and which facts the support team is permitted to disclose after an identity check.
One channel, one language and five intents are an optional initial scope. The implemented channel foundation is web chat. Additional channels, managed follow-up and the managed console require separate scope.
| Area | Decision needed |
|---|---|
| Operator records | Source-system owner, read-only permissions and permitted fields. |
| Identity and access | How a customer is verified and which records that identity can retrieve. |
| Knowledge and wording | Approved policy, language, guardrails and protection wording. |
| Human handoff | Team owner, service hours, record context and reply procedure. |
| Deployment | Acceptance evidence, cost, support responsibilities and written quote. |
Keep connector responses minimal and verifiable
Return only the fields needed to answer the agreed question. Useful support context can include a record identifier, a verified status and the relevant event time, where the source system provides them. Field names and mappings are agreed for the integration; these examples are not a fixed API contract.
Do not infer a completion time from an incomplete status. When information is unavailable, inconsistent or unverified, preserve that uncertainty and hand the issue to a person with the available facts and record IDs.
Exclude account passwords, API credentials and unrelated personal data from response payloads. Chat and retrieved information can reach the contracted model provider; review the data-handling boundary before accepting a field map.
Acceptance checks before launch
- Identity isolation: a verified customer can retrieve only the records permitted for that identity and tenant. Failed verification must not reveal account data.
- Record accuracy: supported answers agree with the source record and approved policy in each accepted language.
- Failure handling: missing records, unavailable systems and unverified results produce a safe response and the agreed review path.
- Handoff continuity: the receiving team sees the question, known facts and record IDs and can reply in the same chat.
- Operating boundaries: confirm resource caps, audit access, service hours and who maintains the connector and knowledge.
Automated checks support implementation evidence. Launch still requires acceptance of the actual sessions, languages, fields, connector and service scope.
What to bring to a private demo
Bring a description of one support journey, the source-system type, the languages needed and a list of candidate fields. Use synthetic examples initially. Do not send live player records or credentials through the public inquiry form.
Black-Bay hosts the platform. Teams can use the connector specification and SDK or agree paid managed onboarding in the quote. A private demonstration can cover the widget, reply-and-ticket view, knowledge settings and handoff flow. Read the product scope to distinguish the implemented foundation from proposed capabilities.