What should you ask at a Homebot One KOKO demo?
A useful Homebot One KOKO demo starts with a specific question about your household. Choose one routine you would like to explore and describe the people, room, and desired outcome. Ask which parts the current robot can demonstrate and which remain development goals.
Send the team a short description beforehand. Include relevant details such as narrow passages, changing furniture arrangements, or several people sharing the space. Avoid sharing private household information that is unnecessary for the discussion. Ask what the demo will cover and whether it reflects a development build or a released product.
What is the robot doing independently?
Ask the presenter to identify the start command, the robot's decisions, and any assistance from a person. Is the route prepared? Is someone operating it remotely? Has the activity been configured for this room? These questions help you understand the demonstration's conditions without dismissing the value of a prototype.
Watch the whole routine, including preparation and reset. If several steps are shown separately, ask whether they currently work as one continuous activity. Note how much intervention is needed and request an explanation when a step cannot be completed.
How do people stay in control?
Ask the team to show the documented pause and stop controls, the supervision requirements, and the procedure for a blocked path. Discuss who may use the robot and what instructions household members or visitors need. Follow the presenter's procedures instead of improvising obstacles or contact tests.
Also ask how the system communicates a misunderstanding. Can someone tell whether it is listening, waiting, moving, or asking for help? A clear explanation of an unfinished task is useful information about the interaction experience.
What happens to household data?
Ask what information the product captures, where it is processed, how long it is retained, and who can access it. Request an explanation of available recording controls, account permissions, and deletion procedures. Include everyone who regularly shares the space in this discussion.
NIST's consumer IoT guidance treats security as a property of the whole product, including related software and services. Its recommended documentation covers data handling, support terms, and expected lifespan. Use those topics to ask about the robot, its app, and any cloud service together; the guidance is not a certification of the product being demonstrated.
What are the KOKO price, availability, and ownership terms?
Discuss charging, cleaning, maintenance, software updates, and how support requests are handled. Ask which costs and service dependencies have been confirmed. If availability or terms are still being developed, record them as open questions instead of filling in the blanks.
After the demo, write down three things: what you observed, what the team stated, and what remains untested in your home. For KOKO, Homebot One reports ongoing in-home testing and engineering validation. Ask which current capabilities are relevant to your proposed use and what a possible next evaluation would involve.
Frequently asked questions
Should I bring a long feature checklist?
Start with one or two important routines. A detailed discussion of their conditions and limitations is often more useful than briefly covering many unrelated features.
Does a successful demo prove it will work in my home?
It shows performance under the demonstrated conditions. Ask which differences in your layout, users, or routine require further evaluation.
Can I ask about the KOKO robot price during a demo?
Yes. Ask for current pricing and availability information for your intended use, including what is included and any recurring costs. If terms are not confirmed, keep them as open questions rather than assuming a price or delivery date.
Sources & further reading
From Homebot One, the team building KOKO in Fremont, California.
