What an assistant is actually good for in field service
Be skeptical of the demo videos, including ours. The question is not whether talking to your phone is impressive. It is which parts of running a crew are faster by voice than by thumb, and the honest answer is the parts where your hands are busy and the answer is short.
A morning with an assistant connected looks like this. In the truck: "what does my day look like," and the schedule reads back while you drive to the first job. Mid-morning, a client calls asking to squeeze in a visit, so while you walk the property you say "create a job for Maria Lopez tomorrow at 9 for a move-out deep clean," and it is on the board before you are back at the tailgate. After lunch: "put Mike on the 2 o'clock," and the dispatch happens without opening anything. End of day, parked outside the supply house: "who still owes me money," and the unpaid invoices read back oldest first.
None of those beat a laptop at a desk. All of them beat a phone held with wet gloves. That is the whole pitch, and it is enough.
Directory connectors and custom connectors are different doors
Muse launched at the end of September 2026 and opened its connector platform to outside developers within days.1 There are two ways a tool shows up inside it.
Directory connectors are the ones listed inside the app. Meta reviews each one for function, security, and legal requirements before it appears, and the review runs in waves. The launch directory is strong on office software: email, calendars, documents, accounting, payments. It is empty where the trades live. As of October 2, independent tracking counted 58 live connectors and 18 announced, with nothing dedicated to field service among them.2
Custom connectors are the door anyone can use today. A Muse user can point the assistant at any hosted MCP endpoint, supply a credential, and start working. Meta does not review custom connectors, so the trust decision is yours: only connect services you already trust with the same data.3 MCP is the Model Context Protocol, an open standard for connecting tools to AI assistants, and it is the same mechanism Claude and ChatGPT use. A service that exposes one endpoint works across all three.
The practical consequence for a small operator: you do not have to wait for the software you use to win a review queue. If it has an MCP endpoint, you can connect it this week.
Connecting EosLog to Muse, step by step
EosLog's connector is live at https://eoslog.com/mcp. Our directory submission is in Meta's review queue; until it clears, the custom connector path below works for any account.
- Get a connector token. In EosLog, open Settings and then the AI Connectors tab, name the token after where it will live, and copy it when it appears. Tokens are shown once, created only by admins and managers, and revocable any time.
- Add a custom connector in Muse. In the Muse app, open the connectors settings and choose to add your own. Give it the endpoint
https://eoslog.com/mcp. - Supply the credential. Muse asks for the token through its credential prompt, not in the chat itself, and stores it on your device's side of the connection. The token travels as a bearer credential in the request header.
- Say something. "What does my day look like" is the test we suggest first, because it proves the schedule read end to end without changing anything.
The full tool list is on the connector documentation page. The short version: today's snapshot, schedule reads, job detail, job creation, crew assignment, unpaid invoices, invoice drafting, and invoice sending.
If you run different software
The steps above are EosLog specific, but the shape is universal, so here is the version to take to whatever vendor you use. Ask two questions: do you have a hosted MCP endpoint, and how do I get a credential for it. If the answer to the first is yes, the Muse side is identical: add a custom connector, paste the endpoint, supply the credential when prompted. If the answer is no, the honest timeline is unknowable, because an MCP server is real engineering work that has to be scoped, secured, and hosted, and most vendors are deciding right now whether the demand justifies it.
One warning while the ecosystem is young: an MCP endpoint holds the keys to whatever it can touch. Do not paste credentials for your business software into endpoints you found on a list somewhere. The vendor's own domain, documented on the vendor's own site, is the standard to hold out for.
What to let an assistant do, and what to keep behind a click
We built the EosLog connector read heavy on purpose, and we would give the same advice whatever software you run. Reads are free: letting an assistant tell you about your schedule or your receivables risks nothing. Writes deserve a hierarchy.
Creating a job is low stakes, because an unwanted job is a thirty second fix. Assigning a worker is low stakes for the same reason. Sending an invoice is different: that is an email to a real client with a payment link in it, and a mistake is a conversation you have to have. Our connector will send an invoice when asked, but the habit we recommend is saying the invoice number back before you confirm, the same way you would read a phone number back before dialing it for someone.
Two guardrails worth checking in any connector before you trust it with a business: every request should be scoped to your own company's records, and the credential should be revocable without a support ticket. If a vendor cannot answer how those two things work, keep it read only.
What this costs
On the EosLog side, nothing beyond the plan you already have. The connector is included on every plan, including the free one, and free plan accounts keep their normal monthly caps on job and invoice creation. On the Meta side, Muse is its own product with its own pricing, and that is between you and Meta. EosLog serves US businesses only, which matches where Muse launched its connector push.1
Questions operators have asked us
Does this work before EosLog appears in the Muse directory?
Yes. The custom connector path does not depend on the directory at all. The directory listing, when review clears, mostly changes discovery: people will find EosLog inside Muse instead of needing this guide.
What happens if I say a client name that matches two people?
The connector refuses to guess. It lists the matching clients with their ids and asks the assistant to retry with the exact one. The same rule applies to worker names. Slightly slower, never wrong about who gets dispatched or billed.
Can my crew use it, or just me?
Connector tokens are limited to admins and managers for now. A worker's day runs through the mobile app. If a token holder is demoted, their token stops working immediately.
Run the day from wherever you are standing
EosLog is field service management for small US service businesses: scheduling, dispatch, quotes, and invoices that get paid. The Muse connector is included on every plan.
Already have one? Read the connector docs or ask us for a token. You can also try the free quote generator with no account at all.
Sources and further reading
- CNN Business, Meta wants Muse to be part of your everyday life (September 24, 2026 announcement of Muse and its device lineup at Meta Connect).
- Postfast, Meta Muse Connectors: The Full List, With Sources (independent weekly tracking of live and announced directory connectors; 58 live and 18 announced as of October 2, 2026, none dedicated to field service).
- Parallel, Meta Muse Custom Integrations: Connect Any API or MCP (how custom connectors work, credential handling through Muse's credential prompt, and the trust model difference from reviewed directory connectors).
- Meta, Muse Connector Platform (the developer submission process: describe the product, submit for functional, security, and legal review, appear in the directory).
The Muse connector ecosystem is days old and moving quickly. Directory counts, review timelines, and feature availability in this guide are accurate as of October 3, 2026 and will drift; the linked trackers are updated more often than this page. Nothing here is affiliated with or endorsed by Meta.