Appointment setting

The SDR booked 18 meetings last month. The AE accepted four of them.

That is not a scheduling problem. It is appointment setting done badly. The team treated a full calendar as evidence of progress, while the AE spent time with companies outside the target market, contacts with no buying role, and prospects who had agreed to a call simply to end the conversation.

Appointment setting is the part of sales development that turns a worthwhile prospect conversation into a scheduled meeting with the right sales representative. The calendar invite is the output. The real work is deciding whether the meeting deserves to exist.

Start with the reason for the meeting

A setter does not need to complete a full discovery call before booking an appointment. A cold prospect may not share their budget, procurement process, or entire buying committee with someone they have just met.

The setter does need to establish three things in plain language: why this account fits the ideal customer profile, what problem or business change makes the conversation relevant, and what the prospect wants to discuss with the AE.

The simplest test is: why this account, why this person, and why now?

For example, imagine a 180-person software company selling compliance monitoring to fintech firms. Its best customers are companies expanding into the United States, launching regulated payment products, or dealing with customer security reviews that consume engineering time.

An SDR notices that a target account has hired a chief information security officer and is recruiting for governance roles. Recent job descriptions mention SOC 2 and PCI DSS. None of that proves the company is shopping for software. It does create a reason to ask a useful question.

The first message should not be, “Would you like a demo of our compliance platform?” That jumps to a product before the prospect has acknowledged a problem. The SDR could instead ask how the new security team handles evidence collection across engineering and product.

If the CISO replies that audit requests are pulling engineers away from roadmap work, the SDR can ask a few practical follow-ups. How often does the work happen? Who owns it today? Is there a specific audit or customer review coming up? What would the CISO want to understand before involving a specialist?

At that point, suggesting a meeting is reasonable. The calendar invite should include the trigger, the current process, the people involved, and the question the prospect wants answered. “Intro call” gives the AE almost nothing. “Discuss reducing engineering time spent collecting SOC 2 evidence ahead of the Q4 customer review” gives the conversation a purpose.

The handoff matters more than the booking

An appointment setter may be an SDR, business development representative, inbound representative, or an external team operating inside the company’s process. The job title is not the important part. The handoff is.

The AE should not have to open the CRM five minutes before the call and reconstruct the conversation from scattered notes. The handoff should explain what changed at the account, what the prospect said, who else may be affected, and what the prospect agreed to cover.

This is also where multi-threading begins. The initial contact might be a security leader, while the underlying issue involves engineering, legal, finance, or an executive sponsor. The first meeting does not need every stakeholder in attendance. It should give the AE enough context to find out who else needs to be involved and why.

My view is that teams over-qualify on generic fields and under-qualify on timing. They ask whether the prospect has budget, authority, and a need, then ignore the more useful question: what event would force this problem to be addressed? A contact can have authority and still have no reason to act. A prospect with no approved budget may still be worth a meeting if an audit, renewal, launch, or regulatory deadline is close.

Inbound and outbound should not use the same playbook

Inbound appointment setting starts with an action from the prospect, such as a pricing request, product trial, contact form, or webinar registration. That action provides a starting point, but it does not automatically make the lead qualified.

Someone who requests pricing may be comparing vendors for next year. Someone who starts a trial may only be testing a feature. The setter still needs to find out what prompted the action and what the prospect expects from a conversation.

Outbound is harder because the prospect has not asked to talk. The setter has to create a credible reason to engage. Useful triggers include a funding round, a new executive hire, expansion into a new market, an audit finding, a processor change, or a major product launch.

A 70-person ecommerce company that recently moved payment processors should not receive the same sequence as a 4,000-person retailer preparing for an international launch. The account size, likely problem, contact role, and urgency are different. The cold outreach process should define those differences before anyone starts sending messages.

“Personalize every email” is not a process. A rep can mention a prospect’s recent announcement and still send the same generic pitch to everyone. A workable process names the account segment, target roles, trigger sources, message angle, number of attempts, and stop conditions.

A booked meeting can still be a bad meeting

Prospects accept calls for many reasons. They may want to learn, benchmark vendors, help a colleague, or get off an uncomfortable call. Attendance is useful, but it is not proof of intent.

The compensation plan often makes this worse. If setters are paid or praised for meetings booked, the rational response is to lower the bar. A meeting with a 30-person company outside the ICP looks identical in the activity report to a meeting with a 2,000-person target account facing a live audit.

Measure what happens after the booking. Did the AE accept the meeting? Did the prospect attend? Did the account move into an opportunity stage? Was there a next step with a relevant stakeholder? Review those outcomes by segment and source rather than relying on one blended conversion rate.

A simple feedback loop is enough. After each meeting, the AE marks it accepted, recycled, disqualified, or advanced and adds a short reason. “No current project” points to a timing issue. “Wrong segment” points to targeting. “Contact had no influence” points to role selection. Without that detail, a low conversion rate tells the team almost nothing.

Scheduling software can remove administrative work. Calendly can manage availability, buffers, conferencing links, scheduling rules, and CRM connections. It can prevent double bookings and reduce email exchanges. It cannot decide whether the account belongs on the list or whether the meeting has a credible business reason.

That judgment stays with the team setting the appointment: choose the right account, find the right contact, use a real trigger, confirm the problem, and give the AE enough context to make the meeting worth attending.