Delegate Errands to Muse: Let Meta's Personal AI Agent Handle Bookings, Forms, and Follow-Ups

Purchasing and coordination take about four hours of your week, and they arrive in pieces. A teacher needs toner and chart paper by Thursday. A contractor promised a quote on the front-office repair two weeks ago and never sent it. The principal wants lunch catered for the next PD day, and nothing can be ordered until the purchase order clears the district ERP. Each errand means a few phone calls, a vendor who goes quiet, and a price you look up twice because the district catalog and the store website disagree. You squeeze all of it in between late passes, parent calls, and the 6:30 sub scramble.

Muse can carry those errands while you run the front desk. It emails vendors and contractors for quotes, follows up when they stall, and hands you a comparison table. It prices a supply list across more than one source, so you know the number before you enter the PO. For PD days it shortlists caterers and rooms that fit the headcount and the budget line. Nothing gets sent or paid until you tap approve.

Keep it on logistics. Your inbox holds parent absence notes, enrollment paperwork, and payroll questions from staff. That is FERPA and HR territory, and none of these errands needs it.

What This Builds

The conference registration you keep meaning to finish. Three vendor quotes nobody has replied to. A license renewal form with eleven screens. Errands like these eat evenings because each one is small but spread across tabs, logins, and waiting. This build sets up Muse, Meta's personal AI agent, so you can hand it an errand in a few sentences, close the app, and come back to a finished booking or a short list of approvals waiting for your tap.

You end up with three reusable pieces: a connected Muse account with permissions you chose deliberately, a standing-preferences message Muse remembers, and a delegation brief template you fill in for every new errand.

Prerequisites

• Comfortable giving a chatbot detailed instructions, and comfortable granting an app access to an email or calendar account
• A US address, age 18 or older, and a payment card (Muse asks for one at signup, even on the free plan)
• A Muse account. Sign up at muse.ai/join or in the Muse app, then within 48 hours of creating the account open Settings and enter invite code DUQ2T7. That gives you 1 billion bonus Muse tokens, roughly ten weeks of free-tier usage, on top of the weekly free allowance. This is a referral code, and the redemption window closes 48 hours after your account is created.
• Total ongoing cost: $0/month on the Muse Free plan, which covers occasional errands. If you start handing off work every day, you may need the Power plan. Current limits: Free plan includes the full agent, Secure VM and browser with roughly 100 million Muse tokens per week; Power ($20/month) raises that to 500 million and Maximum ($100/month) to 3 billion. US only, payment card required at signup.
• About an hour for setup and one test errand

The Concept

Think of Muse as a capable assistant who works from a desk in another building. That desk is a private cloud computer Meta calls the Muse Secure VM, with its own web browser. Muse can open sites, compare options, fill in forms, and draft emails there, and it keeps going after you close the app on your phone.

A second system sits at the door of that office. Meta calls it the Sentinel, and nothing Muse does reaches the internet unless the Sentinel lets it through. When Muse wants to send an email, pay for something, or take another sensitive step, the Sentinel stops and asks you first. Every action lands in an audit trail you can read later.

Muse runs on Meta's Muse Spark 1.3 model, and you do not pick a model. It connects to your own accounts: Gmail, Google Calendar, Outlook, WhatsApp, Instagram, Notion, GitHub, OpenTable, Ticketmaster, Expedia, Plaid for bank data, and retail partners such as Best Buy, Walmart, and Wayfair. Purchases go through Link by Stripe with a one-time virtual card, so Muse never sees your real card number. It also remembers what you tell it once, like your seat preference or a food allergy, and applies that to later tasks.

You can reach it on iOS, Android, the web at muse.ai, inside a WhatsApp chat, and through a Mac app that works with your local files, mail, and calendar.

Build It Step by Step

Part 1: Account, Connectors, and Approval Rules

1. Create the account. Go to muse.ai/join or install "Muse from Meta" on your phone. Enter your payment card when asked.
2. Redeem the invite code now. Open Settings, find the invite or referral code field, and enter DUQ2T7. Do it today. The window closes 48 hours after account creation, and the 1 billion bonus tokens give you room to experiment without watching the meter.
3. Decide which accounts to connect, and how. Open the connections area in Settings and look at each app before you switch it on. Every connector is controlled per app, and email accounts offer a choice between read-only and send-capable access. Start narrow:

   • Connect your calendar so Muse can check availability and add holds.
   • Connect one email account as read-only first. You can upgrade it to send access later, once you trust how Muse drafts.
   • Leave messaging apps, bank data, and social accounts off until a task actually needs them.
4. Know what "connected" means. Muse reads everything in an account you connect. One early user who gave the Mac app broad access found 187,000 rows of iMessage history synced into it. If your work email holds customer, patient, tenant, student, or employee information, connect it read-only or not at all, and ask whoever owns your organization's data policy before you connect it. Muse is built for personal accounts. It has no CRM, helpdesk, or shared-inbox connectors, so keep it on your own errands, not your team's records.
5. Check privacy settings. Meta says Muse conversations and VM data are not shared with its ad systems. If you would rather Meta not train its models on your conversations, look in the privacy settings for the training opt-out.
6. Leave approvals on. By default, the Sentinel asks you before Muse sends an email or pays for anything. Keep it that way. Turn on notifications for the Muse app (or use Muse inside WhatsApp) so approval requests reach you where you already look.

