An Executive Assistant Scheduled the LinkedIn Meeting: Verify Authority and Context

You accepted a LinkedIn connection. A few messages later, an executive assistant sends a calendar invite for a video call with the leader you originally spoke to. The meeting lands on your calendar, but you are not sure: will the assistant join? Who owns the agenda? Where does follow-up go after the call?

This scenario is common in sales, partnerships, and vendor conversations. Executive assistants coordinate schedules, send invitations, and manage logistics. Their role is operational support, not decision-making authority. Knowing who owns the meeting's purpose, who should attend, and which contact handles post-meeting follow-up prevents miscommunication and wasted time.

Is the assistant a participant or only a scheduler?

Not every assistant who sends an invite will join the call. Some coordinate logistics and hand off the meeting to the executive. Others attend to take notes, manage the agenda, or handle technical issues during the call.

If the invitation does not clarify the assistant's role, ask directly before the meeting. A short reply confirming attendees avoids confusion when the call starts. For example: 'Thanks for scheduling. Will you be joining, or is this a meeting with [executive name] only?'

When the assistant does join, they often manage time, capture action items, and coordinate follow-up. They may not answer strategic questions or make commitments on the executive's behalf. Save technical and operational questions for them; save strategic decisions for the executive.

Who confirms the agenda and attendees?

A meeting invitation from an assistant should include the agenda, expected attendees, and the meeting's purpose. If any of these are missing, request them before the call. Meetings without clear objectives waste time for everyone.

Confirm the executive will attend. Assistants sometimes send invitations before final confirmation, especially when juggling multiple schedules. If the agenda shifts or the executive cannot attend, you want to know before you spend time preparing.

Review the attendee list. If you expected a one-on-one conversation but the invite includes unfamiliar names, ask who they are and what role they play. Large meetings require different preparation than focused discussions.

Which contact owns follow-up after the meeting?

After the call, you will need to send materials, answer questions, or coordinate next steps. Identify the correct contact before the meeting ends. Ask: 'Should I follow up with you directly, or will [assistant name] coordinate next steps?'

Some executives prefer all external communication to flow through their assistant. Others handle follow-up directly. Knowing the preferred route prevents delays and ensures your message reaches the decision-maker.

If action items are assigned during the meeting, confirm ownership and deadlines before closing the call. The assistant may document these, but the executive or another attendee usually owns execution. Clarity here prevents dropped tasks and repeated follow-up.

How business email compromise exploits assistant-scheduled meetings

Business email compromise (BEC) scams frequently impersonate executives and their assistants. Attackers research targets, mimic writing styles, and send urgent requests that appear legitimate. According to the FBI Internet Crime Complaint Center, BEC scams resulted in $2.4 billion in adjusted losses in 2022, representing 35% of all reported losses that year.

These scams often involve fake meeting requests. An attacker impersonates an assistant, schedules a call, and then claims last-minute audio issues. They pivot to text or email and request sensitive information or urgent wire transfers. Microsoft Security documentation notes that BEC attacks use familiarity and trust to bypass scrutiny, especially when impersonating authority figures.

Red flags include sudden changes to meeting format, urgent financial requests through unofficial channels, and pressure to act quickly. Proofpoint reports that 82% of data breaches in Verizon's Data Breach Investigations Report involved the human element, with attackers using social engineering to trick people into sharing credentials, sending money, or providing access to systems.

Verify unusual requests before acting

If an assistant sends a meeting request that feels off, verify it. Check the sender's email address carefully. Attackers use lookalike domains or spoofed display names that appear legitimate at first glance.

Contact the executive or assistant through a separate, verified channel. Use a phone number from the company website or a previous verified conversation, not the one in the suspicious email. Ask: 'Did you send a meeting request about [topic]?'

Microsoft Learn documentation on external bots in Teams recommends that organizers require approval before admitting participants detected as bots to meetings. While this guidance applies to platform-level controls, the principle extends to human verification: treat unexpected or urgent meeting requests with caution, especially when they involve financial or sensitive topics.

A checklist for assistant-booked LinkedIn meetings

Use this checklist to prepare for and verify meetings scheduled by executive assistants:

• Before the meeting: Confirm the assistant's role (participant or scheduler only).
• Before the meeting: Verify the executive will attend and review the attendee list.
• Before the meeting: Request a written agenda if the invitation does not include one.
• Before the meeting: Check the sender's email address for lookalike domains or spoofing.
• During the meeting: Clarify which contact owns post-meeting follow-up and decisions.
• During the meeting: Confirm action items, owners, and deadlines before closing the call.
• After the meeting: Verify urgent or unusual requests through a separate, trusted communication channel.
• After the meeting: Document what was agreed and send it to the confirmed follow-up contact.

How comment-led outreach reduces verification friction

When you build familiarity before sending a connection request on LinkedIn, the recipient recognizes your name. That recognition makes verification easier. They are less likely to question whether your message is legitimate because they have seen you show up consistently in their feed.

Comment-led outreach creates this familiarity. You comment on the buyer's posts over days or weeks. When you connect and eventually schedule a meeting, there is context. The recipient knows who you are and why you are reaching out. This reduces the likelihood that your meeting request triggers suspicion or requires additional verification steps.

For executive assistants managing inbound meeting requests, familiarity signals legitimacy. When the executive recognizes the requester's name from their LinkedIn activity, the assistant can schedule with confidence. This makes the meeting logistics faster and reduces friction for everyone involved.