Research adjacent use case: client intake, calls, and appointment reminders

[diese-tech]

Context

Real-user feedback from a lawyer raised an adjacent workflow need: a system that can field calls, intake clients, allow text-based communication, and send appointment reminders.

This is not necessarily a tonight build item, but it is useful market signal because the same underlying workflow pattern appears outside HVAC:

• incoming request
• intake details
• assignment or follow-up
• appointment/reminder communication
• status tracking

Recommendation

Track this as a discovery/backlog item, not core MVP scope.

SwiftDispatch should stay HVAC-focused for the current product direction. However, the underlying platform may eventually support service businesses where intake, dispatch, reminders, and customer communication are the real product surface.

Potential future directions

• Call intake workflow
• Client/customer intake form variants
• Appointment reminder SMS
• Follow-up reminder SMS
• Staff assignment / routing
• Service-specific templates for intake questions
• Vertical-specific terminology layer, e.g. job/client/case/appointment

Important constraint

Do not let this derail the HVAC MVP. This should be treated as market discovery unless multiple users from the same adjacent vertical show demand.

Acceptance criteria for discovery

• Capture at least 3 examples of non-HVAC service workflows that map cleanly onto SwiftDispatch.
• Identify which parts are generic platform capabilities vs vertical-specific customization.
• Decide whether this belongs as future multi-vertical positioning, a separate product, or a hard no.
• Do not implement until the HVAC demo and private beta flow are stable.

Why this matters

The feedback suggests SwiftDispatch may be solving a broader service-operations problem. That is interesting, but also dangerous. The right move is to capture the signal without widening the MVP too early.