Part 2: Standing Preferences and the Delegation Brief

Muse does its best work when it knows your defaults and gets each errand as a clear brief. Set up both pieces now.

Standing preferences. Send this once, filled in with your details. Muse stores it in memory and applies it to every later task.

Please remember these standing preferences and apply them to every task unless I say otherwise:

- Name for bookings (as it appears on my ID): [full name]
- Home airport: [code]. Seat preference: [aisle/window]. Loyalty numbers: [airline/hotel and number]
- Dietary needs: [e.g. vegetarian, no shellfish]
- Always ask me before sending any email or message, paying for anything, accepting terms, or cancelling or changing an existing booking. Do this even if you think I would approve.
- In my work email, draft only. Tell me when a draft is ready. Never send from that account.
- Any single purchase over [amount] needs my approval along with two cheaper alternatives.
- If a site blocks you or needs a login you do not have, stop and tell me. Do not switch to a different site on your own.
- When a task is done, send one summary with every confirmation number and the total cost. Skip progress updates unless you are blocked.

The delegation brief. Copy this into a note you can reach from your phone. Fill in the brackets for each new errand.

Task: [one sentence describing what "done" looks like]

Background: [dates, names, reference numbers, links, and any document or detail you want Muse to use]

Constraints:
- Budget: no more than [amount] in total
- Use only: [sites, vendors, or accounts]. Avoid: [sites or vendors]
- Rules to follow: [e.g. travel policy limits, refundable fares only, within 1 mile of the venue]

Ask me before you:
- Send any email or message
- Pay for anything
- Share any personal detail or document not listed above
- Cancel or change anything that already exists

Deadline: finish by [date and time]. If you are blocked for more than [number] hours, message me with what you tried and what you need from me.

Report back with: a short summary, every confirmation number, total cost, and anything you could not finish and why.

The "Ask me before you" block repeats what the Sentinel already enforces. That repetition is deliberate. It tells Muse to plan around the approvals, so it gathers everything first and asks once instead of pinging you five times.

Part 3: Test, Check the Audit Trail, Then Go Long-Running

1. Run a low-stakes errand first. Pick something where a mistake costs nothing. For example: "Find three places near my office where I can get a passport photo this week, with hours and price, and add a 30-minute hold on my calendar for the closest one. Do not book or pay for anything." Paste it in and close the app.
2. Read the audit trail, not just the summary. When Muse reports back, open the audit trail for that task and scroll through what it actually did: which sites it opened, what it read in your email, what it drafted. Early users have reported that Muse's own chat explanation of what it accessed can be inaccurate. Trust the audit trail over the summary.
3. Verify the facts yourself. Open the calendar hold and check the time and address. Visit one of the three places' own websites and confirm the hours and price Muse gave you. Do the same for anything you will rely on later: prices, cancellation terms, and dates on every booking.
4. Tighten or loosen permissions. If Muse read more than it needed to, disconnect that account or switch it to read-only. If it did well and kept asking for drafts you had to send yourself, consider upgrading one email account to send access, with approvals still on.
5. Set up one long-running goal. Now try something that spans days. For example:

Task: Get written quotes from three [type of vendor] for [job or item] by [date].

Background: [scope, quantities, address, timing]. Use the vendors in the attached list, or find three well-reviewed ones within [distance] of [location] if the list is empty.

Ask me before you: send each first email, send any follow-up, or share my phone number.

Plan: draft the three request emails and show them to me for approval. If a vendor has not replied after 3 business days, draft one polite follow-up for my approval. When all three quotes are in, or on [date], whichever comes first, send me a comparison table with price, what is included, earliest start date, and anything unclear.

Also send me a one-line status note every Monday while this is open, even if nothing has changed.

That Monday status line matters. Muse normally checks back only when something changes, so a regular note gives you a way to notice if the task has quietly stopped.

Real Example: Booking a Conference Trip in One Brief

The principal approved a catered lunch for the January PD day: 38 staff, a $650 cap from the building's PD budget line, and a vendor that accepts a school purchase order. After dismissal you send Muse this brief:

Task: Get written lunch quotes from three local caterers for our PD day on [date].

Background: 38 staff, 4 vegetarian, 2 gluten-free. Delivery to the school office at 11:30.

Constraints:
- Budget: $650 total, including delivery and service fees
- Vendor must accept a school purchase order. No credit card deposits.

Ask me before you: send any email, send a follow-up, or share my phone number.

Deadline: comparison table by next Friday.

Muse drafted three request emails, and you approved them in one batch. Two caterers replied within two days. The third got one polite follow-up and answered on day four. The table showed $13.50, $15.25, and $16.80 a head, with the cheapest totaling $513.

