Nova Kustomer Laravel Package

Product Decisions This Supports

• Whether to surface customer-support context inside the admin panel. The core product question this package answers is: "Should support/ops staff see Kustomer customer profiles and conversation context inside Laravel Nova, or should they context-switch to Kustomer?" The package is a reference implementation of "embed CRM data in the internal tool."
• Build vs. buy vs. deep-link for admin integrations. It gives you a third option beyond (a) building a custom Nova tool and (b) just adding a hyperlink to the Kustomer record. A cheap, MIT-licensed Nova tool is often enough for a v1 read-only view; this package shows roughly what that v1 costs.
• Scoping the internal-tool MVP. The package's shape implies a read-only embed (customer lookup by email/ID, profile/conversation display). That helps you decide whether v1 is "read-only context" or must include write actions (create customer, add note, update attributes) before it earns a roadmap slot.
• Roadmap prioritization of internal tooling. With 18 stars, 0 dependents, and a last release in December 2019, this is a reference, not a dependency. Its value to planning is as a bounded spike (hours, not sprints) to validate demand before committing engineering time.
• Vendor and system-of-record strategy. Adopting it forces an explicit answer to "Is Kustomer the system of record for conversations, and is Nova the system of record for account/order context?" — a decision that outlives the package.
• Deprecation/modernization sequencing. Because it targets the Nova 1.x/2.x and pre-Laravel-8 era, it feeds the decision of when internal tooling must be rebuilt as part of a Nova/Laravel upgrade, rather than as a standalone feature.

When to Consider This Package

Consider it (as a fork or reference) when:

• You are still on Laravel Nova 1.x/2.x and PHP 7.x, and the tool installs cleanly against your Kustomer API version.
• The requirement is read-only: show a customer's Kustomer profile/conversation history in a Nova resource detail page.
• The audience is a small internal team (tens of users) where a broken widget is an annoyance, not a revenue event.
• You want to validate demand fast — a timeboxed spike to see whether support agents actually use in-Nova CRM context before you fund a first-party tool.
• You have capacity to fork and own it, including rotating Kustomer API credentials and handling pagination/rate limits yourself.

Look elsewhere (or build in-house) when:

• You are on Nova 3/4/5 or Laravel 8+. A 2019 Nova tool is very likely incompatible; the migration cost will exceed a clean rewrite.
• You need write actions, webhooks, or real-time conversation updates — this package's scope and maintenance status do not support them.
• You need maintained dependencies. Zero dependents and no release since 2019 means no security patching, no compatibility guarantees, and no upstream fixes; composer audit and upgrade cadence become your problem.
• You operate under compliance or audit requirements (PII in admin, access logging, data-retention rules) — you will need first-party control over authz and PII handling regardless.
• Kustomer's API has moved on from what the package targets; verify the endpoints before assuming any of it works.
• You want a generalizable integration layer (multiple CRMs, or a support-context abstraction) rather than a one-off Kustomer embed.

How to Pitch It (Stakeholders)

For executives: This is a small, MIT-licensed Nova tool that embeds Kustomer customer data into our admin panel, so support and ops staff can see customer context without switching tabs. It is free and tiny — but it was last released in December 2019, has no dependents, and no maintainer activity, so it is not something we should depend on in production. The recommendation is to treat it as a design reference and a one-to-two-day spike, not a purchase or an adoption. If the spike shows agents use the embedded view, we fund a small first-party Nova tool (roughly a few days of engineering) that we control, can patch, and can align with our PII and access-control standards.

For engineering: The package is a thin Nova tool wrapping Kustomer's customer/conversation API, built for the Nova 1.x/2.x era. Expect incompatibility with current Nova and Laravel, stale API contracts, and no test coverage or security patching. Use it to shortcut discovery — endpoint shapes, the Nova tool registration pattern, and the UI shape of a customer-context card — then implement in-house. Budget: spike (1–2 days) to confirm API access and agent demand; build (3–5 days) for a read-only first-party tool with our authz, credential handling, and caching. Decide explicitly whether Kustomer or Nova is the system of record, and gate write actions behind a separate decision.