Team chat · Lead and application threads

CRM with internal team chat: a thread on every lead and application, not a WhatsApp group

Xale is a CRM with internal team chat built into the student record. Every lead has its own thread and every application has its own channel, so the telecaller, counsellor, application, visa and accounts staff working one student talk in one place instead of in personal WhatsApp groups. Whoever can open the lead can read and post, a new counsellor sees the whole history, and the conversation stays with your workspace when people move on.

Start free →See pricing

Updated September 2026 · By the Xale team

The problem

Why counselling teams outgrow staff WhatsApp groups

One student’s file passes through five or six hands between the first call and the visa. When coordination happens in WhatsApp groups, the CRM holds the data, the phones hold the story, and the two drift apart.

Every hand-off starts from zero

From telecaller to counsellor to the application desk, visa team and accounts, each person rebuilds the story from forwarded screenshots.

Files and voice notes everywhere

The passport scan is in one group, the SOP draft in a direct message and the explanation in a voice note on someone’s phone.

Student details on personal phones

Staff groups run on personal numbers next to family chats, so student names, numbers and documents sit on devices the business doesn’t manage.

People leave and take the context

When a counsellor resigns, the group history leaves with their phone. The next person inherits the student, not what was promised.

Groups nobody maintains

Someone who moved branch is still in the group, and the new visa officer was never added.

No record of who said what

When a student questions what they were told, the answer is buried in a scroll of unrelated chat, if it survives at all.

How it works

Internal chat on every lead, and a channel on every application

In Xale a student is a lead, and each university application is a deal with its own stage and owners, as on the study abroad CRM pipeline. The chat follows the same shape.

A thread on every lead

A lead’s Chat tab opens All Chats: the student’s own thread, where everyone working the student posts.

A channel for every application

Each deal, usually one university application, has its own channel. Every message there is copied into All Chats with the application’s name in front, so the student’s thread tells the whole story.

Text, files and voice notes

Write messages, attach PDFs, images, Word files (Excel from the Android app) or short MP4 videos, and record voice notes that play inline.

Replies and @mentions

Quote a specific message in your reply. Type @ to bring in the lead’s creator, owner or assignees, or anyone on its applications.

Read status and unread counts

Your own messages show “Seen by” with a count in the lead’s Chat tab. The header’s Messages list shows the latest message and unread count for every lead you can open that has team messages.

Live, with alerts

New messages, reads and deletions appear live for people on the thread. People assigned to the lead or its applications, and the lead’s creator, get an inbox notification and an Android push that opens the chat.

Who is in the thread

Who can read and post in a lead’s chat

Nobody is added to a chat by hand. A person can read and post in a student’s All Chats thread when they can open that lead:

Admins: Every conversation in the workspace.
Stage access: People whose role has admin or manage access to the lead’s stage, within their branches.
Assignees: Anyone actively assigned to the lead, or to one of its applications.
Territory and track reach: Roles with reach by field value, such as a country manager for their countries within their branches, or reach through a track.

An application’s channel also requires access to that application, and being mentioned doesn’t grant access. These routes come from your roles, branches and territories, so changing someone’s role or branch changes which conversations they see.

Worked example

One student, five roles: a telecaller-to-visa hand-off in the lead chat

A student enquires, is qualified, and applies to one university in the UK and one in Canada. Here is who posts where, and what the others see.

A student’s hand-off from telecaller to visa in Xale’s lead chat
Step	Who	Where	What happens
1. Enquiry qualified	Telecaller	All Chats	Posts a voice-note summary of the first call for everyone who can open the student.
2. Counsellor assigned	Counsellor	All Chats	Reads the thread from the first message, so the student isn’t asked the same questions twice.
3. Two applications opened	Counsellor	UK and Canada channels	Shares the SOP draft in the UK channel; All Chats shows it too.
4. Application query	Application officer (custom role on the UK application)	UK channel	Quotes the SOP message and @mentions the counsellor: a second LOR is needed.
5. Visa file	Visa officer (custom role on the Canada application)	Canada channel	Reads the channel’s history and posts the checklist status.
6. Deposit receipt	Accounts (assigned to the Canada application)	Canada channel	Is @mentioned about the deposit, gets an alert and replies in the thread with the receipt.
7. Oversight	Branch manager	Any thread	Reads threads for students in the stages their role manages, without being added to anything.
8. Counsellor leaves	Admin	—	Reassigns the student, blocks the leaver so Xale refuses their next request, and removes the Xale app from their company phone.

Role names are examples: the study-abroad workspace starts with Super Admin, Admin, Manager, Counsellor and Telecaller, and you add application, visa or accounts roles. How each team is assigned and reminded at every hand-off is shown step by step in one student, four teams.

Side by side

Staff WhatsApp groups vs Xale lead chat

WhatsApp remains the right tool for talking to students. For talking about them inside the team, here is how the two compare, including where WhatsApp does more.

Staff WhatsApp groups compared with Xale lead chat
	Staff WhatsApp groups	Xale lead chat
Where the conversation lives	A group on someone’s personal number	Inside the student’s lead, and in a channel on each application
Who is in it	Whoever was added by hand, and rarely removed	Whoever can open the lead or application, from assignments, stage, branch and territory access
New counsellor after reassignment	Has to be found and added to the right groups	Reads the whole thread as soon as they are assigned
A staff member leaves	Chats and files stay on their phone	Block them and Xale refuses their next request, so they can’t open any chat; messages stay on the lead
One student, several applications	One group per student, or one huge group for everyone	A channel per application, all copied into the student’s All Chats
Who else is in the app	Students, family and friends	Only signed-in staff of your workspace
Search inside message text	Yes	Not yet: the Messages list is searched by student, not by message text
Reactions and typing indicator	Yes	No typing indicator; reactions aren’t shared across the team

