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

Events and campaign planning take about four hours of your week, and a single donor recognition event can eat four to eight hours on its own. Very little of that time goes to the part that raises money. It goes to calling three venues about one open Thursday, asking caterers for per-person pricing, rebooking a table when a major donor moves a cultivation dinner, and hunting down the registration page for the AFP conference you meant to sign up for in March. In a small shop there is often no development associate to hand it to. The person who writes the grant narrative also collects the caterer quotes.

Muse can carry those errands. Give it a date, a headcount, and a budget, and it drafts the quote requests, follows up with the venue that went quiet, and lines the options up in one table. Cultivation dinners fit well because OpenTable is one of its connectors. Conference registration does too: long forms, early-bird deadlines, and a hotel block to compare against nearby rates. You approve every send and every payment from your phone, often between donor meetings.

Keep the fundraising itself with you. Donor names, giving history, and the ask belong in your donor database and your own conversations, not in an agent's brief.

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

Your spring donor recognition reception needs a venue and a caterer, and your executive director wants options before the next board meeting. You fill in the delegation brief:

Task: Written quotes from three venues for a donor recognition reception with catering for 75 guests.

Background: A Thursday in mid-April, 5:30 to 8:00 pm, within 15 minutes of our office. Heavy hors d'oeuvres, beer and wine, one vegetarian and one gluten-free option. We are a 501(c)(3), so ask each venue about a nonprofit rate.

Constraints:
- Budget: no more than $6,000 all in, including service charge, tax, and gratuity
- Use only: venues with in-house or preferred catering

Ask me before you: send any email, pay a deposit, or mention a donor by name.

Deadline: comparison table by March 6. Draft one follow-up if a venue is silent for 3 business days.

Report back with: price, what is included, rental hours, deposit, and cancellation terms.

Your work inbox is connected read-only, so Muse showed you three drafts and you sent them yourself. Two venues answered within a day. The third, a history museum, replied after the follow-up.

Muse's comparison listed $4,950, $5,600, and $5,850. Before forwarding it, you opened the cheapest proposal. Its rental covered three hours, but setup and teardown push your event to four and a half. At $400 per extra hour, the real price was $5,550. When your director chose it, Muse asked before the $1,000 deposit, and you paid it with the organization's card.

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

Donor records never go into Muse. Giving history, pledge amounts, prospect research, and cultivation notes live in Bloomerang, DonorPerfect, Salesforce Nonprofit, or Raiser's Edge, and they stay there. Do not paste a guest list into a brief. Give Muse a headcount and dietary counts, and put only your own name on a cultivation dinner reservation.

Your work inbox holds pledge conversations, major gift asks, and grant correspondence. Connect it read-only or not at all, and ask your executive director before you connect it, because donor privacy is an organizational policy question. Keep send access off for that account. A draft Muse writes to a donor still goes out as a message from your organization.

Amazon blocks Muse. For gala decor, table numbers, or a projector, point it at Walmart, Wayfair, or Best Buy, which are Muse retail partners, or have it build a cart you check out yourself.

Watch for gifts hiding inside quotes. A caterer who offers to donate the dessert course, or a venue that waives its rental fee, is making an in-kind gift. That conversation, the sponsor recognition, and the acknowledgment letter are yours, and the gift gets entered in your donor database. Tell Muse to flag offers like that instead of replying.

Venue and catering contracts may need your executive director's signature. Muse can gather the paperwork but should never accept terms.

After an AFP conference, save the attendance record yourself if you track education for CFRE recertification.

• 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 Development Directors who want to hand routine errands to an AI agent. Muse is free to start, and heavier use may require a paid plan.