There There Cli Laravel Package

Product Decisions This Supports

• Build vs. Buy: Accelerates internal tooling for customer support workflows by avoiding custom CLI development for the There There API, reducing engineering effort and time-to-market.
• Feature Expansion: Enables seamless integration of There There’s helpdesk functionality into DevOps, automation pipelines, or internal tools (e.g., incident response scripts, ticket triage bots, or CI/CD notifications).
• Roadmap Alignment: Supports initiatives like:
  • Automated ticket routing (e.g., auto-assigning tickets based on labels/tags via CLI triggers).
  • Cross-system integrations (e.g., linking There There tickets to Jira, GitHub, or Slack using webhooks + CLI commands).
  • Self-service support portals for internal teams (e.g., CLI-driven ticket creation for developers to report issues without UI access).
• Use Cases:
  • Incident Management: Scripted workflows to fetch/update tickets during outages (e.g., there-there tickets:list --status=open --limit=10).
  • Data Migration: Bulk import/export of tickets or customers via CLI (e.g., there-there customers:export --format=csv).
  • Audit/Compliance: CLI-based reporting for ticket histories or SLA violations (e.g., there-there tickets:stats --since=2024-01-01).

When to Consider This Package

• Adopt if:
  • Your team uses There There for helpdesk/customer support and needs CLI automation (e.g., scripting, CI/CD, or internal tools).
  • You’re building DevOps or SRE tools that require programmatic access to ticket data (e.g., incident response playbooks).
  • You need multi-workspace support (profiles) for managing credentials across different There There instances.
  • Your team prefers terminal-based workflows over UI/API libraries (e.g., PHP SDKs) for speed or integration simplicity.
• Look elsewhere if:
  • You’re using a non-There There helpdesk (e.g., Zendesk, Freshdesk) and need cross-platform CLI tools.
  • Your use case requires real-time webhooks or event-driven automation (CLI is pull-based; consider There There’s native webhooks).
  • You need advanced customization (e.g., modifying ticket fields beyond API limits)—this is a thin wrapper over the API.
  • Your team lacks Composer/PHP CLI familiarity (installation requires composer global setup).
  • You prioritize GUI-based tools or low-code solutions over developer-centric CLI.

How to Pitch It (Stakeholders)

For Executives:

*"This CLI tool lets us automate and integrate There There’s helpdesk workflows without building custom solutions. For example:

• Reduce manual work: Script ticket triage or incident updates in seconds (e.g., auto-close resolved tickets via CLI).
• Improve cross-team collaboration: Let DevOps teams create/assign tickets directly from their terminal or CI pipelines.
• Cut costs: Avoid reinventing the wheel—this is a maintained, battle-tested tool from Spatie (creators of Laravel packages used by 1M+ developers). Investment: Minimal (5–10 hours to integrate); ROI in faster incident response and developer productivity."*

For Engineering:

*"This is a lightweight, PHP-based CLI for There There’s API, perfect for:

• Automation: Replace repetitive UI actions with scripts (e.g., there-there tickets:create --subject="Outage" --priority=high).
• Integration: Plug into existing tools (e.g., Bash scripts, Python apps) via JSON/API responses.
• Multi-environment support: Manage multiple There There workspaces with named profiles (e.g., --profile=prod vs. --profile=staging). Why not build it?
• Zero maintenance: Spatie handles updates/bugs.
• Fast iteration: Test commands interactively before embedding in larger systems. Try it: Install globally with composer global require spatie/there-there-cli and run there-there --help to explore commands."*