Can Meta Muse calls chase your job applications?

What can Meta Muse calls actually do for a job seeker?

Meta Muse calls let paid subscribers have Meta's AI agent phone a US business for them. Afterward, Muse sends back a transcript and a summary of the call. Meta started testing calling in September 2026, and as of November 12 every paid subscriber can use it. Free users can't. Paid plans start at $20 a month on the Power tier, and heavier users can pay $100 a month for Maximum. Meta hasn't announced a separate per-call fee. Muse launched on September 8, and Meta says it now has more than 10 million users. For job seekers, that means a tool many of you already use to draft cover letters can now pick up the phone and chase an application while you're stuck in a meeting.

The limits matter more than the launch headline. Muse can only call US businesses, there's no sign of international calling, and it can't receive calls. So it won't wait around for a recruiter to call back. Calling was built for chores like booking appointments, checking stock and collecting quotes, and it shows. Muse is good at short, structured questions where the answer is a yes, a no or a date. It's weak at anything that needs judgment, rapport or a follow-up question you didn't see coming. Some job-search calls fit the first description and plenty fit the second, so the rest of this guide sorts one from the other.

There's also some history to know before you give Muse your name and an employer's number. During testing, Meta passed some calls to human contractors without telling the person on the other end. On one of those calls, a contractor reportedly made an offensive remark. Meta says it has stopped using contractors on calls and that the feature will only run with proper disclosures. That doesn't make Muse unsafe for a quick status check. But anything the agent says, it says in your name. If you're already weighing how much of your career data to give Meta, our breakdown of what Muse should and shouldn't see from your CV covers the privacy side in detail.

Which job-search calls are worth handing to Muse?

The calls worth handing over are short, factual and low-stakes: asking a small business whether a role is still open, confirming an interview time or address, or checking that a mailed application or portfolio arrived. Each has one clear answer, the person who picks up can give it in under a minute, and nobody is judging your personality from the exchange. Dental practices, family-run restaurant groups, regional logistics firms and independent retailers often post jobs with no applicant portal at all. Hiring there means a manager and a phone. A polite call asking, 'Is the front-desk role you posted last week still open, and how should applicants send a CV?' really does help, and Muse can make it while you work your current shift.

Interview logistics are the second good fit. Say you've got an in-person interview on Thursday and the confirmation email didn't mention parking, which entrance to use, or whether to bring printed copies of your CV. A receptionist can answer that in thirty seconds, and you get a written transcript to check on the train. The same goes for rescheduling when the employer has explicitly said to call the front desk. Be specific in your instruction. Name the role, the interviewer if you know them, the date, and exactly what you need confirmed. A vague request like 'call them about my interview' leaves the agent to improvise, and that's where AI calls go wrong.

Status follow-ups are a judgment call. If a small or mid-sized employer told you to expect a decision by Friday, a call the next Tuesday asking whether the process is still running is fair. At a large company, it mostly wastes your plan's allowance. Corporate recruiters rarely publish direct lines, and the person on the main switchboard can't see the applicant tracking system. You'll be told to 'check the candidate portal.' Our take: if the job ad sent you to a portal, the phone is the wrong channel, whether a human or an AI makes the call. Send the recruiter a short email instead, and save Muse for employers that actually hire over the phone.

Which calls backfire when an AI agent calls an employer?

Cold-pitching a hiring manager through Muse is the call most likely to backfire, closely followed by negotiating pay through a bot. A cold call only works because a real person shows initiative, warmth and quick thinking in the first few seconds. When an AI voice opens with 'I'm calling on behalf of Priya, who's interested in your marketing role,' the hiring manager learns the one thing you didn't want them to know: you didn't call yourself. Early users already report businesses hanging up the moment they realize an AI is on the line. A hiring manager sorting through fifty applicants has even less patience than a cable company's front desk.

