Meta presents Muse as an artificial intelligence agent capable of sending emails, preparing shopping lists, or calling a company to complete a task on our behalf. But Reuters reveals that the company also tested a system called a "human concierge": subcontractors could handle certain calls that users thought they were entrusting to their digital agent. The trial was reportedly suspended following internal privacy concerns. This case raises a simple question: when a service presents itself as AI, must it clearly state that a human can access our request?<\/p>\n
Launched by Meta on September 8, 2026 in the United States, Muse is presented as a personal agent, not a simple chatbot. The difference lies in the action. A chatbot answers a question; an agent receives an objective, prepares several steps, and uses digital services to achieve it.<\/p>\n
According to Meta, Muse can help users organize their calendars, send messages, plan trips, search for products, or turn long-term goals into action plans. The service is accessible through a dedicated app and can also interact with users within WhatsApp.<\/p>\n
To accomplish these tasks, the agent needs access to more information than a typical search engine: contacts, calendar, emails, preferences, purchase history, or project-related data. The more useful the assistant becomes, the more crucial the issue of confidentiality becomes.<\/p>\n
Making a phone call seems simple for a human, but it's a complex task for a machine. The agent must understand the request, dial the correct number, get through a switchboard, explain the reason for the call, interpret an unexpected response, and sometimes negotiate or confirm an expense.<\/p>\n
According to internal documents seen by Reuters, Meta experimented with a "human concierge" to study the reactions of people who did not want to speak directly to an AI. Call center employees could then discreetly make certain communications to book a service, check stock levels, or request a price.<\/p>\n
Human intervention can also help prevent the failure of a still-imperfect product. When an agent doesn't understand a user or encounters an unusual procedure, an operator can complete the task. This method is sometimes used in emerging digital services to test a feature before fully automating it.<\/p>\n
A hybrid service is not automatically problematic. Many companies combine software and human intervention. An anti-fraud system can forward a case to an analyst; a medical assistant can have an alert reviewed by a professional.<\/p>\n
The difference lies in consent. If a person asks an AI to call a clinic, an insurance company, or a bank, they may be transmitting information they wouldn't have shared with an unknown operator. Therefore, they need to know whether their request will be processed by a computer system or if a subcontractor will be able to listen to, read, or rephrase it.<\/p>\n
Reuters reports that Meta employees were concerned about the potential transfer of sensitive data to call centers. The test was subsequently suspended. This suspension does not mean that all Muse calls were handled by humans, nor that the system is still in use today. It does, however, highlight the need to clarify the line between automation and human assistance.<\/p>\n
A voice agent combines several technologies. A model transforms the user's request into an action plan. A speech synthesis system pronounces the sentences. Speech recognition transcribes the user's responses. Finally, the model chooses the next action: asking a question, accepting a proposal, requesting clarification, or soliciting the user.<\/p>\n
Each step can fail. A product name might be misunderstood, the price might change, an important condition might be overlooked, or the agent might approve an expense without fully understanding the answer. To mitigate risks, the user must be able to define rules: maximum amount, prohibited information, mandatory validation before payment, and limited data retention.<\/p>\n
The real issue isn't whether humans have definitively disappeared from customer service. It's who is acting, with what data, and under what responsibility. An agent can be very convenient while remaining a hybrid. But the user must be able to distinguish between automated actions, human intervention, and decisions that involve their money or identity.<\/p>\n
Meta's promise\u2014a personal AI capable of acting in the real world\u2014will only be sustainable if trust accompanies automation. Otherwise, every spectacular demonstration will raise the same question: is it really the AI doing the work, or someone behind the scenes?<\/p>\n
No. Reuters describes a test involving a human reinforcement system. The available information does not allow us to confirm that all calls were affected.<\/p>\n
According to Reuters, the test has been suspended. This experiment should be distinguished from Muse's other automated features.<\/p>\n
The initial announcement was for the United States. Availability, features, and privacy policies may vary by country.<\/p>\n
Meta tested a "human concierge" for some calls from its AI agent Muse. Who could access the requests and what guarantees were in place for users?<\/p>","protected":false},"author":5,"featured_media":6975,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":true,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_hide_featured_image":false,"_jetpack_featured_image_duplicate_dismissed":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[3,4,10],"tags":[],"class_list":["post-6967","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-actus","category-intelligence-artificielle","category-tech"],"acf":[],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t