EdTech CRM
Which of the dozens of institutions that took a demo is really close to buying gets lost in e-mail inboxes. The difference between a school that shows interest and a school that signs a contract comes out in the discipline of the follow-up.
The teacher, the administration and the IT officer are separate contact records tied to the same school record; the end of the pilot class and the licence renewal day are fields on that record.
- Split school and institution opportunities into stages and follow which one is nearing a decision in a visual pipeline
- Keep the end of the pilot class and the licence renewal day on the institution record and see the schools to call back before the term closes in a single list
- Gather the meetings and notes with all the contacts at the same institution in a single customer record
- Report how many opportunities are waiting at which stage and the progress per team member
- Run the correspondence with institution contacts from a single business number; let the conversation history stay in the record even when staff change
| School Contact Cards | The teacher, the administration and the IT officer are separate contact records tied to the same school record; which promise was given to whom sits in a note on their own contact card, and the whole situation of the school is read from the institution record. |
|---|---|
| School Year and Licence Renewal | The end of the pilot class deployment and the licence renewal day are fields on the institution record; the schools that need to be called back before the term closes are gathered in a single list by these dates. |
| School Support Request | A usage problem coming from a school is a request record; which school it came from and which module it concerns sit in its fields. The resolution note is written onto the request, and when the same question comes again, it is read from the records of the earlier requests. |
| Budget Line and Approval Step | Which budget line the school will pay from and which approval step the quote is waiting at are fields on the opportunity record; the quote, the management approval and the order are separate stages, and which institution is stuck at which step is read from a single list. |
| Teacher Training Session Record | The usage training given to an institution is a session tied to the institution record; the teachers who attended, the date and the trainer sit in fields, the post-session survey is tied to the same record, and which subject department has not had the training is seen from a list. |
In education technology the decision is not made by one person, and the decision is tied to the calendar: the teacher who tries the product in the classroom, the administration that commits the budget and the IT officer who approves the infrastructure are each convinced separately. This trio decides at the start of the term; when the pilot ends in the middle of the term, the matter slips to the next school year and contact with that institution starts from scratch.
Rapitek CRM gathers the teacher, the administration and the IT officer at the same institution in a single record; what was said to whom sits on the institution's card, not in personal notes. Because it is reported at which stage the opportunities are piling up, the institutions that need to be called back before the term closes are read from a list.
