[improvement] 360dialog extend request to receive message feature #2053
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
roschaefer
approved these changes
Oct 7, 2024
spec/adapters/whats_app_adapter/three_sixty_dialog_inbound_spec.rb
Outdated
Show resolved
Hide resolved
mattwr18
force-pushed
the
2031_extend_request_to_receive_message_feature
branch
from
7fc7537 to
793dd03
Compare
I've updated the description. I hope that helps. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changed in this PR and Why
We now save the external id of outgoing 360dialog WhatsApp messages to the message record in the database. This allows us to:
a) Send out a previous personalized message that the contributor might have forgotten to ask for, but is still interested in responding to, and
b) Support a reply_to feature where the contributor might quote reply an older message and we can properly assign the incoming message to the correct request instead of trying to infer it solely based on the latest message they received and relying on the user to move the message to the correct request if it has been incorrectly assigned.
Closes #2031