Access and ownership

Chat access follows lead permissions, and history stays with the student

Messages are stored against the lead, with no expiry. Access is worked out live from permissions, not a member list someone must maintain.

No separate chat permission to get wrong

Reading and posting follow one rule: can this person open the lead, and for an application channel, that application? The same check guards file uploads and read receipts.

Reassignment moves access

Messages belong to the lead. A new assignee sees the full history; the previous one loses access unless their role, branch or territory still covers the lead.

Blocking ends chat access

Block a user and Xale refuses their next request, so they can’t open any chat. Deactivating alone doesn’t: a deactivated user can still sign in and see what their role allows.

Part of the record

How team chat connects to follow-ups, documents and the activity timeline

Chat is where the team thinks out loud; the rest of the lead record turns decisions into tasks, files and history.

Follow-ups

Agree the next step in chat, then set it as a follow-up for the role that owns it. The follow-up carries the reminder; the chat carries the reasoning.

Role-based follow-up management

Documents and stage requirements

Files shared in chat stay in the chat. Official documents go in the Attachments tab, where stage requirements can stop a move until the passport or SOP is there.

Student document management

Activity timeline and lead filters

Stage moves, assignments and document changes go on the activity timeline. To find students your team discussed, filter the lead list for “Discussed in team chat”, optionally by sender.

Lead management software

WhatsApp with students

Team chat is staff-only. Student conversations run through Xale’s separate WhatsApp inbox, so internal notes stay internal.

WhatsApp CRM for education

Web and Android

Team chat for counsellors, at the desk and on the move

In the web CRM

Chat tab in the lead drawer, with a picker for All Chats or any application’s channel
Messages in the header: unread badge, search threads by student, start a chat by finding a lead, and Clear chats for your own list
Voice notes from the browser microphone
Hover a message to reply or delete

In the Xale Android app

Chat hub with Internal and WhatsApp tabs, and a Chat tab on each lead
Photos, camera, documents (PDF, images, Word, Excel) and voice notes that play inline
Reply to a message or copy its text
Push notifications that open the lead’s chat

Coming soon

Next: edit messages and jump to the original

Built, and coming to the web CRM in the next release; not live in workspaces yet:

Edit your own text messages, marked “edited” (the earlier text isn’t kept).
Click a quoted reply or mention to jump to the original message.
A sound and clickable toast on the web for new messages.
Live updates for admins and managers viewing a thread they aren’t assigned to.
Multi-line messages (Shift+Enter) in the web composer.
@mention workspace admins, and alert anyone you mention even if they aren’t on the lead.

Limits

What Xale’s team chat doesn’t do yet

No typing indicator. Reactions in the Android app stay on that phone and aren’t shared with the team.
The Android app shows each lead’s All Chats thread, including the application messages copied into it, but not the separate application channels, and it can’t edit or delete messages.
Moving a lead to Trash deletes its chat, and restoring the lead doesn’t bring it back.
The lead’s creator gets a short preview alert for new messages even after losing access to the lead.
A blocked user who created a lead can still receive short preview notifications for it on an Android phone that keeps the app.
Application messages show in the student’s All Chats to anyone who can open the student, even if that application is hidden from them.
Chat attachments open from a direct file link and are kept apart from the Documents tab.
Push notifications need the Xale Android app.

Frequently asked questions

CRM with internal team chat: common questions

What is a CRM with internal team chat?

A CRM where staff discuss a customer inside that customer’s record instead of in a separate messaging app. In Xale every student lead has a team thread, every application has its own channel, and access follows the lead’s own permissions.

Is this the same as WhatsApp with students?

No. Team chat is internal: only signed-in staff in your workspace who can open the lead can see it. Conversations with students run separately, through Xale’s WhatsApp inbox.

Can the student see the team chat?

No. Students have no access. Only team members signed in to your Xale workspace who can open that lead or application can see it.

Can I send voice notes and files?

Yes. Record a voice note from the browser on the web or from the Xale Android app, and it plays inline in the thread. You can share PDFs, images and Word files from either, Excel files from the Android app, and short MP4 videos from the web.

Who can read a lead’s chat?

Anyone who can open the lead: admins, people with admin or manage access to its stage in their branch, the people assigned to the lead or its applications, and territory roles such as a country manager. An application’s channel also needs access to that application. There is no separate chat permission.

What happens to the chat when a lead is reassigned?

The messages stay on the lead. The new assignee can read the whole thread straight away, and the previous assignee loses access unless their role, branch or territory still covers that lead. Past messages keep their sender’s name.

What happens when an employee leaves?

Block the user and Xale refuses their next sign-in or request, so they can no longer open any chat. If they created leads, a phone that still has the Xale app can keep showing short new-message previews for those leads, so remove the app from company devices. Deactivating a user doesn’t end access on its own: they can still sign in and see what their role allows. The conversations stay on your students’ records for whoever takes over.

Can I edit or delete a message?

You can delete your own message for everyone; others then see This message was deleted and the content is removed. Editing your own text messages is coming in the next release. Neither is available on the Android app yet.

Who gets notified about new messages?

People assigned to the lead or its applications and the lead’s creator get an inbox notification with a short preview, plus a push on the Xale Android app that opens the chat. The creator keeps getting these even after losing access to the lead, and then sees only the preview.

Move the conversation into the record.

Give every student and every application its own team thread, and let access follow the permissions you already set.