Xale

Automations · Reliable

CRM automation your counselling team can rely on

Xale CRM is the best CRM for automating a study abroad consultancy. Its 26 automation actions, including Move deal, Sync deals, Assign track, Set / update follow-up and Auto-distribute, start from new or re-enquiring leads, assignments, stage, status and sub-status changes, new deals, deal moves and completed tracks.

Each run is queued only after the triggering change is saved, runs in the background with automatic retries on a separate worker server, and is logged with a plain-English summary of each action; an hourly job re-runs recent failures, and any failed run can be retried in one click. Test runs change no data, chains of rules are protected from looping endlessly, business-hours windows and once-per-lead limits keep messages sensible, and scheduled Notification and Alert automations report live counts such as overdue follow-ups. Describe the rule you want in plain English or Malayalam and Xale AI drafts it in the builder for you to preview and save.

Describe it, Xale AI builds it →

Why Xale CRM is the best study abroad CRM →

Updated · By the Xale team

Reliability

Automations built to be relied on

A rule that assigns a new enquiry or books a counsellor’s next follow-up has to run every time. Here is what happens to every automation run in Xale CRM, from the moment a change is saved.

  1. Change savedA lead is created, assigned or moved, or a deal or track changes.
  2. QueuedThe rule is queued only after that change is saved.
  3. Runs in the backgroundUp to 3 attempts, with increasing delays between them.
  4. LoggedSuccessful, failed or skipped, with a plain-English summary.
  5. RetriedRecent failures re-run every hour, or retry one with a click.

Queued only after the change is saved

An event automation is queued only after the change that triggered it is saved. The counsellor’s save goes through first, and the rule then runs in the background.

Automatic retries

A run that hits a problem is tried again automatically, up to 3 attempts, with increasing delays between them.

An hourly re-run of recent failures

Every hour, Xale CRM re-runs automations that failed in the last 24 hours. It skips failures caused by permissions and runs that a later success already fixed, and records a summary in the system log.

A log of every run

Every run is logged as successful, failed or skipped, with a plain-English summary of what each action did, so you can see what a rule did to each lead.

One-click retry

Open a failed run and retry it with one click once you have fixed what stopped it.

Test runs change no data

Test-run an automation before you switch it on. The test changes no data, so you can check a new rule safely.

Priority order, and stop on failure

Automations run in the priority order you set, and a rule can stop at its first failed action instead of carrying on with the rest.

Protection against endless chains

When one rule’s action sets off another rule, Xale CRM protects against endless chains of rules triggering each other.

A separate worker server

Background work runs on a separate worker server: 22 background job types with automatic retries. WhatsApp and Gmail sends are tried up to 5 times.

Built for volume. Lead lists, boards and dashboards are cached by visibility scope, bulk imports, automations and sends run on a separate worker server with automatic retries (22 background job types with automatic retries), and workspaces range from small teams to 150+ user workspaces capturing 10,000+ new leads a month across the platform (Platform figures, September 2026). How the platform is put together is on the platform page.

Xale AI

Describe it, Xale AI builds it

A powerful rule is hard to build by hand: the right trigger, the conditions that pick the right students, five actions in the right order and the dials that stop it firing twice. So we built an AI that builds it. Describe the rule you want in plain English or Malayalam and Xale AI drafts it in the automation builder on your screen, trigger, conditions, actions and dials, checked against your own stages, roles, users and branches; you preview it and press Save.

Say it by chat, from Ask AI in the header or ⌘K / Ctrl+K on any screen, or say it out loud in a live voice call with Xale AI, in Malayalam by default or English on a click. Two descriptions, and what lands in the builder:

A new lead, routed and booked

You say

“When a new Meta lead arrives for the Kochi branch, give it to the least-loaded counsellor there, set their follow-up for tomorrow at 10 am and send our welcome WhatsApp template.”

What lands in the builder

Trigger
A lead is created
Conditions
Source is your Meta lead form, and Branch is Kochi, matched to your own source and branch names
Actions
Auto-distribute to the Counsellor role among the branch’s users, least-loaded first; Set / update follow-up for the Counsellor role, 1 day ahead at 10:00 AM, only if there is no follow-up yet; send the welcome template from your Wati account
Dials
Once per lead, inside business hours

You preview it, change anything, test-run it and press Save.

An offer, described in Malayalam, moves the rest

You say

Said in Malayalam: “When a UK application reaches Offer received, move the student’s other applications up to Offer received too, except any for Germany, and put the student on the Visa filing track.”

