Overview
This document maps every major end-to-end workflow in the platform. For each workflow, it covers the entry point, step-by-step progression, user and system actions, key decision points, and what happens when things go wrong.1. Hiring Pipeline
How Candidates Enter
- Job posting page — Candidate views a public job listing and clicks “Start Application”
- Direct link — Candidate uses a registration link shared by the company
- Custom link — A unique link generated by the admin for targeted outreach
- External API — Application created by an external system
- Bulk import — Applications imported in bulk by an admin
Step-by-Step
Key Decision Points
- Compliance rules on each page can redirect the candidate to rejection, waiting list, manual review, or the next stage
- Recollection can be triggered at any point, requiring the candidate to re-submit specific documents or fields before continuing
- Language preference — if the flow requires a preferred language and one hasn’t been set, the candidate is redirected to select one
- Phone number — if phone collection is required and the candidate hasn’t provided one, they are redirected to their profile
What Happens on Failure
- Network error during submission — The form preserves the candidate’s current input
- Compliance rule failure — The candidate is blocked from advancing until the issue is resolved
- Invalid document — Validation error is displayed and the candidate can retry
- Session expiry — The candidate is redirected to log in and resumes where they left off
2. Automation Execution
How Automations Are Triggered
| Trigger | What Starts It |
|---|---|
| On Change | A field value changes (e.g., application moves to a new stage) |
| Schedule | A recurring timer fires (daily, weekly, monthly, etc.) |
| Webhook | An external system sends an HTTP request |
| External API | An application is created via API |
| Form Submission | A specific form element is submitted |
| Recollection | A recollection event occurs |
Step-by-Step
- Trigger fires — The system detects the triggering event
- Active check — The automation is verified to be active
- Concurrency policy applied:
- Queue — Wait for any running instance to finish
- Skip — Ignore if already running
- Continue — Run immediately alongside others
- Conditions evaluated — Branch and filter nodes are checked
- Actions executed — Each action runs in sequence (email, status update, webhook, etc.)
- Results recorded — An execution record captures status, timing, and per-action results
What Happens on Failure
- Action failure — The error is logged; depending on configuration, subsequent actions may still execute
- Webhook timeout — The backend retries according to its retry policy
- Invalid data reference — The resolution failure is logged in the execution record
3. AI Caller Screening
How Calls Are Initiated
| Source | Description |
|---|---|
| Form element | Candidate reaches an AI Caller step in a hiring flow form |
| Automation | The “AI Caller” action triggers a call as part of a workflow |
| Admin test | Admin initiates a test call from the bot setup interface |
Step-by-Step (Phone Call)
- Data preparation — Input variables are resolved from the candidate’s profile
- Call placed — The system dials the candidate’s phone number via the telephony provider
- Conversation — The AI bot follows its conversation script, asks questions, and listens to responses
- Data extraction — The bot captures structured answers based on its output variable definitions
- Call ends — Either the conversation completes naturally or the maximum call duration is reached
- Post-processing — A transcript is generated; if summarization is enabled, an AI summary is produced
- Data written — Output values are mapped to form fields (if form mappings are configured)
Step-by-Step (Audio/Video In-Browser)
The same process, except the session takes place in the candidate’s browser rather than over a phone call. The candidate speaks through their device’s microphone (and camera, for video).What Happens on Failure
- No answer — The enrollment is marked as failed
- Network drop — The session may reconnect or be marked as failed
- Data extraction issue — Admins can re-process the transcript to re-extract answers
4. Event Scheduling
Step-by-Step
- Candidate reaches scheduling step in their application form
- Available dates are shown in a calendar view
- Candidate selects a date — Available time slots for that date are loaded
- Candidate selects a time slot and confirms
- Booking is created and the candidate returns to the form
Rescheduling
- System checks whether rescheduling is allowed (a maximum may be configured)
- Candidate selects a new date and time slot
- The previous booking time is shown for reference
- The booking is updated
Cancellation
- Candidate provides a cancellation reason
- The booking is marked as cancelled
Live Meeting
- Candidate joins a meeting queue and enters a virtual waiting room
- The waiting room shows queue position and estimated wait time
- When admitted, a “Join Meeting” button appears
- The video meeting opens in a new window
- The candidate can cancel their enrollment while waiting
5. Course Completion (LMS)
Step-by-Step
What Happens on Failure
- Mid-course exit — Progress is saved; the learner resumes from their last lesson
- Quiz failure — The learner sees their score and can retry
- Enrollment cancelled — The learner sees a blocked status page
6. AI Agent Execution
Step-by-Step
- Trigger — The agent is triggered by an automation, a form element, a manual trigger, or a test
- Input resolution — Input variables are populated with data from the application context
- Instruction execution — The agent follows its instruction workflow step by step:
- Visits URLs, clicks elements, types text, uploads files
- For conditional branches: evaluates the condition and follows the appropriate path
- For loops: iterates over the data array, executing child instructions for each item
- For AI instructions: uses AI to determine the appropriate browser action
- Output capture — Data extracted during execution is collected as output variables
- Completion — The execution record is created with status, timing, and all input/output data
What Happens on Failure
- Element not found — The agent halts at the failed instruction
- CAPTCHA encountered — The agent attempts to solve it automatically
- Timeout — The execution is marked as failed after the timeout period
7. Worker Onboarding
Step-by-Step
- Contract created — Via automation, admin action, or API call
- Worker receives notification — An invite or email directs them to the platform
- Worker logs in — They are automatically directed to their onboarding flow
- Form completion — The worker fills out onboarding pages (forms, documents, signatures, etc.)
- Completion — The worker transitions to active status and can access the full worker dashboard
Recollection
If documents need to be re-submitted during or after onboarding, the worker is prompted to re-collect those items when they next log in.8. Authentication
Login Methods
| Method | Description |
|---|---|
| Email + Password | Traditional email and password combination |
| Email OTP | A one-time password sent to the user’s email |
| Phone OTP | A one-time password sent via SMS |
| Google Login | OAuth-based sign-in with Google |
| Dual OTP | Requires both email and phone verification |
| Magic Link | A one-click authentication link sent via email |
| Invite Link | A pre-shared link for new user registration |
Registration
New candidates register by providing their name and email, with optional phone number and middle name fields (configurable per company). They can set a password or authenticate via OTP. Google sign-up is also supported if enabled.Password Reset
- User requests a reset by entering their email
- A reset link is sent to their email
- They set a new password (minimum 8 characters, must include uppercase, lowercase, number, and special character)