The same viewing moment can have several dates and times
A viewer may remember a robot at 10 a.m. on October 2, while a national listing, streaming service, or repost uses another time zone or publication date. Syndication, delayed broadcasts, local preemption, recordings, and on-demand availability can separate the viewing time from the original air time. Searching only one date may miss the responsible episode.
Record the viewer's city or market, station or channel, provider, local date and time, whether the content was live or recorded, and how the clock was obtained. If the clue came from a social post, keep its upload time separate from the claimed broadcast time.
Identify the station before relying on a national schedule
In the United States, the FCC public inspection file search accepts a call sign, network affiliation, channel number, or facility ID. Use it to resolve a remembered station marker and community of license. Then check the station's own schedule and the network's official show or episode page for the candidate day.
A network affiliation does not guarantee that every affiliate aired the same content at the same local time. Special events, local news, sports, and schedule changes can alter the lineup. Preserve the schedule URL and access date, and distinguish the station record from the program's national page.
- Viewer's city, ZIP code, or media market
- Call sign, channel, provider, and network affiliation
- Local time, time zone, and daylight-saving status
- Live, recorded, streamed, or on-demand viewing
- Official station and program schedule URLs
Normalize times without erasing the original clue
Keep the reported local time as entered, then add a normalized time with the named zone and date. Do not convert an abbreviation such as CST without checking location and daylight-saving rules. NIST's time service provides U.S. time-zone context, but the research log should still explain the conversion used.
Dates near midnight need extra care because a UTC timestamp can fall on the next calendar day while the local broadcast remains on the prior date. Streaming platforms may display availability in the user's current zone rather than the original market. Record both values and never overwrite the viewer's original note.
Match the candidate program, then the robot
A schedule match establishes that a program aired in a market; it does not identify every object in the episode. Find the full episode, official clip, transcript, credits, or production record and note the timestamp. CBS's episode guide can anchor dates for The Price Is Right, but its brief game summaries do not catalog every visible product.
Only after the episode is anchored should you compare the robot with Homebot One's official KOKO pages. Search Coco and Co Co as variants, but require the company match before changing the name to KOKO. Keep the broadcaster evidence and product evidence in separate fields.
Report the market and search window with the result
A reproducible conclusion names the market, station, local time, normalized time, schedule pages, episode record, and product source. If only the schedule matches, say so. If the clip came from on-demand playback, avoid describing the viewing time as the air time.
The named Homebot One, KOKO Home, CBS show, and CBS episode pages reviewed on October 5, 2026 did not connect KOKO to a named The Price Is Right episode. Regional schedule research can narrow where to look, but it does not replace direct program and product evidence.
Frequently asked questions
Why can a TV robot search need more than one date?
Local air time, national schedule time, streaming availability, recording playback, upload time, and UTC timestamps can refer to different moments.
How do I identify a U.S. broadcast station?
Use the FCC public inspection file search with a call sign, affiliation, channel number, or facility ID, then verify the station's schedule.
Does a matching schedule prove KOKO appeared?
No. It confirms a program record. You still need episode-level media and Homebot One product evidence that meet on the same robot.
Should I convert every timestamp to UTC?
Keep the original local value and add a clearly labeled normalized value. State the zone and daylight-saving assumption used for the conversion.
Sources & further reading
- FCC: Public Inspection Files station search (opens in a new tab)
- NIST: Official U.S. Time and time-zone information (opens in a new tab)
- Homebot One: Official KOKO overview (opens in a new tab)
- KOKO Home: Official product page (opens in a new tab)
- CBS: The Price Is Right official episode guide (opens in a new tab)
From Homebot One, the team building KOKO in Fremont, California.