What lands in the builder

Trigger
A deal moves
Conditions
Status is Offer received, and Country is United Kingdom, checked against your own statuses and field options
Actions
Sync deals: the student’s other applications follow, stage limit Offer received, exception: never a deal whose Country is Germany; Assign track: Visa filing at its first step
Dials
Every time, respecting stage requirements

You preview it, change anything, test-run it and press Save.

Checked against your workspace

The draft names your own stages, statuses, roles, users, branches and templates, not generic placeholders, so what you preview is what will run.

You preview, you save

The draft opens in the builder on your screen with the trigger, conditions, actions and dials filled in. Change anything you like, test-run it, then press Save.

Explains the engine

Ask Xale AI how automations are queued, retried and logged, and it explains the engine in plain words, in Malayalam or English.

Reports on every rule

Ask which rules are healthy, which failed last night and what a rule did to a student, and Xale AI lists your rules with their health and run history.

Everything you can ask Xale AI, and how to talk to it →

Triggers

Start a rule when the student’s journey moves

Event rules start from a saved change to a lead, a university application (deal) or a track. Time-based rules find the leads that need attention and work through every matching lead, with an optional cap on leads per run.

Leads

  • A lead is created
  • A lead re-enquires
  • A lead is assigned
  • A lead changes stage, status or sub-status

Deals (university applications)

  • A new deal is added
  • A deal moves

Tracks

  • A track is assigned
  • A track is removed
  • A track is completed

Time-based rules

  • Lead idle
  • Lead has no follow-up
  • Lead older than N days

Conditions and guards

Rules that act only when they should

Conditions decide which leads a rule acts on, and guards decide when and how often it runs, so an automation sends the right message to the right student at a sensible time.

AND and OR groups

Combine conditions in AND and OR groups, with equals, contains, greater or less than, between, in or not in a list, and is empty.

Fields with several values

A field that holds several values matches when any one of its values matches, so a condition on one country still matches a student interested in three.

Time of day and day of week

Check the time of day or the day of the week in a rule’s conditions, so a rule acts only during office hours or only at weekends.

Inside or outside business hours

Run a rule only inside business hours or only outside them, for example an after-hours WhatsApp reply to a new enquiry.

How often it runs

Run a rule every time, once per lead, or at most once per chosen period, so a welcome message goes to each student once.

Another application’s stage

A condition can read the stage of the student’s first, other or previous application, so a rule fires only when the whole file is where it should be.

The student’s tracks

A rule can check the student’s tracks in its conditions, so a hand-off waits until the right checklist is under way.

Actions

26 automation actions, from Auto-distribute to Sync deals

One rule can run several actions in order: distribute the student, date the right role’s follow-up, move applications, send the first message and push the lead to another system.

Assign and Auto-distribute

Assign a lead to a person, or Auto-distribute it to a role, a branch or a branch’s users, least-loaded first, skipping anyone over the overdue-follow-up limit you set.

Shuffle

Move leads to another branch, to a role or among a branch’s users, across as many roles and branches as you choose, with the lead never leaving its own branch.

Stage moves

Move a lead to the stage you choose when the rule’s conditions are met.

Move deal

Move the triggering application, the first, the newest or all of a student’s applications to a chosen stage, or to the stage another application is in. It can skip applications already further along, and it can respect or skip stage requirements.

Sync deals

Make a student’s other applications follow the one that moved, up to a stage limit you set, with per-deal exceptions such as never a deal whose Country is Germany.

Delete deals

Remove the applications you specify, so a withdrawn or duplicate application leaves the student’s file automatically.

Set / update follow-up

Set a chosen role’s follow-up, or every assigned role’s, a set number of days or hours ahead, optionally at a fixed time of day from 8:00 AM to 8:00 PM IST. Guards: only if there is no follow-up yet, only if it is missing or overdue, never pull a date forward, never push a date back. Count from the current follow-up, and close other pending follow-ups in the same step.

Close follow-ups

Close the chosen roles’ pending follow-ups on the student, so a closed or converted file stops ringing anyone.

Assign track / set sub-track

Put a student on a track at a chosen step, or move them to that step. The Track completed trigger then starts the next rule when a chosen track is finished.

Remove track

Take a student off a track when the rule’s conditions are met, so a checklist that no longer applies is cleared from the file.

Fields and custom fields

Update a lead’s fields and custom fields as part of a rule, so the record keeps pace with the student.

Email templates

Send an email template from a connected Gmail account when a rule runs.

WhatsApp templates