Salary negotiation is worse, and we'd never hand it to an agent. Negotiating means reading the other side as you go: where they hesitate, the budget they hint at, the perk they offer when base pay is capped. An agent following a script can't trade a signing bonus for a later start date. It won't pick up on a hint like 'the band is fixed, but the title is flexible.' It can also agree to something you never would and you'd only find out from the transcript. At the offer stage, the employer is deciding whether you'll be a good colleague, and handing that conversation to software sends the wrong signal. The same goes for accepting, declining or withdrawing. Do those yourself.

The quieter mistake is volume. When calls cost nothing beyond your subscription, it's tempting to have the agent ring every employer you applied to last month. Don't. Recruiters remember names, and a pattern of automated calls makes you look either desperate or like you're applying everywhere. It also hides the real problem. If twenty applications got zero replies, a phone call won't fix that. The bottleneck is almost always the CV or the fit, not the employer's inbox. Save calls for a handful of strong, well-matched applications where one factual answer moves you forward. They're no substitute for better applications.

What does the employer hear when Muse calls?

The employer hears an AI voice calling on your behalf, and so far it hasn't always been clear that it's an AI. One early published transcript had the agent introduce itself with a human first name and say it was calling for a user. Other testers said businesses hung up as soon as they heard it was an AI. Meta says calls will carry proper disclosures, but it hasn't published a detailed script. So assume whoever picks up will quickly figure out they're talking to software, and plan your request around that. A call that sounds like a polite, efficient assistant gets answered. A call that seems to be pretending to be you gets hung up on.

The fix is simple: tell the agent to say it's an AI at the start of the call. Put it in your request, along these lines: 'Say you're an AI assistant calling for Jordan Lee, who applied for the warehouse supervisor role on October 30. Ask only whether interviews have been scheduled yet. If they ask anything else, say Jordan will email them today.' That last line matters. It gives the agent a polite way out, so it doesn't guess at your notice period or make up a salary expectation. It also respects the employer's time, which is what you'd expect from a human assistant too. Then read the full transcript before you act, because the summary can leave out details the receptionist actually gave.

Be careful about what you put in the request itself. The agent needs your name, the role and perhaps the date you applied. It doesn't need your phone number read aloud, your current employer, your home address, or anything from your CV beyond what identifies the application. Keep in mind that Muse transcribes these calls, and the person you're calling only agreed to answer a quick question. If Muse is the hub of your search, keep employer contacts, call notes and CV versions organized in one place. Our walkthrough on setting up Muse as a job-search workspace shows how to set that up without pasting sensitive details into every chat.

Why does your CV matter more than the follow-up call?

A follow-up call only works if the CV it points to holds up, because every call ends with someone opening your application. When a receptionist says 'let me check,' or a hiring manager pulls up your application after hearing your name, they see what the applicant tracking system parsed and what your CV says in the first ten seconds. A call can push your application to the top of the pile for a moment. It can't make a weak CV strong. It can even draw attention to a CV that was quietly filtered out for a reason, like a two-column layout the system scrambled or a skills section missing the tools the ad asked for.

That's why the order matters: fix the CV, then follow up. Before you let any agent call an employer, run your CV through a free HRLens analysis. The free version gives you an overall score out of 100, five category scores (including ATS compatibility and clarity and structure), your strengths, and a visual layout analysis. Paste in the job description and the analysis lists the skills you're missing for that role. It also generates ATS-friendly rewritten versions of your CV in six templates that use the job's keywords. The paid Full Analysis adds a fix list, the reasons you might be rejected and an estimate of your hiring chances for $3.99, a fraction of a month on a paid Muse plan.

Here's the workflow we recommend. First, pick the three to five applications you care about most. Second, check whether your CV matches each job description and fix the gaps before anyone looks again. Third, wait until the employer's timeline has passed. Calling early looks impatient, no matter who dials. Fourth, use Muse only for the factual calls described above, with a clear AI disclosure and a scripted way out. Fifth, read every transcript, and follow up yourself by email whenever a real conversation opens up. In that order, the agent handles the logistics while your CV does the persuading, which was always its job.

Frequently asked questions