A candidate has submitted availability, but the recruiting team still has no interview on the calendar. A custom assistant marks the task complete and sends a confirmation anyway. The problem started with a wrong assumption about what the scheduling link does. In Ashby, direct booking and candidate availability are different workflows. Choose the route before automating the email around it.
This guide covers the native scheduling distinction and a recommended design for custom AI assistance. Ashby provides the booking and availability features described here. The review, tracking, and recovery controls below are engineering recommendations for an integration, not claims about a built-in AI agent.
Choose the link by the outcome you need
Direct booking lets a candidate see available times based on interviewer calendars and meeting hours. The candidate chooses a time and books. These links are specific to the candidate, job, and interview stage. Direct booking works when the activity contains one interview event.
A candidate availability link asks the candidate to provide possible times. It does not show interviewer availability. The organizer must compare those times with the interviewing team and finish scheduling. This route is useful when the activity contains multiple interview events or the interviewers have not yet been assigned.
| Question | Direct booking | Candidate availability |
|---|---|---|
| What does the candidate see? | Available interviewer slots | A form for their own possible times |
| What happens after submission? | The selected interview is booked | The organizer still needs to schedule |
| Which activity fits? | One interview event | Useful for multiple events or unassigned interviewers |
| What should an assistant track? | Request sent, then booking state | Request sent, availability received, then organizer completion |
Configure the interview activity before adding AI
Start in the job’s Interview Plan. Add or review the schedule interview activity in the intended stage. Confirm the interview type, feedback form, panel, location, and organizer. Review meeting hours and calendar integration before testing available slots. An assistant should not fill gaps in this configuration by inventing an interviewer or promising a time.
Use an authorized account. Ashby’s documentation lists Org Admins and specified job-level Elevated Access roles for scheduling and sending links. Do not assume that access to a candidate record grants permission to manage the scheduling configuration. Test the actual role that will operate the workflow, not only an administrator’s account.
Configure the matching communication template. Ashby provides separate Direct Booking Link and Candidate Availability Link substitution tokens. A missing token value can mean that the activity or link does not exist yet. Treat that as a setup issue. Never replace a missing token with a link copied from another candidate.
Keep stage entry automation under one owner
The Automation tab on a schedule interview activity supports Automate on Stage Entry. Choose whether to send a direct booking or candidate availability link and set the corresponding email template in Communication. This can cover the normal request without a custom sender.
If you also build an external assistant, define its job narrowly. It might prepare an exception brief, identify incomplete configuration, or draft a response to a candidate’s question. It should not independently send the same initial request that the native activity already sends. Our broader interview scheduling automation guide covers ownership across calendars and recruiting tools.
Bind every request to the current activity
Store a small internal record for each scheduling task. Include the candidate, job, stage, interview activity, link type, responsible organizer, and the last observed scheduling state. Keep the actual link in access-controlled storage. Do not put candidate-specific links into shared prompts, broad team logs, or reusable templates.
Before a custom assistant recommends a send, read the current activity again through an authorized interface. The candidate may have moved stages, the panel may have changed, or a recruiter may already have sent a request. An earlier task snapshot is insufficient evidence that the request is still needed.
For a reviewed draft, bind approval to the exact recipient, link, activity, and message. If any of those change, obtain a new review under your team’s operating policy. An approval to contact one candidate should not become permission to contact every candidate entering the stage.
Handle replacements without parallel active requests
Ashby allows only one direct booking or candidate availability link to be active under a single interview activity. An Active Meeting Request already exists error should trigger inspection of the current request. It should not trigger repeated attempts to create another one.
If the team needs to change routes, cancel the existing link using the appropriate activity action before creating the replacement. Confirm which request was cancelled and which new request now belongs to the activity. Separate activities can have separate links, so identify the activity rather than blocking every scheduling request for the person.
If a custom send times out, record an uncertain outcome. Inspect the activity timeline and communication state before retrying. If you cannot determine whether the message was accepted, hand the task to the organizer. A network error alone does not prove that the candidate received nothing.
Test reminders and the organizer handoff
Ashby supports scheduling reminders for candidates who have not booked or submitted availability. The documented reminders are created when the link is sent directly through Ashby. Copying a link and sharing it outside an Ashby email does not send those reminders. Confirm the delivery route before relying on a reminder policy.
- Preview a direct booking link and check that the intended event and interviewer availability appear.
- Submit availability through the other route and verify that the organizer receives the task to finish scheduling.
- Test a candidate already scheduled before the assistant’s next check.
- Test a stage change and a replacement link while an old task is waiting.
- Test a copied link without assuming native reminders were created.
- Test an uncertain send and verify that the assistant stops rather than sending again blindly.
Use test records and controlled inboxes. Record the expected final activity state for each case. A plausible email draft is not enough evidence that scheduling works.
Common mistakes to remove first
- Using a candidate-specific link as a general sourcing link.
- Describing submitted availability as a confirmed booking.
- Running native stage entry email and a custom sender for the same request.
- Ignoring an active meeting request error and retrying creation.
- Expecting reminders after sharing a copied link outside Ashby email.
- Letting an old stage task send after the candidate has moved on.
How Remqa can help
Remqa builds AI agents for recruiting teams around the systems they already use. A useful scheduling project starts with activity configuration, clear task ownership, and tests of the final calendar state. The assistant can then handle preparation and exceptions without duplicating native scheduling. If coordinators spend time repairing these handoffs, explore recruiting workflow support and walk an engineer through one real scheduling path.