Text messaging has become a standard channel in higher education communication, from application deadline reminders to registration nudges and event confirmations. But the market for "higher ed texting platforms" is far less uniform than most vendor lists suggest. Some products are purpose-built conversational texting tools. Some are AI engagement layers. Some are full higher education CRMs in which SMS is one channel among many. And some are general-purpose messaging infrastructure that institutions must configure themselves.
This guide compares 14 platforms that institutions commonly evaluate in 2026. It is written for admissions and enrolment leaders, student success and marketing teams, registrars, CRM owners, and the CIOs and IT leaders who have to make these systems work together.
Two things before we begin. First, this is not a ranking. The 14 platforms below are grouped by architecture, not by quality, and the order carries no judgement. Second, this is a procurement guide, not a feature checklist: the most important differences between these products are structural, and they determine what an institution can realistically do with each one.
A higher ed texting platform is software that allows a college, university or business school to send and, in many cases, receive text messages with prospective students, applicants, enrolled students, alumni or staff. Typical uses include admissions outreach, deadline and event reminders, enrolment and registration nudges, student success interventions, and advancement campaigns.
Beyond that shared definition, the products diverge quickly. They differ in where student data lives, whether students can reply, who sees and answers those replies, which channels beyond SMS are supported, how consent and opt-outs are recorded, and whether messaging history is written back to the institution's system of record.
A higher ed texting platform can mean at least four different things. Understanding which type you are evaluating matters more than any individual feature.
Purpose-built around two-way conversations, campaigns, nudges and staff-to-student communication. These tools usually sit alongside an existing CRM or student information system (SIS) and act as the institution's conversation layer.
SMS is combined with virtual assistants, automated answers, live chat and proactive outreach. The emphasis is on answering student questions at scale and intervening at behavioural moments, with humans handling escalations.
SMS operates within the broader CRM or lifecycle environment and can use the same applicant and student data that drives admissions workflows. Depending on the platform, messages, consent records and delivery history can sit alongside applications, offers, payments and enrolment status.
SMS capabilities are broad, flexible and often global, but higher education workflows must be configured, developed or integrated separately. These range from simple mass texting tools to full communications APIs.
| Architecture type | Where student data lives | Who typically buys it | Main trade-off |
|---|---|---|---|
| Dedicated higher ed texting platform | Synced from CRM/SIS | Admissions, success, advancement teams | Deep texting features, but a separate system to integrate and govern |
| AI conversational engagement platform | Synced or API-connected | Enrolment and student services leadership | Scales answers and nudges, but AI governance must be verified |
| Higher ed CRM/lifecycle platform with integrated SMS | Native platform records or integrated data | Institution-wide, led by admissions or IT | Unified workflow context, but texting depth varies by vendor |
| General-purpose messaging or infrastructure | Imported lists or API-connected | IT, communications, individual departments | Maximum flexibility, minimum built-in higher ed workflow |
None of these is universally better. The right choice depends on the institution's existing technology estate, the markets it recruits in, and whether it wants messaging to live inside or alongside its system of record.
The answer depends on the messaging model you are buying, because several credible products in this guide intentionally solve only part of the problem. An infrastructure platform, a focused mass-texting tool, CRM-integrated SMS and a conversational engagement product do not need identical capabilities.
Depending on the institution's use case, capabilities worth evaluating include one-to-one communication, campaign and bulk sending, scheduling and audience targeting, automated event-triggered messaging, personalisation from student data, inbound replies and routing, CRM and SIS integration, consent and opt-out management, delivery reporting and, for institutions recruiting internationally, support for the sender types and regulations of each target country.
Not every institution needs all of these. A registrar sending term-date reminders has different requirements from an admissions team running two-way conversations with applicants across 40 countries. The procurement framework later in this article turns these capabilities into specific questions.
"Supports SMS" is not enough information on its own. A short glossary helps procurement teams read vendor claims accurately.
SMS is standard text messaging: short, plain-text messages delivered over carrier networks. It works on essentially every mobile phone without an app.
MMS adds multimedia such as images. Availability, cost and behaviour vary significantly by country and carrier; MMS is well supported in the United States but is not a reliable global channel.
Two-way texting means students can reply and staff or automation can respond. This is fundamentally different from one-way broadcast SMS, and it is the capability that varies most across the platforms in this guide.
A short code is a five- or six-digit sending number generally intended for high-volume messaging in supported markets, with its own approval process and costs.
Toll-free messaging uses a toll-free number for texting in markets where this is supported, subject to verification requirements.
A2P 10DLC is the United States framework for application-to-person messaging sent over registered ten-digit long-code numbers, administered through The Campaign Registry. It applies to US long-code business messaging. It is not a global requirement, and institutions messaging only outside the US will encounter different sender rules instead.
An alphanumeric sender ID displays an institution or brand name instead of a number and is common in many international markets. Capabilities vary by country, and alphanumeric senders typically cannot receive replies.
WhatsApp and web chat are separate channels with their own rules, costs and consent models. WhatsApp can be particularly relevant for international recruitment because adoption is very high in many markets, although channel preference varies substantially by country.
The platforms below are grouped by architecture. Within each group, and across the list as a whole, the order is organisational, not evaluative.
Platform type: dedicated higher education engagement platform
What it is. Mongoose is an engagement platform used by more than 1,000 colleges and universities, built around two-way conversations across text, web chat and WhatsApp. Its current positioning centres on AI Agents that handle routine student questions and follow-up, working alongside the institution's existing CRM and SIS rather than replacing them. Older material refers to Mongoose's texting product as Cadence; the company now markets the platform under the Mongoose name, with the Conversation Hub and Intelligence Hub as its core components.
How texting works. Mongoose supports two-way SMS conversations, campaign sending, and AI-assisted responses, with staff handoff when a conversation needs a human. The platform spans enrolment, student success and advancement use cases, including fundraising campaigns by text.
Data and integrations. Student context comes from the institution's CRM and SIS via Mongoose's connectors. Customers cite integrations with systems such as Slate and Ellucian Colleague. Mongoose states that it maintains SOC 2 certification and provides controls intended to support institutions' FERPA, GDPR and TCPA requirements, including consent management and opt-out functionality.
Relevant institutional context. The architecture suits institutions that intend to keep their existing CRM or SIS and want a specialist conversation layer on top of it, particularly where multiple departments will text students.
What to verify. How exactly does messaging history sync back to your CRM, and at what frequency? Which AI Agent capabilities are generally available versus in development? Is WhatsApp supported for your specific recruitment markets?
Platform type: dedicated conversational texting platform
What it is. Modern Campus Message, formerly Signal Vine, is a conversational text messaging platform within the broader Modern Campus product family. It is explicitly built around Nudge Theory: timely, personalised prompts that guide students through milestones across the learner lifecycle, from application through to alumni engagement.
How texting works. Message combines automated campaigns with one-to-one staff conversations through what the company describes as patented blended messaging, where AI-driven automation and human replies coexist in a single conversation thread. A Campaign Builder automates follow-up and adapts outreach based on student responses.
Data and integrations. Messaging is driven by data from the institution's SIS and CRM, allowing targeting by student status, preferences and behaviour, with add-on modules and connectors extending the core product. Published case studies include Kellogg Community College, UC San Diego's student success coaching programme and the University of Notre Dame's alumni engagement work.
Relevant institutional context. A fit for institutions that want a focused, lifecycle-wide nudging and conversation tool rather than a broader AI assistant or a new CRM, especially where student success and retention are the priority use cases.
What to verify. Which of your SIS and CRM fields can drive segmentation, and how is that data kept current? How are inbound replies routed across departments sharing the platform? What does the add-on and connector pricing look like for your stack?
Platform type: AI conversational engagement platform
What it is. Mainstay, formerly AdmitHub, provides behaviourally intelligent chatbots and messaging for admissions, enrolment and student success, with SMS as the primary channel alongside live chat, web chat and social messaging. In 2026, Mainstay became part of the Lemnis Collective and now operates as a division of Lemnis, a nonprofit organisation focused on expanding learner opportunity.
How texting works. Mainstay combines proactive nudges, such as FAFSA reminders, enrolment task prompts and melt interventions, with an AI knowledge base that answers common student questions automatically, escalating to staff where needed.
Data and integrations. Messaging is informed by student data and behavioural signals synced from institutional systems, with the AI drawing on an admissions and enrolment knowledge base refined through millions of student interactions.
Relevant institutional context. Mainstay is distinctive in the strength of its published evidence. Its original deployment, Georgia State University's "Pounce" assistant, was run as a randomised controlled trial evaluated by researchers Lindsay Page and Hunter Gehlbach: committed students with access to the chatbot were 3.3 percentage points more likely to enrol than the control group, which the researchers describe as a 21% reduction in summer melt. That is one institution, one population and one intervention, evaluated in 2016 and published in AERA Open; it demonstrates that well-designed text nudging can move enrolment outcomes, not that any given deployment will replicate those figures. Mainstay also publishes vendor case studies, such as a reported 32% decrease in summer melt at the University of Wyoming, which should be read as case-study evidence rather than controlled research.
What to verify. How is the AI grounded in your institution's own policies and content, and what are the escalation rules? What happens to conversations involving sensitive topics? How is outcome measurement designed, and will you be able to distinguish the platform's effect from other initiatives?
Platform type: AI conversational engagement platform, multi-channel
What it is. Ivy & Ocelot is Gravyty's student engagement and support product, formed from the combination of the former Ivy.ai and Ocelot businesses. It provides AI-powered virtual assistants and live support across chat, SMS, email, WhatsApp, telephony and social channels, aimed at admissions, enrolment, financial aid, retention and broader student services.
How texting works. SMS is one channel within a multi-channel engagement model: the virtual assistant answers student questions around the clock, proactive outreach targets applicants and at-risk students, and live assistant tools let staff step into conversations.
Data and integrations. Gravyty lists integrations with CRMs including Salesforce and Slate, SIS platforms including Ellucian Banner, Colleague, PeopleSoft and Jenzabar, and LMS platforms including Canvas, Blackboard, Moodle and D2L Brightspace, allowing the assistant to draw on live institutional data. The company states compliance with standards including SOC 2, FERPA and GDPR.
Relevant institutional context. Relevant where the primary problem is question volume and service capacity across many departments, and where the institution wants to enhance its existing CRM and SIS rather than replace them.
What to verify. Which knowledge sources will the AI answer from, and how is content kept accurate when policies change? Which of the listed integrations are native for your specific systems versus configured via API? How are SMS consent and opt-outs recorded, and in which system?
Platform type: higher education CRM with native SMS and AI
What it is. Element451 is an AI-focused CRM and student engagement platform for higher education. Texting is a native capability rather than an add-on: SMS and MMS run through the platform's Conversations module and campaign tooling, alongside its Bolt AI agents.
How texting works. Element451 supports two-way SMS and MMS conversations in a shared team inbox, with threading per phone number, conversation assignment, saved replies and automation rules. Inbound messages from known contacts open or reopen conversation threads. A STOP reply automatically records an SMS unsubscribe milestone that applies across the institution's numbers and stops both conversation and campaign sends. Bolt AI agents can be configured to reply to inbound messages, and as of an April 2026 release, both staff and Bolt agents see the originating campaign message when a student replies to an SMS campaign, so short replies like "yes" arrive with context. The platform also screens outbound SMS for content likely to trigger carrier filtering. Per its documentation, MMS attachments are delivered to US numbers only, and messages cannot be sent to VoIP numbers.
Data and integrations. Because texting is native, personalisation, consent and history draw on the same contact records used for applications, campaigns and workflows across the platform.
Relevant institutional context. Relevant for institutions that want texting, AI agents and CRM in one system rather than integrating a separate texting layer.
What to verify. Does the SMS feature set extend to the countries you recruit from, including sender types and MMS behaviour? How would Element451 coexist with, or replace, your current CRM and SIS? What governance controls apply to Bolt agents answering students directly?
Platform type: higher education CRM, admissions and student information platform with integrated SMS
What it is. Full Fabric is a unified platform built for higher education, spanning CRM, admissions, enrolment, payments and student records. It is not a standalone texting product, and it should not be evaluated as one. SMS is an integrated communication capability within that wider platform.
How texting works. Full Fabric supports SMS sending for time-sensitive communications and reminders through an integrated SMS provider, MessageBird. Sent SMS messages and delivery status are logged on profile records. SMS can also be sent as an action within the platform's automated workflows. Current documentation includes a Send SMS message to profile action across applications, offers, classes, forms and events. Workflow entry conditions can respond to events such as an application being started or submitted, an offer being made, accepted or declined, event registration, form submission or lifecycle transitions, with wait steps available for scheduled sequences.
Data and integrations. When the relevant applicant or student data already lives in Full Fabric, personalisation can draw directly from the same profile environment rather than requiring a separate texting database. Full Fabric's marketing-policy framework records communication preferences and policy history against the profile, giving institutions a central consent record to use when governing marketing communication. Institutions remain responsible for configuring and using those communications lawfully. For institutions operating other systems alongside Full Fabric, the platform provides documented integrations and API capabilities.
Relevant institutional context. This architecture is relevant for institutions that want SMS to sit alongside applicant/student data, workflow status and communication history inside a broader higher education platform. Institutions whose priority is a high-volume, two-way conversational texting operation with a specialist shared SMS inbox should separately evaluate the dedicated texting platforms in this guide. The useful comparison is architectural rather than a claim that one model is universally superior.
What to verify. Which countries do you need SMS delivery in, and what sender options apply in each? Which lifecycle events should trigger messages, and how will those workflows be designed? How should messaging permissions and consent be captured for your specific use cases and jurisdictions?
Platform type: admissions and enrolment CRM with built-in texting
What it is. Slate is Technolutions' widely used higher education admissions and enrolment CRM. It handles application management, application reading, decision release, events, communications and data integrations in a single system, and its admissions platform explicitly lists Advanced Texting Features among its capabilities.
How texting works. Texting in Slate sits inside the broader admissions environment. Communications tooling includes drip campaigns, and the platform's AI features include generative predictive text for composing personalised messages, alongside embeddable chatbots for prospective student enquiries. The essential point is that Slate is principally an admissions and enrolment CRM in which texting operates against the applicant records, queries and workflows the office already runs.
Data and integrations. Student context is native to the CRM, with Slate's query engine driving segmentation and its integrations connecting to institutional data sources.
Relevant institutional context. For institutions already running Slate, the practical question is whether Slate's built-in texting meets the required communication model or whether a dedicated texting layer is needed for additional conversational requirements. Several specialist messaging products integrate with Slate for this type of architecture.
What to verify. Which sender types does your Slate configuration support in the markets you need? How are inbound texts routed and assigned within your office structure? If you add a texting layer, which system will own consent and hold the authoritative message history?
Platform type: CRM-embedded conversational messaging
What it is. SMS-Magic is a conversational messaging platform designed to operate inside CRM environments, with products for Salesforce (Converse) and Zoho (Interact), plus a standalone portal offering (Conversive) for organisations without a CRM. Higher education is one of its named industries, with use cases spanning admissions, financial aid reminders, retention, events and alumni relations.
How texting works. SMS-Magic provides one-to-one and campaign messaging, keywords, and conversational flows directly within CRM records, so recruitment and student services staff text from the system they already work in.
Data and integrations. Student context comes from the host CRM. The vendor operates a 10DLC registration centre for US sending and offers compliance tooling such as consent and preference management. Its marketing describes campaigns as globally compliant; buyers should read this as a description of the compliance features provided, not a legal conclusion, since lawful configuration and use remain the institution's responsibility in every market.
Relevant institutional context. Particularly relevant for institutions that run recruitment on Salesforce or Zoho and want texting embedded in that environment rather than a separate application.
What to verify. Which Salesforce clouds and objects does the integration cover in your organisation? How are messaging costs structured on top of the licence? How do consent records in SMS-Magic reconcile with consent held elsewhere in your stack?
Platform type: programmable communications infrastructure
What it is. Twilio is communications infrastructure, not a higher education admissions platform, and the distinction matters. It provides APIs and platform products for SMS, MMS, RCS and WhatsApp messaging, voice, email through SendGrid, contact centres through Flex, identity verification through Verify and customer data through Segment, with education as one of its named solution areas.
How texting works. Twilio's programmable messaging APIs can support a very broad range of use cases, including two-way SMS, mass texting, automated messaging, verification codes and contact-centre conversations. In practice, capability depends on what the institution builds, configures or buys through partners, because the education-specific workflow must be designed by the institution or a partner rather than arriving out of the box.
Data and integrations. Student context is whatever the institution connects through API or its wider data architecture. There is no native higher education applicant record or admissions workflow.
Relevant institutional context. Relevant for institutions with development capacity that want messaging embedded into their own portals and systems, for unusual or high-scale requirements, and for IT teams consolidating communications infrastructure. This is an architectural characteristic rather than a criticism: flexibility is the product.
What to verify. Who will build and maintain the integration, and what does total cost look like once numbers, carrier fees, registration and engineering time are included? How will opt-outs and consent be recorded in your systems of record? Which countries and sender types do you need, and what are the local requirements for each?
Platform type: business messaging software with CRM and workflow integrations
What it is. Sinch Engage, formerly MessageMedia, is business messaging software within the wider Sinch group, offering channels including SMS, MMS, WhatsApp and RCS, together with inbox, campaign and integration capabilities. MessageMedia officially rebranded as Sinch Engage in July 2026. Sinch Engage should not be conflated with the whole Sinch portfolio, which also includes broader communications infrastructure.
How texting works. Institutions can send campaigns and manage two-way messaging, or connect messaging to existing business systems. Current Sinch documentation highlights integrations including HubSpot, Salesforce, NetSuite and Zoho CRM, allowing messaging to operate alongside CRM data and workflows.
Data and integrations. Student context comes from imported data or connected CRM and workflow systems rather than a higher-education-specific student data model.
Relevant institutional context. Sinch Engage occupies a middle ground between raw communications infrastructure and a higher-ed-specific engagement platform. It can suit institutions that want business messaging integrated with a mainstream CRM without building directly on lower-level messaging APIs, while recognising that higher education workflow logic is not the product's primary data model.
What to verify. Which integration do you need for your CRM? What are message, sender and number costs in your destination countries? How are inbound conversations routed when several teams share the platform? Which system holds the authoritative consent record?
Platform type: focused mass texting and two-way messaging platform
What it is. Text-Em-All is a US-based mass texting and automated calling platform with a dedicated higher education offering. Its model is focused: administrators can build contact lists, compose broadcasts and send messages without implementing a wider CRM platform.
How texting works. The platform supports mass broadcasts, scheduled and recurring messages, keyword-based interactions and two-way texting. Contacts can be segmented for different audiences, and opt-out handling is built into the messaging workflow. The company also provides assistance with US carrier-registration requirements, while institutions remain responsible for maintaining the consent required for their messaging.
Data and integrations. Student data can be imported or connected to external systems. This is an imported or integrated data model rather than a native higher education CRM record.
Relevant institutional context. Relevant where an institution or department needs focused broadcast and two-way texting without replacing its wider CRM or SIS.
What to verify. Do you need message history written back to your CRM? Who owns and maintains consent records behind the contact lists? Does geographic coverage match the populations you need to reach? What sending model and pricing structure apply to your expected volume?
Platform type: general-purpose SMS marketing platform with higher education use cases
What it is. EZ Texting is a general SMS and MMS marketing platform with higher education use cases covering communications such as admissions updates, financial-aid nudges and orientation reminders.
How texting works. Its published capabilities include bulk messaging, two-way messaging, keywords, auto-replies, automations, scheduling, segmentation, opt-in tools and reporting.
Data and integrations. Contact data is imported or connected through external integrations. There is no native higher education student data model, so applicant or student context depends on the data the institution supplies and maintains.
Relevant institutional context. It can be relevant for individual departments or institutions that need an accessible general-purpose texting system without buying a wider higher education CRM. Vendor engagement statistics should be treated as vendor-reported rather than independent sector evidence.
What to verify. How will contact data remain synchronised with your CRM or SIS? Which plan contains the functions you require? What are the applicable message and carrier costs? Can the inbox model support your expected two-way conversation volume?
Platform type: general-purpose mass texting and SMS marketing platform
What it is. Textedly is a general mass-texting platform rather than a higher-education-specific product, although education organisations are among its customer segments.
How texting works. Published capabilities include bulk SMS and MMS, scheduling and campaigns, two-way conversations, keywords, auto-replies and analytics. Institutions should verify current capabilities directly with the vendor and treat vendor engagement statistics as marketing evidence rather than general higher education research.
Data and integrations. Contact data is imported or connected through external integrations. There is no native student record, so personalisation depends on the information supplied and maintained by the institution.
Relevant institutional context. It can suit straightforward broadcast or departmental messaging use cases where a broader CRM or specialist higher education engagement platform is not required.
What to verify. Which sender types are available in your markets? How are opt-outs synchronised with institutional consent records? Does the plan and throughput match expected volume and seasonal peaks? What integration is needed to retain messaging history elsewhere?
Platform type: multi-channel communications platform and API
What it is. ClickSend is a cloud communications platform offering channels including SMS, MMS, RCS, email and voice, with both dashboard access and APIs for developers and broad international coverage.
How texting works. Institutions can send bulk or individual SMS, receive inbound replies where supported, route activity into external systems and automate messaging through APIs and integrations.
Data and integrations. ClickSend does not provide a higher education-specific student data model. Student context comes from whatever CRM, SIS or other application the institution connects.
Relevant institutional context. Relevant where an IT or operations team wants a flexible communications delivery layer that can be connected to existing student systems and is prepared to own the workflow and integration design. Higher education workflow depth should not be assumed beyond documented integrations and API capabilities.
What to verify. Which systems will trigger messages and through which integration? What are message and number costs in each destination country? Which inbound capabilities and sender types apply in those countries? How will replies and opt-outs flow back to institutional records?
Feature lists converge; architectures do not. When evaluating any of the platforms above, work through the same set of questions for each candidate.
Platform type. Is this a dedicated texting platform, an AI engagement layer, a CRM or lifecycle platform with integrated SMS, a CRM extension, or general communications infrastructure?
Primary audience. Is the product designed for admissions and enrolment, current student success, the whole lifecycle, alumni or institution-wide communications?
SMS model. Which capabilities are actually supported in your markets: one-to-one messaging, bulk campaigns, automated event-triggered messages, inbound replies, a shared team inbox or AI-assisted responses? Never assume the complete set exists.
Student context. Where does personalisation data come from: the platform's own CRM records, synchronised SIS or CRM data, imported lists or API connections? This determines how current, complete and auditable the context behind each message is.
Other channels. If a vendor claims multi-channel or omnichannel communication, verify which channels are actually coordinated and which markets support them.
Integrations. Focus on current first-party documentation for the systems your institution actually operates. Distinguish supported/native connectors from functionality that is only possible through custom API development.
Compliance and deliverability tooling. Evaluate consent and preference records, opt-out processing, delivery status, sender registration, auditability and staff access controls. These capabilities can support compliance. They do not automatically make an institution compliant.
Institutional fit. Finally, map the architecture to your technology estate. A specialist texting layer can make sense for an institution retaining an established CRM; SMS integrated into the CRM or lifecycle platform can make sense where reducing system boundaries is a priority. The wrong choice is often an architectural mismatch rather than a missing checkbox.
Is inbound two-way SMS supported in every country you recruit from? Is message volume included in the licence or billed separately? Which sender types are available in each market? Which system owns consent? How does an opt-out propagate to other systems? Where do inbound replies go? Is messaging history written back to the CRM? Which integrations are supported connectors versus custom development? Can multiple departments share messaging resources with appropriate permissions?
This section is an orientation, not legal advice. The legal position varies by country, message purpose, sender, recipient, relationship and technology, and institutions should take advice specific to their circumstances.
Institutional texting in the US sits primarily under the Telephone Consumer Protection Act (TCPA) and FCC rules, alongside carrier and industry requirements.
Most of the FCC's consent revocation rules adopted in the TCPA Consent Order, FCC 24-24, became applicable on 11 April 2025. For covered robocalls and robotexts, consumers may revoke consent through any reasonable means, and senders cannot designate one exclusive opt-out method. The FCC expressly recognises reply-text keywords including STOP, QUIT, END, REVOKE, OPT OUT, CANCEL and UNSUBSCRIBE as examples of reasonable revocation, and covered revocation requests generally must be honoured within a reasonable period not exceeding ten business days. The rules also permit a sender to send one non-promotional confirmation message as provided by the FCC's rules.
One specific requirement has been delayed. Section 64.1200(a)(10), to the extent that it would require a revocation made in response to one type of informational message to apply to all future robocalls and robotexts from the same caller on unrelated matters, is subject to a limited waiver. The FCC's Consumer and Governmental Affairs Bureau extended that waiver until 31 January 2027 in DA 26-12, adopted on 6 January 2026. The revocation rules as a whole were not delayed.
Separately, US application-to-person messaging over standard ten-digit numbers uses the A2P 10DLC registration framework, covering the sending brand and campaign use case. Several platforms help institutions with this process, but carrier registration and TCPA consent are different issues.
Institutions should also map their message purposes because marketing and informational communications can face different requirements.
In the UK, marketing by SMS is governed by the Privacy and Electronic Communications Regulations 2003, PECR, alongside UK GDPR. SMS counts as electronic mail for PECR purposes.
Unsolicited direct marketing by electronic mail to individual subscribers generally requires consent unless an applicable exception is satisfied, and the relevant consent must meet the applicable UK GDPR standard.
The position changed in 2026 for charities. The Data (Use and Access) Act 2025 introduced a charitable purposes soft opt-in, in force from 5 February 2026, and the ICO published updated guidance on direct marketing using electronic mail on 28 April 2026. The exception has specific conditions. Many UK universities have charitable status, but institutions should not assume that the charitable soft opt-in automatically covers student recruitment texting. The specific purpose and conditions matter.
The ICO's current guidance should be treated as the primary reference.
Across the EU, the GDPR governs the processing of personal data, while electronic marketing rules also arise through the ePrivacy framework and national implementation.
That means the precise rules applicable to marketing SMS may differ between member states. Institutions recruiting across several EU markets should establish which national rules apply rather than assume one universal SMS-consent rule.
For broader context on admissions data, see Full Fabric's guide to GDPR compliance in higher education admissions.
The purpose of a message can materially affect the applicable rules, but how operational, service and promotional communications are treated varies by jurisdiction.
Examples of operational communications include application-receipt messages, missing-document notices, interview reminders, payment confirmations and schedule changes.
Promotional communications can include programme promotion, open-day marketing, recruitment campaigns or fundraising.
The boundary can sometimes be difficult to determine. Institutions should map each communication type to the applicable rules and document their legal and consent approach rather than relying solely on the label attached to the message.
Compliance determines what an institution may send; deliverability determines what actually reaches the recipient.
Factors worth evaluating include sender registration, carrier filtering, complaints and opt-outs, invalid or recycled numbers, use of generic link shorteners, sending frequency, message relevance and local sender requirements.
Segmentation also matters operationally because relevant communication is less likely to generate complaints or opt-outs than indiscriminate broadcasting.
A note on the ubiquitous claim that SMS has a 98% open rate: the figure circulates extensively through vendor marketing with weak and circular sourcing, and SMS platforms cannot generally measure opens in the same way email systems do. Do not treat a universal SMS open-rate percentage as established higher education research.
Where engagement matters to the business case, measure the institution's own:
data and clearly label vendor-provided evidence as such.
It depends on the message.
Blanket claims that an entire generation "prefers texting" hide variation by message type, urgency, institution, demographic and lifecycle stage.
The more useful distinction is functional. SMS is well suited to short, timely and action-oriented communication such as an approaching deadline, missing document, interview reminder or registration window. Email, portals and formal documents remain more appropriate for detailed information and material that students need to retain.
The Georgia State nudging research discussed earlier is useful precisely because texting was used for targeted prompts around concrete tasks rather than as a universal replacement for every other communication channel.
For broader mobile-recruitment context, see Full Fabric's article on why mobile marketing matters for admissions strategy.
SMS is particularly useful for:
These are moments where speed and visibility can support the wider admissions funnel.
Sensitive or detailed information often belongs in a secure authenticated channel instead. SMS may be appropriate for prompting a student to log into that channel rather than carrying the sensitive content itself.
A recruitment or student-engagement texting platform should also not automatically be treated as an emergency-notification system. Emergency communications can have different reliability, redundancy, escalation, governance and audit requirements that must be evaluated explicitly.
AI in student messaging can refer to several different things.
Drafting assistance helps staff compose messages.
Intent detection and classification analyse incoming messages for routing or prioritisation.
Automated FAQ responses answer common questions from a knowledge base.
Conversational agents hold multi-turn interactions.
Proactive agents initiate communication based on configured signals or workflows.
Human handoff determines when a staff member takes over.
These capabilities carry different risks.
For AI-generated student-facing communication, buyers should investigate:
AI can increase response capacity. It does not guarantee improved enrolment outcomes.
Strip away the feature lists and many institutions face one strategic question: should texting operate as a specialist layer connected to the CRM, or within the same CRM or lifecycle environment that holds applicant and student data?
A standalone texting layer can make sense when the institution has a CRM or SIS it intends to retain, needs deep two-way conversational texting at volume, wants conversational AI as a primary capability or needs a specialist shared inbox across departments. The architectural trade-off is that data, consent and message history may need to be synchronised between systems.
CRM-integrated SMS can make sense when applicant and student data already lives in the CRM or lifecycle platform, messages need to respond directly to lifecycle events, and keeping workflow context and communication records close together is a priority. The trade-off is that texting depth depends on what that wider platform provides.
Full Fabric is an example of the second model. SMS can operate against profile data inside the wider platform and can be used as an action in automated workflows alongside applications, offers, classes, forms and events. This is relevant to personalised, data-driven outreach because messaging can use existing lifecycle context rather than relying exclusively on a disconnected texting database.
Element451 and Slate are also examples of broader higher education platforms with texting capabilities, while products such as Mongoose, Modern Campus Message and Mainstay represent specialist engagement architectures.
Neither model is universally better. The choice follows from the institution's systems, markets, messaging requirements and governance model.
For broader context, see Full Fabric's complete guide to CRM for higher education.
A higher education texting platform is software that allows a college, university or business school to send and, often, receive text messages with prospective students, applicants, current students, alumni or staff. The category includes dedicated texting tools, AI conversational engagement platforms, higher education CRM or lifecycle platforms with integrated SMS, and general-purpose communications platforms.
There is no universal best. The right choice depends on where student data lives, whether the institution needs two-way conversations or mainly triggered reminders, which countries it messages, and whether texting should sit inside the CRM or as a separate specialist layer. Start with the architecture decision, then compare products within the appropriate category.
A specialist texting platform centres on sending and managing conversations and normally receives student context from lists or integrations. A higher education CRM manages the underlying relationships and records, such as enquiries, applications, offers and enrolment, and may include or integrate SMS as one communication channel.
Potentially, but the applicable rules depend on the jurisdiction, message purpose, technology and consent position. In the UK, PECR applies to marketing by SMS. Across the EU, GDPR and nationally implemented electronic-marketing rules are relevant. In the US, TCPA rules apply to covered calls and texts. Institutions should establish the rules applicable to each use case rather than rely on a generic classification.
It depends on the message type and jurisdiction. Marketing SMS commonly requires consent or an applicable legal exception, while operational communications may be treated differently. Institutions should document the basis on which each category is sent and ensure that applicable opt-out or revocation mechanisms work correctly.
A2P 10DLC is the United States framework for application-to-person messaging using registered ten-digit long-code numbers. Organisations register the sending brand and campaign use case. It applies to US long-code business messaging and is not a global requirement.
Many can, but not all. Two-way capability should be verified explicitly, including whether it works in the institution's target countries, where replies appear, how they are routed and whether conversation history returns to the CRM or SIS.
Neither is universally better. SMS is well suited to short, timely and action-oriented prompts, while email and authenticated portals are more appropriate for detailed information, documents and content students need to retain. They are complementary channels.
Yes. Full Fabric supports SMS message sending through an integrated provider, MessageBird, and logs sent messages and delivery status against profile records. Send SMS message to profile is also available as an action in automated workflows across areas including applications, offers, classes, forms and events. Full Fabric is a wider higher education CRM and student-lifecycle platform in which SMS is an integrated communication capability rather than a standalone texting product.
