Things to try

Every prompt below is something Charyl can actually do today, grouped by what it touches. None of these are hypothetical — they’re drawn from the same tool surface she actually runs on. Use them as written, or as a starting point for your own version of the same question.

Inventory & warranties

• “What do I own in the kitchen?” — pulls straight from your inventory, filtered to that room.
• “What’s expiring soon on my warranties?” — a sorted list, soonest first.
• “How’s my home doing overall — anything I should deal with?” — a one-question health check across warranties, maintenance, and open items.
• “I just bought a new dishwasher, can you add it?” (with a photo of the nameplate) — she researches it and drafts the record for your approval.

Manuals & documents

• “What does error code F02 mean on my washer?” — answered from the manual on file, with the page cited.
• “How do I reset the filter light on the fridge?” — same, for whatever’s actually in the document.

Maintenance

• “I had the furnace serviced today by Acme Heating.” — logged as a maintenance record for you to approve, no separate form to fill out.
• “What maintenance is overdue?” — surfaces already-overdue items first, not just what’s coming up.

Home records

• “What’s my hurricane deductible?” — answered from your insurance policy on file, cited to the page.
• “When does my flood insurance renew?” — pulled from the same Home Records store.
• [Attach a PDF] “File this as my new homeowner’s policy.” — filed as a new Home Record, one tap to confirm.
• “The expiration date you pulled for my policy is wrong, it should be March.” — corrects the record directly, one tap to confirm.

Smart home

• “Turn off the living room lights.” — resolves the room to a device, then asks you to confirm before switching it off.
• “Dim the bedroom lights to 30 percent.” — same confirm step, for brightness.
• “Set the porch light to warm white.” — same, for color temperature.
• “Turn the bedroom fan to medium.” — same, for a fan preset.

Sensors

• “What was the average kitchen temperature today?” — a summary across the day, not a single live reading.
• “Has anyone been in the garage in the last hour?” — read from a presence sensor, if your home has one.

Cameras

• “Show me the driveway.” — a snapshot, not a live stream.
• “Pull up the front door live.” — opens a live view; free on your home network, part of the subscription remotely.
• “Snooze the doorbell notifications for an hour.” — quotes back the exact time it’ll resume.

Dashboards

• “Build me a dashboard for the garage.” — starts from what’s already grounded in your home, then asks you to confirm before creating it.
• “Add a toggle for the porch light to this dashboard.” — same confirm step, added to an existing dashboard.
• “Delete my old dashboard.” — asks you to type the dashboard’s name before it’s gone, since this one isn’t reversible.

Memory

• “Remember that I prefer temperatures in Celsius.” — held onto across conversations, until you ask her to forget it.
• “You can forget about the kitchen reno now, it’s done.” — needs to be specific enough to match one thing; a vague request is declined rather than guessed at.

Service providers

• “Who do I call about the AC making a noise?” — checks who’s already on file for that asset first.
• “Find me a plumber.” — a category search, not tied to a specific asset.
• “Yeah, I’ve got a guy — John’s HVAC.” — proposes the provider she doesn’t already have on file, for your approval.

Commands

• /bug (then describe the problem) — opens a consent card before anything is sent.
• /request a dark mode for the dashboard — same path, filed as a feature request instead of a bug.

None of these need special phrasing — they’re written the way you’d naturally ask. See How do I ask Charyl good questions? for more on what makes a question easy for her to answer well.