feat: broadcasts and drip sequences - #16
Merged
Merged
Conversation
Both send into conversations the workspace already has, never a cold DM, and both honour each network's messaging window server-side: a recipient outside it comes back skipped with window_closed rather than attempted, so the number sent is often lower than the audience.
Both sides appended models, exports and README rows; nothing overlapped.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Broadcasts and drip sequences over the inbox: one message into every conversation the workspace already has with a segment of its contacts, and a series of them on a delay.
Each platform's messaging window is enforced by the API, so a recipient outside Messenger's or Instagram's 24-hour window comes back
skippedwithskip_reasonwindow_closedand nothing is attempted — the number sent is often lower than the audience.Reading needs the
inboxscope; sending, cancelling, enrolling and unenrolling also needpublish.Merged up to date with
main.