Specialist sales development role

Meeting coordination

Coordinate calendars and preserve the context around qualified conversations.

Audience and problem

Where this role creates useful capacity.

Built for: Sales teams that need consistent scheduling, reminders, ownership, and meeting context across handoffs.

Qualified conversations are weakened when calendar ownership is unclear, required context is missing, reminders use the wrong message, or outcomes never return to the CRM.

Inputs required

Approved scheduling rules and calendars
Required meeting context
Reminder and rescheduling templates
No-show and escalation playbook

Scope of work

Coordinate available times
Prepare meeting briefs
Send approved reminders and rescheduling messages
Record scheduling and attendance outcomes

Working sequence

A workflow the owner can inspect.

Confirm qualification and the correct meeting owner.
Offer approved availability using the defined calendar path.
Prepare the context brief and approved reminders.
Record outcomes and route no-shows or conflicts.

Deliverables

Confirmed calendar event
Seller meeting brief
Reminder and rescheduling record
Outcome and exception update

Owner decision boundaries

No promises about pricing, fit, availability, or outcomes.
No qualification override or calendar access beyond the approved scope.
Commercial decisions remain with the meeting owner.

Quality controls

Owner and timezone verification
Required-context checklist
Reminder-template check
Outcome reconciliation

Operating examples

How the boundary works in practice.

Multi-owner routing

The assistant applies the approved territory and availability rules, then escalates collisions rather than choosing an owner informally.

No-show recovery

The approved recovery message is sent and the result is recorded without changing opportunity status beyond the rule.

Role questions

Frequently asked questions

Can the coordinator decide who is qualified?

No. The role can check required fields and route according to rules, while the sales owner controls qualification.

What belongs in the meeting brief?

Include verified account context, stated need, source links, prior interactions, open questions, and the responsible owner.

Related services

Connect the adjacent handoffs.

Create a controlled first workflow

Turn this scope into a role brief.

Bring the queue, systems, current owner, and known exceptions.

Plan a consultation