That total was wrong. The cheapest caterer's quote PDF set a 50-person minimum, which pushed the real cost to $675 before delivery. Muse had multiplied by your headcount and missed the fine print. You chose the $15.25 caterer at $610 with delivery, entered the PO in the district ERP yourself, and emailed the vendor the PO number.

An office worker needs to attend a two-day industry conference in another city next month. Their employer's travel policy caps hotels at a set nightly rate, requires economy fares, and asks for bookings at least 14 days out.

Setup: Muse is connected to their work calendar and to a personal Gmail account with send access. Standing preferences include their ID name, home airport, aisle seat, and a vegetarian meal note.

Input: They send Muse a filled-in delegation brief: attend the conference on the listed dates, economy round-trip arriving the evening before, a hotel under the policy rate within walking distance of the venue, calendar holds for travel time and both conference days, a vegetarian meal request on both flights, and a dinner reservation near the hotel for the first night. The brief asks for approval before any payment and sets a deadline of Friday.

Output: Over the next day, Muse compares flights, shortlists two fares and two hotels that fit the policy, and sends one approval request with the options side by side. After they approve, it books through Expedia with a one-time card, adds the meal request, reserves dinner through OpenTable, and creates the calendar holds. The final summary lists every confirmation number and the total cost. They open the airline and hotel confirmation emails, check names, dates, and cancellation terms against the summary, and forward the receipts to their expense system themselves.

Time saved: The comparison shopping and form filling move to Muse. Their part shrinks to writing the brief, answering one approval request, and checking confirmations, usually 10-15 minutes.

What to Do When It Breaks

Three systems stay out of Muse entirely. Your SIS (PowerSchool, Infinite Campus, or Skyward) holds attendance and enrollment records. The district ERP holds purchase orders and budget lines, and the district HR system holds staff timekeeping. Muse gathers prices and quotes. You enter the PO and code the budget line, because a wrong code becomes a reconciliation headache at the district office months later.

Work email is the hard line for this role. Connect it read-only at most, and preferably not at all, because it carries parent absence explanations, student health updates, and payroll details. Ask your principal and district IT before you connect anything. Many districts require approval for new tools, so get the answer in writing. If the answer is no, use Muse for research only: let it build the vendor shortlist and draft the request emails as text, then send them from your school account yourself.

Your district's procurement policy decides which vendors count. If it keeps an approved vendor list, paste it into the brief so Muse quotes only from that list. Muse cannot log in to the district catalog, so give it those prices yourself for the comparison.

Amazon blocks Muse. For supply price checks, point it at a retail partner such as Walmart and have it return a list with links. It should never check out, since every school purchase still goes through a PO.

Keep student names out of every brief, including field trip lunch counts.

• The task stalls with no update → Check for an unanswered approval request first. Muse waits for you before any send or payment, so one missed notification can freeze a task for days. Turn on Muse notifications, or run errands from WhatsApp so approvals land in a chat you check often.
• A long-running goal goes quiet (the failure you won't see) → Connectors have been reported to disconnect without warning, and the task stops with no error message. If the Monday status note from Part 3 does not arrive, open the task, check the audit trail for the last action, and look at your connections list. Reconnect the account and tell Muse to resume from the last completed step.
• A site blocks Muse → Some retailers treat Muse as an unauthorized agent. Amazon does. Sites that need a login you have not connected will fail too. Ask Muse to use a retail partner instead, or to build the cart or list with links so you check out yourself.
• You hit the weekly token cap mid-task → The usage meter warns you before the cap. Once you reach it, Muse slows or pauses until the weekly reset. Save the delegation brief, let the task finish after the reset, or move to the Power plan if this happens most weeks.
• Muse acts on a preference that is no longer true → It remembers details you mention once and applies them later, including old ones. Tell it to forget the specific detail ("Forget that my home airport is ORD"), then give it the new one. Reread your standing preferences every few months.
• Muse read or drafted from the wrong email account → This usually means a personal and a work account are both connected, or you connected the wrong one. Check which address appears in your connections list, disconnect the account you did not intend to share, and restate in the brief which account to use.
• The summary and the audit trail disagree → Believe the audit trail. Check the booking or order directly on the vendor's site before relying on it.

Variations

• Simpler version: Skip the connectors. Use Muse only for research and comparison ("find the three cheapest refundable fares for these dates and give me the links"), then book everything yourself. You keep full control, and there is nothing to disconnect later.
• Extended version: Install the Mac app and let it fill forms from documents already on your computer, with destructive actions still requiring approval. Connect Notion and ask Muse to log every finished errand, with confirmation numbers and costs, on one page you can pull from at expense time.

What to Do Next

• This week: Run three small errands with the delegation brief. After each one, adjust the template: add the constraint you forgot, remove the approval you never needed.
• This month: List every recurring admin task you did in the last 30 days. Hand the two most tedious ones to Muse as long-running goals, and set a price watch on something you plan to buy.
• Advanced: Send Muse the saved posts, reels, or articles you have been meaning to act on, and ask it to turn each into a checklist with the purchases or bookings it needs. Approve the ones worth doing.

Advanced guide for School Office Managers who want to hand routine errands to an AI agent. Muse is free to start, and heavier use may require a paid plan.