Lifecycle & Payments
An offer belongs to a class, and so does the profile's role in that class. Even so, offers and roles do not change each other on their own: accepting an offer leaves the profile's lifecycle state where it was, and moving a profile to a new state makes no offer. Automation joins the two, in both directions, and through the lifecycle it also reaches payment plans.
Moving the Lifecycle When an Offer Is Answered
Use the template's Automation tab (see Offer Templates):
- Add a workflow and set Start workflow when to the answer you want to react to, for example offer is accepted.
- Add the Transition profile action and pick the Transition to run.
- Save the workflow.
When the applicant answers, the transition runs on the profile's role in the offer's class. If the transition is not valid from the role's current substate, nothing changes. If the profile has no role in that class, nothing happens.
Typical workflows:
| Start workflow when | Action | Effect |
|---|---|---|
| offer is accepted (unconditional template) | Transition profile | Moves the applicant to the substate that follows acceptance, for example toward enrolment. |
| offer is declined | Transition profile | Moves the role to a substate for declined offers. |
| offer is submitted (conditional template) | Send email to staff | Asks admissions to review the submitted conditions. |
| offer is submitted (conditional template) | Transition profile | Moves the role on once the conditions are in. |
Note: For a conditional template, offer is accepted fires when the applicant accepts and the conditions form opens, before anything is filled in. To react to completed conditions, use offer is submitted.
The lifecycle states, substates and transitions available here are the institution's own. See Lifecycle & Journeys.
Making Offers from the Lifecycle
The reverse direction runs from lifecycle workflows. Add a Make offer step (called Create and make offer in the class automation editor) to a workflow that starts on a transition, for example when an applicant moves to an admitted substate. The step starts and makes the offer in the class of the journey that transitioned, with the conditions chosen on the step. See Making Offers.
Steps after Make offer in the same workflow can email the applicant or notify staff.
Connecting Payments
Offer templates cannot create payment plans directly: Create payment plan is not among the actions of an offer template workflow. Payment plans come from lifecycle workflows, which offer the Create payment plan step when the finance module is enabled.
To create a payment plan when an offer is accepted, chain the two:
- On the offer template, add a workflow that starts when the offer is accepted (or offer is submitted for a conditional template) and runs Transition profile to a substate such as "offer accepted".
- Under Settings > Automation & AI > Lifecycle workflows, add a workflow that starts on that transition and runs Create payment plan with the right payment plan template.
The lifecycle transition in step 1 starts the workflow in step 2 for the same profile and class, and the payment plan is created for that class. See Finance for payment plans.
Safeguards Between Offers and Classes
- Removing a profile from a class is blocked while the profile holds an offer in that class, in any state. The Operation not permitted dialog lists the offers, applications, transcripts and payment plans to delete first.
- Deleting a profile after a merge is blocked while the source profile holds any offer. The merge goes ahead and the source profile is kept. See Profile Operations.
- Deleting an offer template removes every Make offer step that uses it from lifecycle workflows. See Offer Templates.
Checklist
Before going live with offers for a class:
- The offer templates exist, and conditional templates have their conditions on the Form tab.
- A workflow on each template emails the applicant when the offer is made, because making an offer sends no email by itself.
- The portal has a page with the Offers widget, and applicants have the
offers.offers_accept_declinefeature. See Applicant Responses. - Template workflows transition the profile on the answers that matter.
- Lifecycle workflows on those transitions create payment plans or send the next communication.