"When someone replies, the framework should know what they are replying to."
The Problem Today
Inbound messages arrive with sender and recipient information but no connection to the outbound message that prompted them. Correlating a reply to its original message requires custom logic keyed on phone numbers, session identifiers, or other application-level markers.
What We Are Building
A correlation mechanism that links inbound messages to the outgoing conversation that originated them, using the sender/recipient endpoint pair and a configurable correlation window (time-based or explicit conversation ID passed via provider thread identifiers where supported). When an inbound message is correlated to a conversation, it is appended to that conversation's history automatically.
Benefits
- Replies are automatically associated with their originating conversation
- No custom correlation logic required in the application
- Correlation works across providers that support thread identifiers and falls back gracefully to endpoint-based matching for those that do not
The Problem Today
Inbound messages arrive with sender and recipient information but no connection to the outbound message that prompted them. Correlating a reply to its original message requires custom logic keyed on phone numbers, session identifiers, or other application-level markers.
What We Are Building
A correlation mechanism that links inbound messages to the outgoing conversation that originated them, using the sender/recipient endpoint pair and a configurable correlation window (time-based or explicit conversation ID passed via provider thread identifiers where supported). When an inbound message is correlated to a conversation, it is appended to that conversation's history automatically.
Benefits