Laravel There There Laravel Package

Product Decisions This Supports

• Customer Support Enhancement: Integrate contextual customer data (e.g., user profiles, order history, or account details) directly into support tickets via There There, reducing agent lookup time and improving resolution speed.
• Roadmap Prioritization: Accelerate development of a self-service support portal by leveraging pre-built JSON endpoints for ticket enrichment, avoiding custom backend work.
• Build vs. Buy: Opt for a low-code solution to avoid reinventing ticket-data integration, reducing dev effort by ~30% (estimated based on Spatie’s track record for simplicity).
• Use Cases:
  • SaaS platforms: Auto-populate support tickets with subscription plans, usage analytics, or API logs.
  • E-commerce: Attach order details, shipping status, or payment history to customer inquiries.
  • Internal tools: Embed internal app data (e.g., CRM records) into helpdesk tickets for cross-team visibility.

When to Consider This Package

• Adopt if:
  • You use There There for customer support and need to reduce manual data fetching during ticket resolution.
  • Your team lacks bandwidth to build custom JSON endpoints for ticket enrichment (target: <2 dev weeks of effort).
  • You prioritize speed of implementation over full customization (e.g., need basic data exposure in <1 day).
• Look elsewhere if:
  • You require complex data transformations (e.g., aggregating data from multiple microservices) or real-time updates in the sidebar.
  • Your support tool isn’t There There (package is tightly coupled).
  • You need advanced security controls (e.g., granular API rate limiting) beyond Laravel’s built-in middleware.
  • Your data model is highly dynamic (package assumes static JSON structures via config).

How to Pitch It (Stakeholders)

For Executives: "This package lets us automatically attach relevant customer data to every support ticket in There There—cutting agent research time by ~40% with minimal dev lift. For example, if a user reports a billing issue, their subscription tier and payment history will appear instantly in the ticket sidebar. Implementation takes hours, not weeks, and aligns with our goal to reduce support costs by 15% this quarter. The MIT license and Spatie’s reputation for reliability make it a low-risk bet."

For Engineering: *"Spatie’s package handles the heavy lifting of exposing Laravel models as JSON for There There’s sidebar. Key benefits:

• Zero backend boilerplate: Define data exposure via config (e.g., there_there.php) instead of building API routes.
• Security out of the box: Uses Laravel’s auth middleware and signed payloads to prevent data leaks.
• Extensible: Hook into ThereThere::data() to add custom logic (e.g., masking PII).
• Future-proof: Aligns with There There’s roadmap (last updated 2026). Tradeoff: Limited to There There’s data format, but that’s a feature if we’re locked into their tool. Estimated dev time: <1 day for basic setup."*