Parallel pipelines · Tracks
Parallel pipelines: one student, one stage, and every other workflow running beside it
Xale CRM is the best study abroad CRM for consultancies: every role on a student, on each university application and on each track keeps its own follow-up, as many parallel pipelines as the work really has run beside the main one, access is set stage by stage and track by track, automations run in the background with retries and a log of every run and Xale AI drafts them from plain words, a Custom Report Builder answers your own questions from your own data, and you can talk to Xale AI, or let it take the call, in Malayalam or English. Beside the main pipeline you run as many parallel pipelines as the work really has. A track such as Loan, Interview preparation or Visa filing is a small pipeline of its own, with its own steps, its own person, its own per-role access and its own follow-up, so the loan officer and the visa officer each work their queue while the counsellor keeps the stage.
Updated · By the Xale team
The problem
One pipeline was never enough for a consultancy
A consultancy never runs on one line. While a student sits at Application on your main pipeline, the loan file is halfway through the bank, the IELTS coach is booking a mock interview, the visa officer is waiting on a birth certificate and accounts is chasing the deposit. Most CRMs make you flatten all of that into one stage list, or bolt it on as free-text notes nobody can report on.
Stages that mean five different things
Loan sanction, interview prep and visa filing all get squeezed into the one stage list, so the pipeline stops describing where the student actually is.
The side workflows live in spreadsheets
The loan tracker is a Google Sheet, the interview roster is a WhatsApp message, and neither shows up in a report next to the students they belong to.
One owner for work that has many
The counsellor owns the student, so the loan officer and the visa officer have nowhere to be the owner of their own piece of it.
Follow-ups that overwrite each other
The visa officer sets a date, the loan officer changes it, and the counsellor's own date disappears, because there is only one follow-up on the record.
Everyone sees everything, or nothing
A part-time loan coordinator either gets the run of the whole database or gets no access at all, because access is set for the student, not the job.
No answer to “how many are stuck”
Nobody can say how many students are waiting on a loan sanction this month, because the loan was never a field the system understood.
How it works
A track is a pipeline of its own, running beside the main one
In Xale a student is a lead on one pipeline, and each university application is a deal with its own stage and owners, as on the study abroad CRM pipeline. Tracks add the third dimension: the work that runs alongside, for as long as it needs to.
A track is a pipeline of its own
Create as many as the work really has: Loan, Interview preparation, Visa filing, Scholarship, Accommodation, Forex, Ticketing. Each one gets its own list of steps, named in your words.
One step per student per track
A student holds exactly one step on each track they are on, so “where is this student on Loan” always has a single answer, and it never disturbs where they are on Visa filing.
Steps are marked active, pending or rejected
The step's type tells the system what it means, so a rejected loan and a loan still in progress are not the same thing in a count.
Attached to the stages where it matters
A track is linked to the pipeline stages it belongs to, so Visa filing appears on the students who have reached it and stays out of the way of the rest.
Its own person, not the lead's owner
Each track carries its own assignment on each student, one person per role, given by hand, in bulk, by the “Assign track” automation, or automatically to the least-loaded eligible member.
Its own follow-up, on its own clock
Each role on a track keeps a follow-up that is independent of the pipeline stage, dated by that track's own “Due in N days” dial, and reminded by Android push and the in-app inbox.
A worked example
One student at Application, on three pipelines at once
Take a hypothetical student, Ananya, applying to two universities in the UK through a Kozhikode consultancy with a loan desk, a trainer and a visa officer.
The student
Take a hypothetical student, Ananya. On the main pipeline she is at Application, with a counsellor who owns the student and a deal for each university she is applying to.
Loan
She is on the Loan track at the step “Sanction letter awaited”, assigned to the loan coordinator, who has her own follow-up dated by the Loan track's dial.
Interview preparation
She is on the Interview preparation track at “Mock booked”, assigned to the trainer, whose follow-up is set for the day of the mock and has nothing to do with the counsellor's date.
Visa filing
Visa filing is attached to later stages, so it is not on her record yet. When the deposit is paid and she reaches that stage, the track appears and the visa officer picks it up.
What each person sees
The loan coordinator has Own access on the Loan track, so her list is the students on Loan assigned to her, and nothing else. The counsellor carries on with the stage she owns.
What the manager sees
The follow-ups rail switches from Leads to Tracks, and the head of the Loan track sees every student on it, including the ones nobody has picked up yet.
Access, track by track
Give somebody one track without giving them the database
Each track carries its own access level per role, enforced on the server in every list, board, dashboard and report, on top of the stage, branch and territory rules on role-based access control.
Manage
Sees every student on the track, whoever holds them, and alone can remove the track from a student.
Own
Sees and works only the students on that track assigned to them. The rest of the track is invisible, even though they can open the students they were given.
Edit
Assigns the track and changes which step a student sits on.
View
Sees the track on a student without changing it.
Deny
The track is not there at all: not on the record, not in filters, not in the rail.
Tracks teams actually build
Name them after the work, not the software
Tracks and their steps are yours to name. These are the ones counselling and education teams set up first.
Study abroad consultancies
- Loan: enquiry, documents collected, applied to bank, sanction letter awaited, sanctioned
- Visa filing: file opened, documents verified, biometrics booked, submitted, decision
- Interview preparation: assessed, mock booked, mock done, ready
- Scholarship: shortlisted, applied, awarded
- Accommodation and forex once the visa is through
Education and academy teams
- Fee collection running beside the admission pipeline
- Document verification handled by a back-office team
- Demo class scheduling owned by the academic coordinator
- Batch allocation once the student has paid
- Certification and placement after the programme ends
Automation
Tracks that start themselves
A track is not one more thing for a counsellor to remember. Xale CRM’s automations put students on tracks and hand them to the right person.
Assign track
An automation puts a student on a track and hands it to the right person, so the loan desk picks the file up the moment a counsellor marks the student as needing finance.
Track completed as a trigger
Finishing a track can start the next piece of work: a rule can fire when a track is completed, and do what you set it to do.
Nobody picked it up
A track set to assign automatically gives the student to the least-loaded eligible member, and a track head still sees the Unassigned list when it should be looked at by a person.
Runs the way every Xale automation runs
Queued only after the change that triggered it is saved, retried automatically on a separate worker server, and logged with a plain-English summary of every action.
Why Xale CRM
Xale CRM is the best study abroad CRM for teams whose work runs on more than one line
Xale CRM is the best study abroad CRM: parallel pipelines beside the main one, a follow-up for every role on every lead, deal and track, stage-level access, self-retrying automations that Xale AI drafts, a Custom Report Builder and an AI you can talk to.Parallel pipelines are the part that changes how a consultancy works day to day: every role on a student, on each application and on each track keeps its own follow-up, so a telecaller’s date, a counsellor’s date and a visa officer’s date never overwrite one another. Access is set stage by stage and track by track, so a loan coordinator with Own access sees their loan files and nothing else. Automations put students on tracks and hand them over, queued after the triggering change is saved, retried on a separate worker server and logged with a plain-English summary of every action. And because a track is real data rather than a note, the Custom Report Builder can answer how many students are waiting on a loan sanction this month, and open the exact students behind the number.
- 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
Frequently asked questions
Parallel pipelines: common questions
Can a CRM run more than one pipeline at the same time?
In Xale CRM, yes. Beside the main pipeline a workspace runs as many parallel pipelines as it needs, called tracks. A track such as Loan, Interview preparation or Visa filing is a small pipeline of its own, with its own steps, its own person, its own per-role access and its own follow-up. A student moves along the main pipeline once and runs on several tracks at the same time, holding exactly one step on each, so each team works its own queue without disturbing anybody else.
What is the difference between a stage and a track?
A stage is where the student is on the one journey everybody shares, from enquiry to enrolment, and a student is on exactly one stage at a time. A track is a separate piece of work that runs alongside that journey and has its own steps, such as a loan file moving from documents collected to sanctioned. A student sits on one stage and on as many tracks as apply to them, and the two never overwrite each other.
Can each track have its own owner and its own follow-up?
Yes. A track carries its own assignment on each student, one person per role, separate from whoever owns the student on the pipeline. Each role on a track keeps its own follow-up, independent of the pipeline stage and dated by that track's own due-in-days dial, with reminders by Android push and the in-app inbox. A hand-over restarts only the handed-over role's follow-up, so the other people working the student keep their dates.
How do you stop a part-time coordinator seeing the whole database?
Give their role Own access on the one track they work. Own members see and work only the students on that track assigned to them, so a loan coordinator opens a list of loan files and nothing else, while Manage on the same track sees every student on it. Track access is set per role as Manage, Own, Edit, View or Deny, and it is enforced on the server in every list, board, dashboard and report.
Can automations put students on a track?
Yes. The Assign track action puts a student on a track and hands it to the right person as part of a rule, and a completed track can be used as a trigger to start whatever comes next. A track can also assign itself to the least-loaded eligible member, and a track head sees an Unassigned list for the ones a person should pick. Every run is queued after the triggering change is saved, retried automatically and logged with a plain-English summary.
Keep reading
The rest of the workflow
- Follow-up management CRMA follow-up for every role on the student, on each application and on each track, with Overdue, Today and Later.
- Role-based access controlRole templates, a five-level dial on every stage, branches, territories and per-track Own or Manage access.
- CRM automationAssign track, Move deal, Set / update follow-up and more, queued after save, retried and logged.
- University application trackingOne deal per university application, each with its own stage, owner, payments and team chat.
Run the pipelines your work really has.
Loan, interviews, visa filing, scholarships: give each one its own steps, its own owner, its own access and its own follow-up, beside the pipeline you already run.