Premier Success

Institutions running a large or complex Regent deployment tell us the same thing once implementation ends: they had one team that knew their configuration, and then that relationship went away. Premier Success is built to answer that directly. It is a dedicated team that holds your configuration history and your institution’s context, not a rotating queue of generic support tickets.

Premier Success includes:

• A team that already knows your configuration, so you’re not re-explaining your setup on every call.
• Priority engineering escalation for issues that need an engineer’s attention, not just a support queue.
• Time Machine, a sandbox environment for testing changes before they reach your live system — a capability unique to Regent among financial aid platforms.
• Proactive monitoring of your environment, so an issue is caught before your office has to find it.
• Ongoing training for your financial aid office as regulations, and your own procedures, change.

Managed Services

Premier Success sustains the relationship and your implementation. Managed Services addresses the work behind it. Two subscriptions keep your configuration current. Institutions running specialized funds, custom rules, or Regent-built integrations typically take one or both.

Configuration Pack:

Funds and rules with specialized eligibility fall outside standard auto-packaging. Left alone, they mean manual awarding: more workload, more inconsistency, more compliance risk. The Configuration Pack is where Regent builds and maintains that configuration instead.

• Configuration Build & Maintenance — New and ongoing upkeep for specialized funds and eligibility logic.
• Custom Smart Forms — Built to your institution's own requirements.
• Annual Aid Cycle Updates — Configuration refreshed for every new aid year.
• Integration Maintenance — Ongoing upkeep of integrations Regent built for you.

Assurance Pack:

Ensure each release leaves your configuration working. The Assurance Pack turns our release cadence into evidence: every release is checked against your institution's actual configuration, not a generic test script.

• Release Regression Testing — Run against your configuration, every release.
• Pre-Audit Compliance Checks — Ahead of a program review.
• Release Awareness — What's changing, before it reaches your environment.
• Acceptance Test Plans — Ready for your team to run.