Customer intake, CRM lifecycle, workflows, agreements, invoices, billing schedules, alerts and operator visibility.
BR Lifestyle
Built · Tested · DocumentedVehicle rental operations system built around GoHighLevel.
BR Lifestyle needed one connected way to handle the rental journey, from the first application through approval, agreements, payment, active-rental billing and return.
RENTAL LIFECYCLESelected architecture
01Apply
02Review
03Vehicle
04Agreement
05Payment
06Pickup
07Rental
08Billing
09Return
Contact + Opportunity modelOperational gatesInitial + recurring billingQA evidence
The problem
The job was not to add more tools. It was to make the rental process work as one system.
Applications, customer records, agreements, payment activity and active-rental actions needed to follow the same rental lifecycle. The system also had to preserve the places where staff still needed to review information, select a vehicle or stop a rental from moving forward.
That meant the architecture had to support both automation and operational control.
System architecture
Put the right work in GoHighLevel. Keep the right decisions outside it.
Customer-facing entry point into qualification and application.
Physical fleet data remains outside the CRM and is referenced by Vehicle ID / Unit Code.
Manual review, vehicle decisions and release decisions stay with the people responsible for the rental.
CRM model
The pipeline acts as an operational control system, not just a visual board.
01One renterOne Contact
02One application / booking / rentalOne Opportunity
03Only one active application or rentalPer Contact at a time
04Historical Closed Won / Declined / CancelledDo not block a future application
The Contact holds the person. The Opportunity holds the current rental lifecycle. That separation keeps customer identity stable while allowing each application or rental to retain its own history.
Controls & stage gates
Automation can move the process. It should not be able to bypass the business rules.
HARD RELEASE GATEPickup is never allowed before the initial rental payment is confirmed paid.
Agreement completion and payment confirmation are separate control points. Staff must verify payment status before vehicle release.
Operator-required information is visible and required at the point where it becomes operationally necessary.
Insurance method, agreement path, payment state and rental stage determine which workflow can continue.
Fields used only by workflow logic stay hidden where possible to reduce accidental staff edits.
Billing logic
Payment automation follows the rental state, not a generic reminder sequence.
01Agreement signedPayment can be requested
02Initial paymentRental charges + applicable tax
03Rental activeNext weekly due date initialized
04Weekly billingDate-driven recurring payment request
05ExtensionReturn date changes only after successful payment
INITIAL INVOICERental charges only
Security deposit is handled outside GoHighLevel.
WEEKLY SCHEDULINGCustom Date Reminder
The next due date advances after a successful weekly payment.
DAILY EXTENSIONDate-based calculation
Extension charge is calculated from the approved extension date and current expected return date.
QA & operational proof
If a workflow needs manual rescue during the test, the test has not passed.
The build was tested through the actual customer and operator path, not only by pressing isolated workflow test buttons. Major scenarios were checked from qualification and application through agreement, payment, rental activation, recurring billing and extensions.
MASTER QA / SELECTED TESTSControlled test evidence
01Qualification → applicationPassed
02Contact + Opportunity mappingsPassed
03Vehicle stage-gate dataPassed
04Agreement → payment handoffPassed
05Initial payment → Ready for PickupPassed
06Rental Active → first weekly due datePassed
07Return Overdue weekly paymentPassed
08Daily extension paymentPassed
Result
A connected rental operating structure inside GoHighLevel.
The result is a connected rental operating structure inside GoHighLevel that brings applications, customer records, agreements, payments, recurring billing and day-to-day rental actions into the same process.
Instead of treating each step as a separate tool or isolated automation, the system follows the rental lifecycle and gives the operator defined points to review, act and intervene.
BuiltTestedDocumented
Work With Me
Need a system that connects more than one part of the customer journey?
Tell me what the business needs to do, what is already in place and where the process is breaking down. I’ll start from there.
Tell me what you’re working on Back to selected work