Wati, Gallabox and UrbanChat accounts send approved WhatsApp templates from automations, with template variables filled from the lead.

Branch moves

Move a lead to another branch when the rule’s conditions are met.

Send API request

Push the lead’s data to any external system, such as your accounts software or a partner’s portal, the moment the rule runs.

Deal automations

Rules that work application by application

Each university application is its own deal with its own stage, so a rule can act on one application, on the others or on the whole file. Deal automations work application by application: "Move deal" moves the triggering application, the first, the newest or all of a student's applications to a chosen stage, or to the stage another application is in, never pulling a deal back unless you say so; "Sync deals" makes a student's other applications follow the one that moved, up to a stage limit you set, with exceptions such as never syncing a deal whose Country is Germany; "Delete deals" removes the applications you specify; and conditions can read a student's first, other or previous application's stage, so a rule fires only when the whole file is where it should be.

Move deal: which one, and where to

Choose the triggering application, the first, the newest or all of the student’s applications, and send them to a chosen stage or to the stage another application is in. Skip applications already further along, and respect or skip stage requirements.

Sync deals, with per-deal exceptions

When one application moves, the student’s other applications follow it, up to a stage limit you set. Exceptions are checked on each deal: never a deal whose Country is Germany, for example.

Delete deals

Remove the applications you specify, so a rule can clear withdrawn or duplicate applications from the student’s file.

Conditions that read the other applications

A condition can read the stage of the student’s first, other or previous application, so a rule fires only when the whole file is where it should be.

Deal triggers

Start a rule when a new deal is added to a student or when a deal moves, and act on that application, on the others or on the student.

Worked example

An offer on one application moves the student’s other applications

A student holds three applications: Manchester, Leeds and Berlin. Manchester reaches Offer received, and the rule starts on the deal move. Its condition checks that the student’s other applications are still in Application. Sync deals then brings Leeds up to Offer received, the stage limit you set, and the per-deal exception never a deal whose Country is Germany leaves Berlin where it is. Close follow-ups clears the Application officer’s pending follow-up on the student, Set / update follow-up dates the Counsellor’s next call, and Assign track starts the Visa filing checklist. Every step is in the run’s log, application by application.

Distribution and shuffling

Distribution and shuffling for high-volume teams

When hundreds of enquiries arrive in a week, who gets each one decides whether it is called today. "Auto-distribute" hands new leads to a role, a branch or a branch's users, least-loaded first, and "Shuffle" moves leads between the users of chosen roles across chosen branches with the lead never leaving its own branch. Both skip users who already hold more overdue follow-ups than the limit you set, with a fallback you choose, can except named users or branches, and work through every matching lead in the background.

Auto-distribute to a role, a branch or a branch’s users

Hand each new lead to the least-loaded member of a role, to a branch, or to the users of the lead’s own branch, so nobody’s queue fills while a colleague’s sits empty.

Shuffle across roles and branches

Move leads to another branch, to a role, or among a branch’s users, across as many roles and branches as you choose, with the lead never leaving its own branch.

The overdue-follow-up limit

Both skip users who already hold more overdue follow-ups than the limit you set, with a fallback you choose, so new leads go to people who can call them today.

Exceptions for named users and branches

Except named users or branches from a distribution or shuffle, so a trainee, a manager or a branch being set up is left out.

Every matching lead, in the background

A distribution or shuffle works through every matching lead in the background on the worker server, and every run is logged with what it did to each lead.

Tracks in the same rules

Assign track / set sub-track puts the student on a track at a chosen step, Remove track takes them off it, the Track completed trigger starts the next rule, and a rule’s conditions can check the student’s tracks. A track can also assign itself to the least-loaded eligible member, and each role on it keeps its own follow-up.

Close follow-ups and Send API request sit in the same action list, so one rule can rebalance a branch, close the follow-ups that no longer apply and push the lead to your accounts system in one run. Lead lists, boards and dashboards are cached by visibility scope, bulk imports, automations and sends run on a separate worker server with automatic retries (22 background job types with automatic retries), and workspaces range from small teams to 150+ user workspaces capturing 10,000+ new leads a month across the platform (Platform figures, September 2026).

Scheduled automations

Notifications and alerts that keep managers ahead

Scheduled automations run on the schedule you set, not on a change to one lead, so managers hear about the whole team’s workload.

Scheduled Notification

Remind chosen users or roles on a schedule you set, and include a live count, such as overdue follow-ups or unassigned leads.

Scheduled Alert

