Email and Algorithm

Email and Algorithm

A system is required that can send emails which are triggered by database transactions, and in addition scheduled emails up to 1 week after the database transaction has occurred. This system should be rules based and should include a user console to build new transaction-based emails and amend emails that are sent (including revision of timelines for schedules).

Use case example: If an applicant’s CV is sent to a customer, a further email should be sent to the customer on the 2nd, 4th and 7th following days asking the customer to feedback on the desire to progress or reject the CV’s. This is one of the most complex of use cases as it includes multiple emails over a protracted period of time, in addition the system needs to query the database to ensure that feedback has not been received before issuing each email request for feedback.

There are a number of use cases in which transaction based emails will need to be created, and we expect new use cases to be defined as the business develops.

All emails need to populate the recruitment technology via API.

2. Feedback System

Each CV that is sent to a customer requires feedback from that customer. As such, the customer must be able to formally progress [to interview] or reject an applicant's CV. Our strong preference is an email solution that allows the person reviewing the CV to reply to the CV send email noting whether to Progress or Reject that candidate. Ideally our system would recognise the content of the mail and change the status of the application in the third party system to Rejected or Interview request.
Could this be achieved through a table in an email? i.e.
Candidate Name
Interview
Reject
John Smith
Yes
Dave Jones
Yes

- Suggest technology for transaction-based email. Please provide supporting information for proposed transaction based email technology
- Suggestions for email feedback system (if this is possible)