Q.

What do the statuses "CHANGED" or "INVALID" mean and when do they occur?

A.

"CHANGED" happens when someone reply with 'y' or 'Yes' than reply 'n' or 'No' later on, or the other way around.

"INVALID" only happens when loading the input list when the particular appointment data is not valid.

Q.

What happens when someone replies 'Yes' then 'Yes' again (or 'No' then 'No' again? Would both have 'CONFIRMED_SMS' status?

A.

This is the current logic we have in the code:

1) MO Text: Y or YES

2) MO Text: N or NO

Q.

Can we capture the actual text received in the feed? e.g. when status is INVALID can we have the text so we see what was invalid? Same with CHANGED, it will help us figure out what it changed from?

A.

This is possible. We can probably add to the output list when parsing the input list if the appointment is INVALID.

When receiving MO reply, the MO text can be added to the output list no matter what it is. This will need to add an extra field to MO_Spec and sample MO data. Another consideration is that we currently only accept Y/Yes/N/No (case insensitive). Anything else won't affect the appointment status. Unless the customer wants to know whatever people say in their text, there is not much value to include the MO text.

Q.

Do we just map the additional fields in the input file from the customer with unused fields in the reminder data or is there support for additional fields?

A.

We just map the additional fields in the input file from the customer with unused fields in the reminder data