Your customers should be able to do this themselves.
Every call your dispatch line takes for “what is my balance” is a call your dispatch line cannot take for “my tank is at 12%.” A growing operation has a customer-experience lead, sometimes a small team, who owns the portal, the SMS thread, the contact form, and the volume of inbound that does not need a dispatcher.
The KozyOps customer portal is built into the platform. Same database, same customer record, same rules. Self-service for the customer, less inbound for the desk.
What customers can do without calling
See their account
Balance, recent deliveries, recent service visits, equipment on the property. All read-only, tied to their portal login.
Pay a bill
Card on file, or a new card. Will-call payments at the time of the request, regular invoice payments any time. On Kozy Payments, those payments flow into the ledger with the gateway’s settlement timestamp. The AR team sees them in real time.
Request a delivery
Online delivery request, the customer asks, the dispatch desk sees it on the will-call queue. Optionally pay at the time of the request.
Book a tune-up
The customer looks at your team’s actual availability and books a service window. The job lands on the tech’s schedule.
Contact the office
A real contact form that lands in your inbox, tied to the customer record. Plus a service-message thread for in-flight jobs and the ability to upload photos.
Reset their own password
Forgot-password and change-password handlers, the way every product should have done a decade ago.
What you control
- Branding, per brand. Portal URL, light and dark logos, favicon, support contact, company name, Service Plan PDFs. Multi-brand operators get a separate surface per brand under the same back office.
- Payment surface. Whether portal payments use Kozy Payments, NMI, or Qualpay.
- Availability. Tune-up booking only shows windows you have configured.
Communications across the customer’s record
Customer messages, contact-form submissions, and SMS threads flow into the same customer record your dispatch desk and AR team see. Twilio SMS conversations are tied to the customer too. The portal is one channel. SMS and (if you have turned it on) OnSIP voice are the others. They share a record, which means the customer-experience lead, the dispatcher, and the AR clerk are looking at one history per customer, not three siloed inboxes.