Can we put customer messages and orders in a Muse space and let it reply?
A Muse space is a screen you describe in a sentence inside the app. On 6 November 2026 Meta introduced spaces as a custom experience inside Muse. You describe an idea, such as a holiday gift tracker, a daily word game, or a planning board for the next hands-on project, and Muse builds a screen you can keep changing. You choose where it lives: the sidebar, the main tabs, hidden when you do not need it, or scheduled, so a weekly planner sits in front on workdays and weekend plans replace it on Saturday. After you have used it, you can still adjust it: add a missing field, try another look, or change how it works. Checking items off, adding notes, and editing in the space are still there when you come back. That is a panel inside the app. It is not the order admin your company already runs.
The examples that sound like a shop are on Meta’s list of ideas. The subject is the usage they sketched, not a connector already wired to your system. An order tracker for a small business shows new orders, customer messages, and what needs to ship today, on one screen. A shopping hub pulls holiday and birthday gift ideas, wish lists from Instagram saves, Marketplace listings, and buyer messages into one view. They also name a school dashboard that lifts events out of school email onto a calendar, a music tracker, a wedding planner with the RSVP list and vendor invoices, a trivia game, a podcast studio, a client hub for freelance projects and deadlines, and a trip planner. Once you connect apps you already use, the space updates itself in the background, so new concert dates, price changes, or savings progress show up without a fresh question. A background refresh means the screen fills in changes from those apps. It is not permission to send a message to a customer, and it is not permission to mark an order shipped.
Sharing has not become an editor you can hand to the whole shop. The close of the post says spaces are available, from that day, everywhere Muse is available, and that Meta is exploring ways to share a space with other people for a more collaborative experience. Exploring is their next step. It is not a collaborative editor that has shipped. A slide cannot rewrite that sentence as “the whole company signs into one space and lets it answer customers for the person on duty.” The Taiwan LINE Official Account is not in this product either. Where Muse stood before, and which connectors it named, is the earlier note on whether Muse can be the company assistant. If the sign-in screen says this place is not open yet, the app is not your support desk, and it is not your shipping desk.
The 29 September sentence was not withdrawn. Muse for Small Business says nothing publishes, sends, or spends without your approval. The 6 November spaces post does not take that back, and it does not say that spaces, or voice, cancel it. Do not put on a slide that the new feature means approval is gone. A person still presses send. A customer message that asks to change an order is still not a signature. That is the note on a customer’s AI is not a signed order. Building a space on your side and dropping customer messages into it does not sign those messages as safe to answer automatically, or safe to ship against.
So the live orders and the live messages do not get connected in a way that replies or ships by itself. Do not give a Muse space the order database that is still taking orders, and do not connect the channel where customers write to you so the space answers them or marks orders shipped. A person can describe a planning board and look at a list, a draft, and a to-do that a person assembled. If someone needs to see which orders matter today, a person queries or exports them from the admin you already use, and a person decides which shipment goes out and which reply is allowed to send. If a background update would change a public price or send text to a customer, do not turn that connection on. Prices and delivery dates may quote only sentences you have already published on the service page. A price change that appears inside a space is Meta’s example of an app refreshing. It is not a license for the model to change what you charge.
What the shop can do this week stops at a person pressing send. First see whether Muse is actually open where you sign in. If it is not, do not export the customer list or the orders just to get around that. If it is open, keep drafts on the step that still needs a person to send. The Official Account keeps the path you already have, where a person has looked before anything goes out. We do not install a Muse space as an order desk with nobody watching, and we do not rewrite “exploring sharing” as a shop-wide permission for it to answer LINE.
A message that would let the space reply, and a slide that treats exploring as a shared editor
On Friday the shop owner wrote: “Build a Muse space, put customer messages and orders in it, and let it reply and tick off what has to ship today.” Orders still live in the existing admin, and the LINE Official Account is not Muse. The person responsible answered the same day: a space can be a draft board a person reads. Sending and shipping stay with the person on duty. The live order database and the customer messages are not connected. That space did not become the order desk.
Another slide said “spaces can be shared, so the whole shop uses one screen and lets it answer LINE,” and the source line only cited 6 November. The person responsible changed the sentence back to Meta’s “exploring,” and added that this is not a collaborative editor that has shipped, and it is not Taiwan LINE. The 29 September line, nothing publishes, sends, or spends without approval, stayed on the slide. That page no longer treats an unshipped sharing idea as a customer message that sends itself.
Replies a customer can see still go out from a person, under AI customer support. Lookup, notification, and aggregation under rules you have written sit in AI agent introduction and deployment. Neither item includes giving the live order database or customer messages to a Muse space so it replies or ships on its own.
FAQ
May a space reply to customer messages on its own?
If a person does not press send, it does not go out. On 29 September Meta wrote that nothing publishes, sends, or spends without approval. The 6 November spaces post does not take that sentence back. Do not connect customer messages so the space replies by itself.
May we connect the live order database and let it ship?
No. The order tracker in the announcement is an example of a space, not a connection to your live orders. Do not give it the order database, and do not let it mark goods as shipped on its own. A person still ships and a person still replies.
If the whole shop shares one space, can it answer LINE?
Meta says it is exploring ways to share spaces. That is not a shipped collaborative editor. Spaces are available where Muse is available. They are not the Taiwan LINE Official Account. A shared box on a slide is not a send button.
A person still sends the reply Lookup, notify, aggregate
Source: Meta, 2026-11-06, Muse spaces. Nothing publishes, sends, or spends without approval is in the 29 September 2026 post. The 6 November post does not withdraw it. Sharing spaces is described as exploring, not as a collaborative editor that has shipped.