OVERALL CONTROL / 0.6-customer-control
Grades and scoring
Data access
25% of the overall score before applicability adjustment.
Scored answers and evidence
Read interface 7.5/10
Structured API for the declared product scope
Kustomer Apps Platform user-context cards, app registration and customer-selected search/report CSV exports; generic backend customer API eligibility and full schema remain unresolved.
Cards SDK exposes structured current customer/conversation context; this is user-context access.
Kustomer Cards SDK user-context methods ↗
Kustomer.initialize; Sample Context Response · Checked 2026-10-16
Bulk delivery 2.5/10
Manual report download
Kustomer Apps Platform user-context cards, app registration and customer-selected search/report CSV exports; generic backend customer API eligibility and full schema remain unresolved.
Customer search results export CSV up to 50,000 rows.
Kustomer search-result exports ↗
Export search results · Checked 2026-10-16
Query expressiveness -
-
Kustomer Apps Platform user-context cards, app registration and customer-selected search/report CSV exports; generic backend customer API eligibility and full schema remain unresolved.
The reviewed Kustomer scope does not establish query expressiveness.
Kustomer Apps Platform access and API keys ↗
Reviewed product documentation; stated limitation not resolved · Checked 2026-10-16
Access cost barrier -
-
Kustomer Apps Platform user-context cards, app registration and customer-selected search/report CSV exports; generic backend customer API eligibility and full schema remain unresolved.
The reviewed documentation does not establish lowest-plan entitlement and access-specific fixed charges.
Kustomer Apps Platform access and API keys ↗
Reviewed product documentation; stated limitation not resolved · Checked 2026-10-16
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility 5.0/10
Separate provider consent or partner agreement required
Kustomer Apps Platform user-context cards, app registration and customer-selected search/report CSV exports; generic backend customer API eligibility and full schema remain unresolved.
Developers building for clients or a wider audience request a partner organization.
Kustomer Apps Platform access and API keys ↗
Partners and independent developers · Checked 2026-10-16
Downstream permission -
-
Kustomer Apps Platform user-context cards, app registration and customer-selected search/report CSV exports; generic backend customer API eligibility and full schema remain unresolved.
The reviewed technical documentation does not establish contractual permission for the declared downstream processing.
Kustomer Apps Platform access and API keys ↗
Reviewed product documentation; stated limitation not resolved · Checked 2026-10-16
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface 2.5/10
Named operations in a limited domain
Kustomer Apps Platform user-context cards, app registration and customer-selected search/report CSV exports; generic backend customer API eligibility and full schema remain unresolved.
The Cards SDK documents changing a conversation status via PUT under the current user.
Kustomer Cards SDK user-context methods ↗
Kustomer.request example · Checked 2026-10-16
Custom application path 5.0/10
Approved third-party applications using fixed interfaces
Kustomer Apps Platform user-context cards, app registration and customer-selected search/report CSV exports; generic backend customer API eligibility and full schema remain unresolved.
Customer private apps and a separate partner organization route are documented.
Kustomer Apps Platform access and API keys ↗
Existing customers; Partners and independent developers · Checked 2026-10-16
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism 5.0/10
Scheduled feeds or recurring extracts
Kustomer Apps Platform user-context cards, app registration and customer-selected search/report CSV exports; generic backend customer API eligibility and full schema remain unresolved.
Raw reporting exports can run on a schedule up to daily, bounded to 30 days per export.
Kustomer raw reporting exports ↗
Export raw reporting data · Checked 2026-10-16
Limit visibility 7.5/10
Numeric usage or polling guidance
Kustomer Apps Platform user-context cards, app registration and customer-selected search/report CSV exports; generic backend customer API eligibility and full schema remain unresolved.
Search CSV caps at 50,000 rows and one active export; reports have a 30-day data window.
Kustomer search-result exports ↗
Export search results · Checked 2026-10-16
CDC and deletion capture 2.5/10
Full snapshots permit customer reconciliation; native deltas unverified
Kustomer Apps Platform user-context cards, app registration and customer-selected search/report CSV exports; generic backend customer API eligibility and full schema remain unresolved.
Repeated exports permit comparison of identical complete selections; native deletion identities unverified.
Kustomer search-result exports ↗
Export search results · Checked 2026-10-16
Replay and gap recovery 2.5/10
Rebuild from a fresh snapshot; no historical replay established
Kustomer Apps Platform user-context cards, app registration and customer-selected search/report CSV exports; generic backend customer API eligibility and full schema remain unresolved.
Repeat the same bounded search export to rebuild its selected current records; no intermediate or deleted payload recovery established.
Kustomer search-result exports ↗
Export search results · Checked 2026-10-16
Data exit
20% of the overall score before applicability adjustment.
Scored answers and evidence
Export custody 7.5/10
Customer-held structured files or API records
Kustomer Apps Platform user-context cards, app registration and customer-selected search/report CSV exports; generic backend customer API eligibility and full schema remain unresolved.
The customer can email a CSV download link to a chosen address.
Kustomer search-result exports ↗
Export search results · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Kustomer Apps Platform user-context cards, app registration and customer-selected search/report CSV exports; generic backend customer API eligibility and full schema remain unresolved.
No retrieval window or export charge at cancellation is established by these technical sources.
Kustomer Apps Platform access and API keys ↗
Reviewed product documentation; stated limitation not resolved · Checked 2026-10-16
Planned migration fidelity 5.0/10
Selected report fields in structured files; broader scope unverified
Kustomer Apps Platform user-context cards, app registration and customer-selected search/report CSV exports; generic backend customer API eligibility and full schema remain unresolved.
Selected search/report attributes export; object/history and row limits apply.
Kustomer search-result exports ↗
Export search results; Notes · Checked 2026-10-16
Business logic and customization
5% of the overall score before applicability adjustment.
Scored answers and evidence
Logic authoring 7.5/10
Customer-authored native scripts or custom APIs
Kustomer Apps Platform user-context cards, app registration and customer-selected search/report CSV exports; generic backend customer API eligibility and full schema remain unresolved.
Native app JSON defines workflow actions and input/output templates.
Kustomer native app workflow actions ↗
Workflow action definition · Checked 2026-10-16
Rights to custom logic -
-
Kustomer Apps Platform user-context cards, app registration and customer-selected search/report CSV exports; generic backend customer API eligibility and full schema remain unresolved.
Rights to native workflow artifacts and independent execution are not established.
Kustomer Apps Platform access and API keys ↗
Reviewed product documentation; stated limitation not resolved · Checked 2026-10-16
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
CUSTOMER CHOICE
Third-party accessibility
Administrators create expiring role-bearing API keys for app registration. Independent developers building for a client or public audience request a partner organization; Cards SDK calls run with the current user’s permissions.
Confirm who can connect, who owns the credentials and which uses are permitted. Customer consent and provider approval can be separate requirements; the selected plan and contract still matter.
READ / INTEGRATE
API and export routes
Search results export selected columns to CSV and email a download link. Exports allow one active job; old conversation/message/custom-object results have a two-year search caveat.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Client/public app partner organization | API key | Integration provider | Yes | partner organization request; app-registration role-bearing key; data-operation entitlement needs separate verification | 2026-10-16 |
| Customer search/report CSV export | session | Customer | No | eligible customer user supplies exported csv; no session automation or generic backend api inferred | 2026-10-16 |
| Installed Cards SDK user context | session | Customer | Yes | interactive installed app card executes with current signed-in user permissions; app-registration api key is not the mutation actor; no headless session automation | 2026-10-16 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
The export guides refer to plan availability without naming the eligible tier. Fixed API/export fees and partner charges were not established; named role permissions are not a commercial entitlement.
Check API entitlement, credential ownership and rate limits for the route you intend to use. Include review fees, customer-plan upgrades and ongoing access charges in the total.
ACT FROM OUTSIDE
External action
Cards SDK documents PUT conversation status under the current user’s permissions. App registration POSTs a JSON definition; neither operation establishes arbitrary backend customer create/update access.
Validate the supported operation, acting identity and permission scope (read access does not imply write permission). Ambiguous retries and revoked credentials also affect whether an external workflow can run safely.
KEEP ACCESS USEFUL
Continuity
Raw reporting CSV can run on a schedule up to daily with at most 30 days per export. Repeating selected searches supports scoped current-state recovery; event-stream access is a separate support request.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | Full snapshots permit customer reconciliation; native deltas unverifiedKustomer Apps Platform user-context cards, app registration and customer-selected search/report CSV exports; generic backend customer API eligibility and full schema remain unresolved. Repeated exports permit comparison of identical complete selections; native deletion identities unverified. | Kustomer search-result exports ↗Export search resultsChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Rebuild from a fresh snapshot; no historical replay establishedKustomer Apps Platform user-context cards, app registration and customer-selected search/report CSV exports; generic backend customer API eligibility and full schema remain unresolved. Repeat the same bounded search export to rebuild its selected current records; no intermediate or deleted payload recovery established. | Kustomer search-result exports ↗Export search resultsChecked 2026-10-16 |
Useful ongoing access includes corrections and deletions, not only the first export. A failed request, changed filter or lost resource permission should not be interpreted as a deleted record.
LEAVE WITH YOUR DATA
Data exit and portability
Customer-selected search CSV is portable but bounded by selected attributes, 50,000 rows and search history limits. Individual messages require a Message-object export rather than conversation previews.
Test the output against the destination’s required fields and history. Check stable identifiers, relationships, attachments and extraction time; a sample file proves only the coverage of that sample.
BUILD / INSPECT / REUSE
Business logic and customization
A provider tutorial defines native app workflow actions in JSON. Definitions run in Kustomer; ownership and independent execution rights remain unresolved (a tutorial is not a portability license).
Custom API access, ownership of workflows and the right to export their definitions are separate questions. A custom-app capability alone does not establish that business rules can move to another system.
AGREEMENTS / API DOCS / PROGRAM REQUIREMENTS
Documented conditions
Answers below come from public provider materials. Every answer retains its source check date, scope (a partner agreement does not describe every customer route). Customer contracts and live behavior still need verification.
| Question | Answer / applicable route | Evidence |
|---|---|---|
| What structured read interface is documented? | Structured API for the declared product scopeKustomer Apps Platform user-context cards, app registration and customer-selected search/report CSV exports; generic backend customer API eligibility and full schema remain unresolved. Cards SDK exposes structured current customer/conversation context; this is user-context access. | Kustomer Cards SDK user-context methods ↗Kustomer.initialize; Sample Context ResponseChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Manual report downloadKustomer Apps Platform user-context cards, app registration and customer-selected search/report CSV exports; generic backend customer API eligibility and full schema remain unresolved. Customer search results export CSV up to 50,000 rows. | Kustomer search-result exports ↗Export search resultsChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | -Kustomer Apps Platform user-context cards, app registration and customer-selected search/report CSV exports; generic backend customer API eligibility and full schema remain unresolved. The reviewed Kustomer scope does not establish query expressiveness. | Kustomer Apps Platform access and API keys ↗Reviewed product documentation; stated limitation not resolvedChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | Separate provider consent or partner agreement requiredKustomer Apps Platform user-context cards, app registration and customer-selected search/report CSV exports; generic backend customer API eligibility and full schema remain unresolved. Developers building for clients or a wider audience request a partner organization. | Kustomer Apps Platform access and API keys ↗Partners and independent developersChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Kustomer Apps Platform user-context cards, app registration and customer-selected search/report CSV exports; generic backend customer API eligibility and full schema remain unresolved. The reviewed documentation does not establish lowest-plan entitlement and access-specific fixed charges. | Kustomer Apps Platform access and API keys ↗Reviewed product documentation; stated limitation not resolvedChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -Kustomer Apps Platform user-context cards, app registration and customer-selected search/report CSV exports; generic backend customer API eligibility and full schema remain unresolved. The reviewed technical documentation does not establish contractual permission for the declared downstream processing. | Kustomer Apps Platform access and API keys ↗Reviewed product documentation; stated limitation not resolvedChecked 2026-10-16 |
| Which external write operations are documented? | Named operations in a limited domainKustomer Apps Platform user-context cards, app registration and customer-selected search/report CSV exports; generic backend customer API eligibility and full schema remain unresolved. The Cards SDK documents changing a conversation status via PUT under the current user. | Kustomer Cards SDK user-context methods ↗Kustomer.request exampleChecked 2026-10-16 |
| How can customers connect an application they build or choose? | Approved third-party applications using fixed interfacesKustomer Apps Platform user-context cards, app registration and customer-selected search/report CSV exports; generic backend customer API eligibility and full schema remain unresolved. Customer private apps and a separate partner organization route are documented. | Kustomer Apps Platform access and API keys ↗Existing customers; Partners and independent developersChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Scheduled feeds or recurring extractsKustomer Apps Platform user-context cards, app registration and customer-selected search/report CSV exports; generic backend customer API eligibility and full schema remain unresolved. Raw reporting exports can run on a schedule up to daily, bounded to 30 days per export. | Kustomer raw reporting exports ↗Export raw reporting dataChecked 2026-10-16 |
| How are integration limits disclosed? | Numeric usage or polling guidanceKustomer Apps Platform user-context cards, app registration and customer-selected search/report CSV exports; generic backend customer API eligibility and full schema remain unresolved. Search CSV caps at 50,000 rows and one active export; reports have a 30-day data window. | Kustomer search-result exports ↗Export search resultsChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsKustomer Apps Platform user-context cards, app registration and customer-selected search/report CSV exports; generic backend customer API eligibility and full schema remain unresolved. The customer can email a CSV download link to a chosen address. | Kustomer search-result exports ↗Export search resultsChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -Kustomer Apps Platform user-context cards, app registration and customer-selected search/report CSV exports; generic backend customer API eligibility and full schema remain unresolved. No retrieval window or export charge at cancellation is established by these technical sources. | Kustomer Apps Platform access and API keys ↗Reviewed product documentation; stated limitation not resolvedChecked 2026-10-16 |
| How can customers define their own business logic? | Customer-authored native scripts or custom APIsKustomer Apps Platform user-context cards, app registration and customer-selected search/report CSV exports; generic backend customer API eligibility and full schema remain unresolved. Native app JSON defines workflow actions and input/output templates. | Kustomer native app workflow actions ↗Workflow action definitionChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -Kustomer Apps Platform user-context cards, app registration and customer-selected search/report CSV exports; generic backend customer API eligibility and full schema remain unresolved. Rights to native workflow artifacts and independent execution are not established. | Kustomer Apps Platform access and API keys ↗Reviewed product documentation; stated limitation not resolvedChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Selected report fields in structured files; broader scope unverifiedKustomer Apps Platform user-context cards, app registration and customer-selected search/report CSV exports; generic backend customer API eligibility and full schema remain unresolved. Selected search/report attributes export; object/history and row limits apply. | Kustomer search-result exports ↗Export search results; NotesChecked 2026-10-16 |
SOURCES / SCOPE / HISTORY
Sources and open questions
This review is based on the documentation below. Live account behavior and customer-specific agreements haven’t been tested.
Still to confirm
- Generic backend data API operations and credential permissions
- Named export/API plan and fixed charges
- Event-stream entitlement, retention and deletion semantics
- Whole-account attachment/history migration and native artifact rights
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.