Ticket Creation Demo
Watch messy demand become a shareable project ticket.
This demo is only about the homeowner ticket flow: capture the request, preserve evidence, structure scope, and create an unlisted link. No quotes, bidding, contractor matching, or scheduling.
Project definition before outreach
Freya identifies blockers before pricing
Images appear as images, not document sheets
Share anywhere: text, email, Messenger, Facebook
Live ticket preview
Unlisted
Messy request
Homeowner message
Need a heat pump installed next week. Older house, old one died last night. House is about 1200 sqft I think. See pics.
Outdoor unit
Indoor head
Electrical panel
House exterior
Voice note transcript adds urgency, floors, and comfort goal.
Freya output
Heat Pump Install Ticket
Conditional
Job Identity
- Residential heat pump install or replacement request
- Older home with incomplete electrical and routing context
- Pricing readiness remains conditional until blockers are closed
Critical Unknowns
- Electrical panel/service capacity photo
- Indoor and outdoor placement photos
- Coverage goal: whole home or main living area
Intake Confidence Model
- Scope Confidence: 52%
- Photos present, equipment identified, and timeline known
- Missing: electrical panel photo, existing equipment details, ductwork status
Next Message
- Can you send a photo of the electrical panel with the door open, a wide photo of where the indoor unit should go, and a wide photo of where the outdoor unit could sit?
1
Describe the job
Homeowner types or speaks the messy request in normal language.
2
Attach evidence
Photos stay clean and visual; metadata stays stored with the file.
3
Freya structures scope
Known facts, likely scenario, blockers, risks, and next action are separated.
4
Share the ticket
An unlisted link shows contractors the scope and what is still missing before pricing.