Dentist, physical and haircut: Muse failed all three bookings, asked about 20 questions on two of the three, tried email instead of the form; the author booked the dentist one in about 30 seconds
PablanoPato(Reddit 用户 u/PablanoPato,原帖作者本人,自述让 Muse 去约三项个人预约但全部失败)Reddit · 2026-10-14
Read originalSaved text / editorial summary
原帖正文(Reddit r/MuseAgent,作者 u/PablanoPato;本轮经 Reddit 公开 Atom feed 取得,以下英文部分逐字未改写): “I can't tell what I'm doing wrong, but I can't seem to get Muse to accomplish things for me. For example, gave it the task of scheduling a dentist appointment, annual physical, and a haircut. It failed on all of them. I told it the new dentist I wanted to use on couldn't locate the big 'new patient appointment request' form on their website. Asked me maybe 20 questions and tried sending an email despite clear instructions it needed to use the form. I stepped in and booked the app in about 30 seconds. For the physical it understood that the doctor had a patient portal. Didn't offer to try to navigate the portal for me and asked me another 20 questions. I scheduled the visit while it was thinking in less than a minute. The one that pissed me off was the haircut. It located the booking page and everything and burned a bunch of time writing my barber a long winded email asking about if one of these 10 times from my calendar were acceptable. I just rebooked from the booking page for a new date. I can't tell what I'm missing or doing wrong. Whenever I prompt Muse it asks tons of questions and doesn't actually accomplish the task.” 中文对照:作者说三项预约全失败。牙医:Muse 找不到诊所网站上很显眼的「新患者预约申请」表单,问了约 20 个问题,并在明确要求用表单的情况下仍尝试发邮件;作者自己约 30 秒订完。体检:Muse 知道有患者门户,却没提出去门户里操作,又问了约 20 个问题;作者不到一分钟自己约完。理发:Muse 找到了预订页,却花时间给理发师拟一封长邮件,问日历里 10 个时间哪个合适;作者直接从预订页另选日期。作者结论是它总在问问题、没有把事办完。 注:原帖写的是「writing my barber a long winded email」,只说明在拟邮件,未说明是否真的发出;本页一律按「拟了一封长邮件」表述,不写成已发送。
Business model
Reddit user u/PablanoPato posted 'Struggling to get Muse to do things for me' in r/MuseAgent: he gave Muse three bookings - a dentist appointment, an annual physical and a haircut - and it failed on all of them. For the dentist, Muse could not locate the big 'new patient appointment request' form on the new clinic's website, asked maybe 20 questions and tried sending an email despite clear instructions to use the form; the author stepped in and booked it in about 30 seconds. For the physical, Muse understood the doctor had a patient portal but did not offer to navigate it and asked another 20 questions; the author scheduled the visit in less than a minute while it was thinking. For the haircut, Muse located the booking page but burned time writing the barber a long-winded email asking which of 10 times from the calendar would work; the author simply rebooked from the booking page for a new date. The post says the original text only describes writing that email, not sending it. The author's conclusion: whenever he prompts Muse it asks tons of questions and does not actually accomplish the task. There are no successful bookings, no time-savings calculation, no amounts and no subscription cost; the 30 seconds and under a minute are how long the author took to do it himself, not time saved by the agent. The workflow, prompt, synthetic sample and the 'find the official entry point first, never substitute email' rules are AgentFlow proposals, not the author's practice.
The reusable rule is 'confirm the entry point before allowing any action'. All three failures happened at the same point: there was an official form, a patient portal or a booking page, and the agent substituted questions or an email instead. Making 'find the official entry point' a hard gate, and handing the link back to the person when it cannot be found, is more useful than tuning the prompt. The author's own conclusion is that it asks a lot of questions without finishing. The one-question limit, the no-email substitution and the human submission step are AgentFlow's additions, not his method.
Workflow
- Write each task as clinic plus official entry point plus hard constraints. (AgentFlow's prerequisite; the post gives three tasks and one explicit form-only instruction.)
- Find the official form, portal or booking page first; if it is not found, stop and hand the link back. (AgentFlow's boundary - the post shows Muse doing the opposite.)
- Merge all clarifications into one question at most, then proceed. (AgentFlow's response to the two rounds of about 20 questions.)
- Keep submitting, logging in, paying and sending anything external with the owner. (AgentFlow's boundary; the post describes no confirmation step.)
- Report a status table that says 'not done' when it is not done - finding a page is not a booking.
- Stop at login walls, CAPTCHA or anti-bot checks; do not bypass them. (AgentFlow's compliance boundary; not mentioned in the post.)
Adaptation plan
The post does not say which clinic, which portal, what the 20 questions were, whether the long email to the barber was ever sent, how the agent was authorised, what it costs, or whether login, CAPTCHA or blocking played any part. It gives no successful booking and no time saved. The 30-second and under-a-minute figures are the author's own handling time, not a measured comparison. No reproduction was attempted; the sample here is synthetic.
Prompt
AgentFlow draft · Untested.
You are my appointment-preparation assistant. You may locate official booking entry points, list the fields required and prepare draft content. You do not log in, submit forms, pay, send email or text, substitute email for an official form, or bypass login, CAPTCHA or anti-bot checks. [INPUT] - Task list: [e.g. dentist / annual physical / haircut], each with clinic name, official website and entry-point type (form / patient portal / booking page) - Available dates or slots: [list] - Hard constraints: [e.g. the dentist must go through the new-patient appointment request form] - Forbidden actions: [e.g. do not fall back to email] - Fields I will fill myself: [field list] [STEPS] 1. For each task, locate the official entry point and report its URL, its label, and whether it matches the type I gave. If it is not found, write 'entry point not found + pages checked + suggest I open it myself', stop that task, and do not fall back to email or a guessed contact. 2. Merge every clarification needed for that task into one question at most; if the information is sufficient, continue without asking. 3. List the fields the entry point requires and mark which are personal information I must fill myself. 4. Prepare a draft (request or slot proposal) labelled as a draft, not sent - never describe it as contact made or booking confirmed. 5. Produce a status table: task / official entry point / found or not / blocker / submitted or not / who does the next step. 6. List a 'needs my confirmation' item for every submission, login, payment and external send, stating what I need to do. [OUTPUT] 1) entry-point check per task; 2) one merged question if needed; 3) required fields; 4) unsent draft; 5) status table; 6) confirmation list. [NEEDS MY CONFIRMATION] - Every form submission, login and payment: I do it myself. - Every email, text or call: I confirm and send it. - If the official entry point differs from the type I gave, or the page adds requirements: ask me, do not reroute on your own. [IF MATERIAL IS MISSING OR A STEP FAILS] Page unreachable, entry point missing, login required, CAPTCHA or anti-bot check, slot conflicts: state which task and step is blocked and stop. Never fall back to email, guess contact details or use any bypass. Prefer three honest 'not done' rows over one 'booked' claim based only on finding a page.
Running costs and pitfalls
The post does not say which clinic, which portal, what the 20 questions were, whether the long email to the barber was ever sent, how the agent was authorised, what it costs, or whether login, CAPTCHA or blocking played any part. It gives no successful booking and no time saved. The 30-second and under-a-minute figures are the author's own handling time, not a measured comparison. No reproduction was attempted; the sample here is synthetic. No independent cost benchmark is available. Check subscriptions, permissions and external actions before running a workflow.