Launching today

Foley
A voice to-do list that files, plans and asks first
19 followers
A voice to-do list that files, plans and asks first
19 followers
Say what needs doing. Foley turns it into a task with the project, date and reminder already set, and asks when it isn't sure instead of guessing. When plans change, say so and it moves the task. Ask it to plan your day, or what to work on first, and it answers from your list. Capture from your Apple Watch. The desktop app is free with no account, using your own OpenRouter key. Foley Pro runs the AI for you and syncs every device. On iPhone, Android, Mac, Windows and the web.






Free Options
Launch Team

ClarifyThe full-stack AI CRM for modern GTM teams
Promoted
Handling relative time like "next Tuesday morning" is the part of voice capture that usually breaks first. Building voice AI for older adults, the trickiest case for us was self-corrections mid-sentence ("Thursday, no wait, Friday"). Does Foley treat the last thing said as the final intent, or does it ask you to confirm when it hears a correction like that?
@igorgurovich Great question, Igor, and self-corrections are exactly where we got bitten too.
Foley reads the whole sentence before it files anything, and the last value you say wins. So "Thursday, no wait, Friday" or "actually make that Friday" becomes one task on Friday. There's no extra confirm step, because you already see what it understood before the task lands, and you can fix it there.
It only asks when it's truly unsure: two people called Sam, a project it hasn't seen, or a reminder with just "morning" and no time. A good question beats a bad guess.
On relative time, we don't trust the model with the calendar. When it resolves a weekday like "next Tuesday", the app checks the date in code against your device's clock before saving.
Our hardest real miss was the terse form: "Add a task to call the dentist tomorrow. Update it: Friday." The word "Update" pulled the model toward editing an older task. We fixed it in the task structure, because changing the prompt alone didn't stop it.
Curious how you handle it for older adults. Do you confirm out loud, or show it on screen?
"asks when it isn't sure instead of guessing" is the right default and most voice products get it backwards because asking feels like friction and guessing feels like magic, until the guess is wrong and now you've got a task filed under the wrong project with a made-up date. we fight the same tradeoff on calls at Dial. where's the line for you on what counts as "not sure", confidence score under some threshold, or ambiguity between two specific candidates like two projects with similar names?
@galdayan Great question, and you're absolutely right, Gal. Essentially, the way that I found it was that, as I was doing some testing, it kept coming up with specific things it had decided that it just didn't make sense.
One of the tests that I was doing was when I wanted to add the task, but I didn't specifically provide it the time. This could be an all-day task, of course, but generally, tasks have a specific time. This was more or less at the time that Jev came out. Jev makes the decision on whether this is clear or whether we are missing information or not.
Obviously, there could be much more improvement that I can do, but on a general basis, I think it's pretty good as it is in terms of asking follow-up questions. It kind of becomes a dialogue between yourself and Foley.
can it handle task well even when plans change?
@shivam_kushwaha16 yes it should do. If unsure on ambiguous request it should ask follow up to clarify