Requested Meeting
In Salesforce Scheduler, an appointment request created when a customer or agent selects a desired time slot, which may require confirmation or assignment before becoming a confirmed appointment record.
Definition
In Salesforce Scheduler, an appointment request created when a customer or agent selects a desired time slot, which may require confirmation or assignment before becoming a confirmed appointment record.
In plain English
“A Requested Meeting in Salesforce Scheduler is an appointment request created when a customer or agent picks a desired time slot. It may require confirmation or assignment before becoming a confirmed appointment. So it's the pending state before the meeting is actually booked.”
Worked example
A customer of Nighthawk Aerospace, a private-jet charter, browses the company's Experience Cloud booking site to schedule a charter consultation. She picks a time slot through Lightning Scheduler; the system creates a Requested Meeting record - the appointment exists, has a date and time and customer attached, but is in pending status because charter bookings require manual confirmation by an account manager who reviews aircraft availability and customer KYC. The account manager confirms the request the next morning, and the Requested Meeting becomes a confirmed Service Appointment with a flight-crew assignment. Without the Requested Meeting state, the customer would either get an instantly-confirmed time the company can't actually staff, or wouldn't be able to self-serve at all.
Why Requested Meeting matters
In Salesforce Scheduler, a Requested Meeting is an appointment request created when a customer or agent selects a desired time slot, which may require confirmation or assignment before becoming a confirmed appointment record. The request captures the desired time and topic but isn't yet a committed appointment: assignment logic may need to route it, or an approver may need to confirm it.
Requested meetings support scenarios where appointments need workflow before being finalized: assigning the right specialist, confirming availability, requiring approval for premium appointments. Without this intermediate state, you'd have to either commit immediately (which might assign the wrong person) or manage the pending state outside Salesforce. Mature scheduler deployments use requested meetings thoughtfully where workflow matters.
How organizations use Requested Meeting
Uses requested meetings for specialist appointments that need routing to the right provider before confirmation.
Treats requested meetings as a workflow step for premium advisor appointments requiring approval.
Matches requested meeting usage to scenarios where workflow adds value.
Trust & references
Straight from the source - Salesforce's reference material on Requested Meeting.
- Manage Appointments with Salesforce SchedulerSalesforce Help
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What is a Requested Meeting?
Q2. When should you use this intermediate state?
Q3. What happens after confirmation?
Discussion
Loading discussion…