Case studiesVehicle buying and dispatch

Vehicle sales: taking over messaging and extending it through dispatch

For a vehicle-buying business, SMS carried the lead and dispatch workflow. Mark Philippe Mirasol diagnosed failures in the inherited system, rebuilt its sending controls and extended the platform through the later stages of a deal.

Business
Anonymized vehicle-buying business
Sector
Vehicle buying and dispatch
Scope
Messaging rescue and workflow extension
Contributor
Mark Philippe Mirasol
Editorial illustration: an automotive key and orange dispatch tag on a dark road-shaped base
AI-generated editorial illustration of the project’s domain.

A messaging failure interrupted the sales process.

The inherited system had several distinct failure modes: missing inbound replies, carrier filtering, an expired certificate and message content that broke database writes. Shared hosting later constrained the sending queue.

Because leads and deals moved through SMS, each repair needed to address the underlying cause. The existing workflow was worth retaining, but its message handling and infrastructure needed clearer control.

Stabilize the foundation before extending the workflow.

Mark rewrote the inbound handler and built a managed number pool with rate limits, daily caps and a consistent sender for each customer. Later work repaired TLS, handled message content and moved services to AWS Lightsail.

The workflow expanded into Google Maps address validation, VIN checks, Zoho CRM fields, business-hours follow-up and stage changes from offer to dispatch. AI intent detection was later extended with RoBERTa confidence scoring and Redis conversation history.

What the workflow includes

  • Control sending rates and keep a consistent customer-facing number.
  • Validate addresses and VINs through external services.
  • Schedule follow-up within business hours.
  • Carry the deal from incoming message to dispatch confirmation.

Project details

Automated flow from accepted vehicle offer to dispatch notification

Project materials showing the workflows and interfaces described in this case.

Lead handling and dispatch shared a defined operating path.

The delivery connected diagnosis, infrastructure changes and incremental product improvements around one business workflow. The message-handling foundation supported the later address, quotation and dispatch features.

What this means for the technology owner.

This is the core of a software takeover: understand the inherited behavior, fix its failure paths and improve the system without losing the business process. Account control, carrier dependencies, queue behavior and recovery steps need to be recorded so the next operator can work from them.

Taking over existing business software →

PHPTwilioZoho CRMAWS LightsailOpenAIRoBERTaRedis

Project contribution: Mark Philippe Mirasol. The scope described above identifies the work behind this case.

Editorial review: Ego Eimi · Updated September 6, 2026 · About the team

Your technology

Start with the business

Your business depends on it.

Tell us which system matters, what has changed and who controls it. We will define a reviewable next step. Read Foundation and the commitments and evidence.