Meet Luzena, the Client Pilot.
Luzena by Luzstar · Controlled Voice-Intake Pilot
Luzena is being tested for missed and after-hours voice intake. No real business call is handled without consent, owner approval, configured providers, active monitoring, fallback, and verified safeguards.
The planned pilot always discloses that Luzena is an AI. Any authorized test must produce evidence of what happened and what did not.
Illustrative workflow — capabilities depend on configured integrations.
Staging Demonstration
A fictional call, handled honestly.
This example shows the intended Client Pilot behavior. It is not a live call or client result, and the exact workflow must be configured and verified for each business.
"Thanks for calling — this is Luzena, the AI assistant for Northline Heating. The team's out on jobs right now, but I can take down exactly what you need. What's going on?"
"My furnace stopped working and it's freezing. Can someone come out tomorrow morning?"
"That's urgent — I'm flagging it top priority and alerting the team right now. I can set up a request for tomorrow morning and they'll confirm the exact time with you. What's the best number to reach you?"
"612-555-0142. I'm Sarah."
"Got it, Sarah — 612-555-0142, no heat, top priority, morning request in. The team will call to confirm the time. I won't promise an arrival time myself, because I don't control the schedule — but your request is logged and they've been notified."
Fictional demo conversation. Northline Heating is not a real client. No booking was claimed — a booking request was created for human confirmation.
Controlled Staging
What the Client Pilot is being tested to do.
These capabilities remain behind attended setup, consent, provider readiness, monitoring, fallback, rollback, and an owner-approved test window.
Handle an approved test call
The voice flow is tested only during a monitored window with consent and a human fallback.
Use approved answers
The planned flow is limited to business answers the owner has reviewed. It must not invent prices, policies, or promises.
Capture requested details
Name, phone, service need, and urgency can be tested, but real storage requires an approved and verified destination.
Prepare booking requests
A preferred day and time can be treated as a request for human confirmation, never as a confirmed appointment.
Test urgency routing
Urgency detection and owner notification must be verified for the specific business before any real use.
Disclose that it is AI
Every authorized test must introduce Luzena as an AI assistant. It never pretends to be human.
The Road Ahead — Stated Honestly
Capabilities that could be considered after verification.
These are engineering commitments on our roadmap — not current features. Each one unlocks only when its verification gate passes for your specific business.
Verified calendar writes
Direct calendar booking could be considered only after the exact workflow is simulated, approved, and verified end to end.
SMS text-back & confirmations
Missed-call text-back and appointment confirmations by text — once A2P 10DLC compliance is set up for your number.
CRM sync
Every captured lead will flow straight into your CRM with status and follow-up dates — after the integration is tested against your system.
Warm transfer to a human
A live transfer could be added only after the on-call path and fallback are tested, and a handoff could be claimed only when it connects.
Owner call reports
Plain-language evidence could show what came in, what the system did, what it did not do, and what needs a human.
Why the gates? Because a receptionist who writes to the wrong calendar or texts without compliance isn't an upgrade — it's a liability. Luzena earns each capability per business, with tests, before it goes live.
Her Signature
Every call ends with a truth report.
The Client Pilot is designed to report what actually happened, including what did not. If no booking was written, the report must say so. If no text was sent, the report must say so.
This isn't a feature we bolted on. It's how the whole system is built: no claim leaves Luzena's mouth without a real mechanism behind it.
Hard Lines
What Luzena will never do.
Never claims a booking that didn't happen. "Booked" means the appointment was actually written. Until then, it's a request.
Never pretends to be human. Every authorized test must introduce Luzena as an AI assistant.
Never sends texts without compliance. No SMS until A2P 10DLC registration is done for your business. Period.
Never promises arrival times or dispatch. She doesn't control your schedule or your trucks, so she doesn't speak for them.
Getting Started
How a future controlled pilot would work.
Consent and attended setup
The owner approves the business information, call boundaries, provider setup, test number, and exact test window.
One monitored test window
A real call occurs only after runtime checks pass, with monitoring, human fallback, and rollback ready.
Evidence before expansion
The owner reviews the call record and truth report before deciding whether another controlled step is appropriate.
Pricing
Future pilot pricing will be scoped per business.
Joining the waitlist is not a purchase or activation. Any future quote would depend on call volume, workflow complexity, compliance, providers, and the approved pilot boundary.
Starter
For solo operators losing leads to voicemail.
- Missed-call capture
- Daily summaries
- Approved FAQ handling
- Basic lead organization
Growth
For teams ready for 24/7 intake.
- Luzena voice/text intake
- Urgent lead routing
- Booking request capture
- Weekly review notes
Pro
For multi-truck fleets with deeper needs.
- Verified booking workflow when approved
- CRM/calendar sync after verification
- Custom reporting
- Follow-up automation
- Advanced workflow support
Questions
Fair questions, straight answers.
Does Luzena pretend to be human?
No. Every authorized test must disclose that Luzena is an AI assistant at the start of the call.
Does this replace my receptionist?
No. She handles overflow, after-hours, and missed calls to support your existing team, not replace them.
Can she book appointments?
Not by default. A staging test may capture a preferred time as a request for human confirmation. Direct calendar writes would require separate approval and end-to-end verification.
Can she work after hours only?
That is a planned configuration option. It would still require consent, an approved schedule, provider readiness, monitoring, and a tested fallback.
What if Luzena does not know the answer?
The approved script must defer to a human and avoid inventing policies, prices, or promises. This behavior is verified before any real test call.
Can she connect to my CRM or calendar?
Not during initial staging. Any future connection would require explicit approval, least-privilege access, simulation, rollback preparation, and independent readback.
What happens during a pilot?
A pilot would start with one owner-approved, monitored test window. The evidence would be reviewed before any expansion or permanent setup.
Controlled Staging · Pilot Waitlist
Join the Client Pilot waitlist.
Tell us about your business so we can evaluate future fit. Submitting this form does not authorize a call, activate a provider, create a deployment, or move real customer data.
Important
Luzstar Systems is not an emergency service, dispatcher, or licensed HVAC provider. The Client Pilot is in controlled staging and is not a live public answering service.
Appointment, callback, service-area, and pricing claims are only made when configured and verified. The conversation and truth report shown on this page are fictional examples that demonstrate real guardrails — they are not client results.