Scheduled Calls lets your customers book a future video meeting with one of your agents, receive reminders, and join the meeting when the slot arrives — all tied to an ApifyCloud video app.Documentation Index
Fetch the complete documentation index at: https://docs.apifycloud.io/llms.txt
Use this file to discover all available pages before exploring further.
What it is
A scheduling layer that sits on top of Video. Instead of joining a call right now, a customer books a time; an agent is assigned; both sides get the same meeting link when the time comes.- Bookings can be created by agents, admins, customers (via a public page), or an external system (via the API).
- Availability is driven by each agent’s working hours, with exceptions and ad-hoc “do not disturb” windows.
- Reminders are sent automatically before the meeting.
- Status of every booking is tracked through a full lifecycle (scheduled → confirmed → started → completed, or cancelled / no-show).
The meeting itself uses the exact same Video runtime described in
Video — Overview. Scheduled Calls adds the
“when” and the “who” on top; the actual room is the same one the
customer would enter from an instant link.
When to use it
Scheduling is a fit whenever the call can’t (or shouldn’t) happen the moment the customer clicks:Sales demos
High-AOV or consultative sales that require preparation on
both sides.
Onboarding & KYC
Scheduled document review, identity verification, or guided
setup.
Consultations
Healthcare, legal, or advisory sessions delivered remotely.
Tier-2 support
A follow-up slot after a front-line ticket gets escalated.
How it fits together
Customer books a time
Through the public booking page, an agent-assisted flow, or an
external system calling the API.
An agent is assigned
Either explicitly (URL-forced or customer-picked) or
automatically from the pool of available agents.
Reminders go out
Invitation on booking, plus reminders at configured intervals
before the meeting (24h / 1h / 15m by default).
Both sides join the same meeting
When the slot arrives, the customer opens their reminder link
and the agent opens theirs — they land in the same Video
meeting.
What you bring vs. what ApifyCloud brings
| Responsibility | You | ApifyCloud |
|---|---|---|
| Agents (users with access to the video app) | ✅ (in console) | |
| Working hours, exceptions, DND | ✅ (in console) | |
| Scheduling preset configuration (reminders, limits, channels) | ✅ (in console) | |
| Destination for reminders (customer’s phone, email) | ✅ | |
| Public booking page, console booking UIs | ✅ | |
| OAuth-gated API | ✅ | |
| Reminder dispatch, retries, status tracking | ✅ | |
| Outbound webhooks to your systems | ✅ | |
| Integration with the Video runtime | ✅ |
What’s next
Booking surfaces
The four ways a booking can be created.
Agent availability
Working hours, exceptions, and do-not-disturb windows.
Reminders
What gets sent, when, and through which channel.
Webhooks
Lifecycle events pushed to your systems.