Check a count, such as overdue follow-ups, on a schedule, and notify the chosen people only when it crosses the limit you set. Counts use the automation owner’s data visibility.

Built on the rest of Xale CRM

Automations that respect follow-ups, access and requirements

Automations work through the same role follow-ups, stage requirements and access rules as your team, so an automated step lands where a person’s would.

Each role’s own follow-up

Set / update follow-up writes to the chosen role’s own follow-up on the lead, or on the deal that triggered the rule. Each role keeps one live follow-up there, so the counsellor’s new date never overwrites the telecaller’s.

Follow-up management CRM

Stage requirements still apply

Move deal respects stage requirements unless you tell it to skip them. Where a status requires a scheduled follow-up, a move made by an automation doesn’t make the person schedule a second one.

Stage requirements

Counts within the owner’s access

Scheduled Alert counts use the automation owner’s data visibility, the same stage, branch and territory access that shapes their lead list.

Role-based access by branch

Worked examples

Five automations for a study abroad consultancy

A hypothetical consultancy with several branches, a telecaller, counsellors and a visa team. Each example is a rule you build from the triggers, conditions and actions above.

A new Meta lead reaches a counsellor with a follow-up booked

When
A lead is created.
Only if
Its source is the Meta lead form, and it is inside business hours.
Then
  1. Distribute the lead round-robin to a Counsellor in its branch.
  2. Set / update follow-up for the Counsellor role, 2 hours ahead, only if there is no follow-up yet.
  3. Send the welcome WhatsApp template from the consultancy’s Wati account.

A second rule, set to run outside business hours, sends an after-hours WhatsApp reply instead.

An offer starts the visa hand-off

When
A deal moves.
Only if
The UK application reached the Offer received status.
Then
  1. Distribute the application to a Visa officer in the branch.
  2. Assign track: put the student on the Visa documents track at its first step.
  3. Set / update follow-up for the Counsellor role, 2 days out at 11:00 AM, only if it is missing or overdue.

When the Visa documents track is completed, the Track completed trigger starts the next rule, which puts the student on the Visa filing track and sends a WhatsApp template from the same Wati account.

An offer on one application moves the student’s others

When
A deal moves.
Only if
The application reached Offer received, and the student’s other applications are still in Application.
Then
  1. Sync deals: the student’s other applications follow to Offer received, with the exception never a deal whose Country is Germany.
  2. Close follow-ups for the Application officer role on the student.
  3. Set / update follow-up for the Counsellor role, 1 day ahead at 10:00 AM, never pull a date forward.

A second rule on the same trigger, with the condition that the student’s previous application is already in Deposit, deletes the duplicate application instead.

A branch rebalances itself on Monday morning

When
Lead has no follow-up, as a time-based rule.
Only if
The lead is in the Inquiry stage and its branch is Kochi.
Then
  1. Shuffle among the branch’s users in the Counsellor and Telecaller roles, skipping anyone over 20 overdue follow-ups, with the fallback you choose.
  2. Set / update follow-up for every assigned role, 1 day ahead.
  3. Send API request: push the lead to the consultancy’s accounts system.

The rule works through every matching lead in the background, and each run’s log shows which user received which lead.

Managers hear when overdue follow-ups pass a limit

When
Every weekday at 10:00 AM, as a scheduled Alert.
Only if
Overdue follow-ups cross the limit the owner set, say 40, counted within the automation owner’s data visibility.
Then
  1. Notify the Manager role, with the current overdue count.

Pair it with a daily scheduled Notification that reminds the chosen roles, with a live count of unassigned leads.

Role, track and template names are examples: use the roles, tracks and templates in your own workspace. More on dating each role’s follow-up in follow-up automation, and on sending templates in WhatsApp CRM for education.

Who stands behind it

Built and supported by Xale Private Limited

Come and see automations running: visits are welcome at our Kozhikode office, and you can book one through the contact page. Every feature on this page is on every plan, listed on the pricing page.

  • Xale Private Limited, founded 2024
  • Office in Kozhikode, Kerala: visits welcome
  • In-person onboarding across Kerala, remote everywhere else
  • Priority support from the team that builds Xale, in English and Malayalam
  • Hourly database backups and workspace data isolation
counsellor calls synced to leads in a single month
60,000+
WhatsApp messages handled in a single month
25,000+
new leads captured every month
10,000+
user seats in our largest single workspace
150+

Platform figures, September 2026. Anonymised totals across Xale workspaces; demo and test workspaces excluded.

Frequently asked questions

