Offers
An offer is an admissions decision sent to a profile for a specific class. Staff build reusable offer templates, start an offer from a template on the profile, and make it. The applicant then accepts or declines the offer in the portal. A conditional offer also asks the applicant to meet a set of conditions, filled in on a form and submitted.
Offers do not move a profile through the lifecycle or create payment plans by themselves. Automation connects them: an accepted offer can transition the profile's role in the class, and a lifecycle workflow can make an offer or create a payment plan. See Lifecycle & Payments.
Key Concepts
| Term | Definition |
|---|---|
| Offer template | A reusable definition of an offer, with a name and a type. Templates belong to the institution and can be used for any class. |
| Unconditional offer | An offer the applicant accepts or declines with one click. |
| Conditional offer | An offer that comes with conditions. Accepting it opens a form where the applicant fills in the conditions and submits them. |
| Condition | A field on a conditional template's form. Staff tick the conditions that apply to each offer; the applicant sees only those. |
| Offer state | Where the offer stands, from Waiting to make offer to Accepted, Submitted or Declined. See Offer States. |
| Class | The intake the offer is for. An offer always belongs to one of the profile's classes. |
How Offers Work
- An administrator creates offer templates under Settings > Templates & documents > Offer templates. See Offer Templates.
- Staff start an offer from the profile's class, choose the conditions for a conditional offer, and click Make offer. Automation can do the same. See Making Offers.
- The applicant sees the offer in the Offers widget of the portal and accepts or declines it. See Applicant Responses.
- Each step records who acted and when, adds a story to the profile's activity, and can start automation workflows. Most steps also send a card to the journey owner's Inbox. See Offer States.
Rules at a Glance
- A profile can hold one offer per template in each class.
- An offer stays invisible to the applicant until staff make it.
- Only the profile that received the offer can accept, decline or submit it. Staff cannot answer on the applicant's behalf.
- Accepted and declined are final. There is no way to reopen an answered offer; delete it and start a new one instead.
Pages in This Section
| Page | What it covers |
|---|---|
| Offer Templates | Creating unconditional and conditional templates, the conditions form, template automation, deleting templates |
| Making Offers | Starting and making offers on a profile, choosing conditions, automated offers, deleting offers |
| Applicant Responses | What the applicant sees in the portal, accepting, declining and submitting conditions |
| Offer States | The state machine, the labels staff and applicants see, and where offers show up in reports and exports |
| Lifecycle & Payments | Moving the profile's lifecycle on an answer, making offers from lifecycle workflows, connecting payment plans |
| Settings & Permissions | The Offers module and the features that control each action |