Skip to main content
Edvise logo markEdvise wordmark
Pulse deep dive

Safety, Operations, and Launch Details in One Place

Brief student affairs, IT, and executive sponsors with everything they need: opt-in paths, crisis routing, implementation timelines, and the value proven in our pilot programs.

Product Overview & Outcomes

Set expectations for how Pulse fits alongside existing student-success work.

What is Pulse?

Pulse is an AI-powered SMS platform that checks in with students, answers questions 24/7, routes risks to staff, and gives admins real-time insights and alerts.

What outcomes should we expect in a term-length pilot?

Early identification of at-risk students, higher staff reach to low-engagement students, deeper qualitative insights, and a +1-2% lift in persistence vs. control (measured).

How does Pulse actually work day-to-day?

Every 7-12 days Pulse sends an empathetic check-in by text; students reply in their own words; AI flags risk patterns; staff only follows up where it matters.

How much staff effort does Pulse require?

Pulse automates outreach and triage so staff only step in when students are flagged as needing help, keeping workload focused on the conversations that matter.

Student Experience

Keep outreach human while staying within students' existing habits.

Do students need to install an app or log in?

No. Everything is over SMS.

What kinds of problems does Pulse help with?

Everything that touches persistence: basic needs, finances, belonging, mental health indicators, time management, registration hurdles, and the academic issues that flow from them.

Will students get spammed?

No. Pulse uses a semester itinerary (not the same message every week), cohort-specific campaigns, and rate limits. The first text is a transparent welcome with clear opt-out instructions.

How can students opt out?

Students can reply "STOP" at any time. Opt-out handling is baked into the welcome copy and ongoing follow-ups.

Safety, Triage & Crisis Routing

Duty of care workflows that operate even after hours.

How does Pulse respond to crisis language outside business hours?

Immediate auto-triage kicks in: the bot discloses it is a chatbot and provides crisis resources (national and local). High-risk messages are auto-flagged to your designated core team via alerts.

How are high-risk cases handled by staff?

Treat every case as real: wellness checks or door knocks and, when appropriate and consistent with policy, campus police notification. Post-incident notes go into a protected 'Student of Concern' channel, segregated from general tools to respect FERPA and Clery boundaries.

Can workflows reflect our specific on-call, campus police, and community resources?

Yes. Workflows are institution-specific. We can mirror on-campus crisis teams, campus security, or community response depending on your size and policies.

Where do sensitive post-incident notes live?

Notes stay in a segregated 'Student of Concern' channel rather than moving into broader student-success tools, supporting FERPA and Clery obligations.

Admin Experience & Analytics

Context-rich insights without adding dashboard fatigue.

What do advisors actually see?

A role-based dashboard with alerts, per-student conversation context, risk categories (for example: basic needs or mental health indicators), AI-generated next-step suggestions, sentiment shifts, and emerging themes such as "STEM midterms stacking up."

Can different roles see different data?

Yes. Role-based access (success coach vs. AVP vs. IR) with least-privilege defaults keeps sensitive information scoped appropriately.

Data, Security & Compliance

Transparency for legal, audit, and IT stakeholders.

Where is data hosted?

Google Cloud Platform (GCP). AI services run on Google's stack; data is encrypted at rest and in transit.

Are you FERPA compliant?

Yes. Pulse is designed and operated to be FERPA-compliant; student data remains under institutional control.

What about HIPAA/PHI and SOC 2?

We minimize PHI collection, segregate sensitive notes, and log access. Our team shares current HIPAA considerations and SOC 2 audit status so you can communicate the right posture to stakeholders.

What if a student sends prohibited data (for example: a credit card number or medical diagnosis)?

The system detects and suppresses sensitive strings (PCI/PHI patterns), avoids routing them to unintended recipients, and places the record into a DLP workflow. Flagged content is purged on recurring cleans, and we can produce an internal deletion report on request.

How long do you retain data? Can we purge it?

Retention is configurable by institution; exports and deletions can be fulfilled upon request (FERPA access/deletion support).

How do you monitor administrator access?

Every administrator action is logged with exportable audit trails, so security and compliance teams can review access at any time.

Do you support customer-managed encryption keys?

Yes. Institutions can opt into customer-managed keys so your security team controls key rotation and revocation.

How is authentication handled?

SSO (SAML/OIDC via your IdP) with RBAC; all access is logged for audit and compliance.

Integrations & Knowledge Base

Ensure answers stay accurate and on-brand.

Do you crawl the open web?

No. The knowledge base is restricted to institution-approved sources (your site plus selected community resources) and curated Q&As, so answers stay authoritative and current.

What if the bot cannot answer a question?

The exchange is queued in the training center for staff to author or approve a canonical answer that becomes part of the knowledge base.

Pilot & Timeline

Launch quickly, measure outcomes, and build the expansion case.

What is in the pilot and how fast can we launch?

A one-term pilot for up to roughly 1,000 students (pilot plus matched control), one-week setup, and full access to Pulse, analytics, and support.

What metrics do you track in the pilot?

Opt-in and engagement rates, advisor follow-up on flagged students, sentiment patterns, and differential persistence versus the control group, so you have a measurable case for expansion.

Do you require a long-term contract for the pilot?

No. Evaluate with no long-term commitment.

Can we start with a smaller cohort?

Yes. Many partners begin with 200-300 students to prove the model, then scale to institution-wide cohorts when they are ready.

IT & Implementation Specifics

Data flows and controls your IT colleagues expect.

What data do you need for a pilot? How is it transferred?

A secure roster with name, mobile number, and cohort tags. Pilots use encrypted file transfer for speed, and full rollouts can shift to API or SIS integrations that your team already supports.

How do you handle 10DLC registration and compliance text?

We register the campaign under your institution, send a transparent welcome message with opt-out language, and follow carrier/CTIA rules.

How do you keep responses on-brand over time?

Scoped knowledge base, retrieval-first prompting, and a human-in-the-loop training queue. Staff can edit or retire answers at any time.

Can we move from file uploads to direct integrations later?

Yes. Start fast with encrypted file uploads and graduate to API or SIS integrations that follow patterns your team already supports.

Governance, Privacy Notices & Records

Documented expectations for students and staff.

How do you set expectations with students?

The welcome message makes scope and disclosure explicit (that advisors may view messages). Safety copy discloses that it is a chatbot and shares resources immediately on high-risk language.

Can we get audit/export files?

Yes. Exports by cohort or term are available, and internal logs support incident-response and deletion attestations on request.

Ready to get started?

Share this brief with IT, student affairs, or procurement. Once you send the roster and kickoff checklist, we will lock in your launch date.

Request the pilot kickoff