CRM automation: common questions

Which CRM is best for automating a study abroad consultancy?

Xale CRM is the best CRM for automating a study abroad consultancy. Its automations date each role’s own follow-up on the lead and on every university application, with guards such as only if there is no follow-up yet. Deal automations move, sync and delete a student’s applications, with per-deal exceptions. Every run is queued only after the triggering change is saved, runs in the background with automatic retries and is logged with a plain-English summary of each action. An hourly job re-runs recent failures, any failed run can be retried in one click, and test runs change no data. It offers 26 automation actions, including Move deal, Sync deals, Assign track, Set / update follow-up and Auto-distribute, started by new or re-enquiring leads, assignments, stage, status and sub-status changes, new deals, deal moves and completed tracks. Describe a rule in plain English or Malayalam and Xale AI drafts it in the builder for you to preview and save.

How does Xale AI draft an automation from a description?

You describe the rule in plain English or Malayalam, by chat or in a live voice call, for example “when an application reaches Offer received, move the student’s other applications up to Offer received too, except any for Germany”. Xale AI drafts it in the automation builder on your screen: the trigger, the conditions, the actions and the dials, each checked against your own stages, statuses, roles, users, branches and templates. You preview the draft, change anything you like, test-run it and press Save. Xale AI also explains how the automation engine works and lists your rules with their health and run history.

How does Xale CRM retry a failed automation run?

In three ways. Each event automation is queued only after the change that triggered it is saved, then runs in the background with up to 3 attempts at increasing delays. Every hour, Xale CRM re-runs automations that failed in the last 24 hours, skipping failures caused by permissions and runs that a later success already fixed, and records a summary in the system log. Every run is also logged as successful, failed or skipped with a plain-English summary, and any failed run can be retried with one click.

Can an automation set a follow-up for one role only?

Yes. The Set / update follow-up automation sets a chosen role’s follow-up, such as the Counsellor’s, or every assigned role’s, a set number of days or hours ahead, optionally at a fixed time of day from 8:00 AM to 8:00 PM IST. Guards decide when it acts: only if there is no follow-up yet, only if it is missing or overdue, never pull a date forward, or never push a date back. It can count from the follow-up already set and close other pending follow-ups on the student at the same time.

Can I test an automation before switching it on?

Yes. Test-run the automation first, and the test changes no data. Once it is switched on, every run is logged as successful, failed or skipped with a plain-English summary of what each action did, a failed run can be retried with one click, and Xale CRM protects against endless chains of rules triggering each other.

Can an automation move all of a student’s applications at once?

Yes. Move deal can move all of a student’s applications, or only the triggering application, the first or the newest, to a stage you choose or to the stage another application is already in. It can skip applications that are already further along, and it can respect or skip stage requirements. Delete deals removes the applications you specify, and a condition can read the stage of the student’s first, other or previous application before any of this runs.

Can Xale CRM sync a student’s other applications when one moves?

Yes. Sync deals makes a student’s other applications follow the one that moved, up to a stage limit you set, so an offer on one university application brings the rest up to the same point. Exceptions are checked on each deal, for example never a deal whose Country is Germany, and every run is logged with what it did to each application.

How does Auto-distribute choose who gets a new lead?

Auto-distribute hands the lead to a role, a branch or a branch’s users, least-loaded first, and Shuffle moves leads between the users of chosen roles across chosen branches with the lead never leaving its own branch. Both skip users who already hold more overdue follow-ups than the limit you set, with a fallback you choose, can except named users or branches, and work through every matching lead in the background with a log of every run.

Can an automation push lead data to another system?

Yes. The Send API request action pushes the lead’s data to any external system when the rule runs, such as an accounts package or a partner’s portal. It runs in the background on the worker server with automatic retries, and every run is logged as successful, failed or skipped, with one-click retry.

Can automations assign and follow tracks?

Yes. Assign track / set sub-track puts a student on a track such as Loan, Interview preparation or Visa filing at a chosen step, or moves them to that step, Remove track takes them off it, the Track completed trigger starts the next rule when a chosen track is finished, and a rule’s conditions can check the student’s tracks. Each track carries its own assignment, one person per role per student and track, given by hand, in bulk, by the Assign track automation or automatically to the least-loaded eligible member, and each role on a track keeps its own follow-up, independent of the pipeline stage.

Automate the busywork. Keep every run in view.

Distribute new enquiries, date each role’s follow-up and move a student’s applications together with rules that retry automatically and log every run, drafted by Xale AI from a plain-words description.