OnOff Automation Solutions
OnOff – Home Assistant Onboarding
Signed-in user: OnOff Technician
Intake will create / update an ITflow ticket.
OnOff Automations · Intake
Home Assistant Pre-Onboarding
Fill this once during the discovery call. Submit to create an ITflow ticket, then export as Word / PDF / HTML.
Step 1: Capture requirements
Step 2: Submit → Ticket created
Step 3: Export → Word / PDF / HTML

Step 0 OnOff Agent & Client Information

OnOff agent (who is creating this intake)
Client / Project Name
Primary Contact
Role / Title
Phone
Email
Number of Locations to Integrate
Planned Go-Live Date
Site Address(es)

Step 1 Goals & Expectations

What do they want Home Assistant to do?
Special use (shul, mikvah, business, rentals, etc.)
Top priorities (with due dates) Add each priority with its target date.
Must-have automations or scenarios

Step 2 Current Automation / Home Assistant Status

Existing automation system Control4 / Crestron / Hubitat / Home Assistant / other
Installed by (if applicable)
Do they already have Home Assistant installed?
If YES, what type of installation? (VM / Docker / Server, host)
Existing integrations
Customizations
Existing dashboards or custom themes
Custom integrations / HACS that must stay

Step 3 Server / Host Platform

Where will Home Assistant run?
Existing server – CPU / RAM / Storage
Power / UPS details
Remote access requirement

Step 4 Devices & Rooms

Devices (counts + make/model) Fill in how many of each and the main brand/model.
Smart switches
Smart dimmers
Smart plugs
Thermostats
Temp / humidity
Motion / presence
Door sensors
Door locks
Window sensors
Blinds / shades
Garage doors / gates
Cameras
Alarm / security
Speakers / media
Relays / contactors
Other device types
Areas & Rooms
Zigbee / Z-Wave / Matter hubs
Critical areas to automate first

Step 5 Integrations & External Services

Cloud services to integrate
Other cloud services
Camera / NVR systems (brand & notes)
Cameras / NVR – IP / Username / Password
Door access / intercom / alarm systems
Door access – IP / Username / Password
Existing APIs or special systems

Step 6 Modes

Predefined modes (check all that apply)
Custom modes

Step 7 Dashboards & Users

Who will use the dashboards?
How many user accounts?
Access levels (admin vs control-only)
Branding / theme (logo, colors, languages)
Important rooms / areas notes

Step 8 Backup, Updates & Maintenance

Backup requirements
Update frequency
Uptime / reliability expectations

Step 9 Contract & Support Plan

Service type
Monthly contract level
Expected response time
Budget range (monthly & one-time)

Step 10 Notes & Next Steps

Special notes / constraints
Immediate action items (0–30 days)
Internal owner (our side)
Client owner / decision maker

Step 11 Meeting Notes & Follow-up

Notes from customer
Promises (what we promised)
To research
To check
Break it or make it
Internal notes
To get back to the client
Need to follow up? When will we follow?
Export Options
PDF options

After submit, attach YAMLs, screenshots, diagrams, and exported files directly to the created ticket in ITflow.