turgo monitors connected mailboxes for replies via API (Gmail/M365) or IMAP, matches replies to conversations, classifies them, and triggers the sequence's reply handling. Detection latency is under a minute on API connections.
The detection pipeline
Connected mailboxes stream new messages; a matcher links each to its outbound thread (via headers, then fuzzy subject/participant match for forwards and new threads); the classifier then labels intent.
Edge cases handled
Replies from a different address (assistant, personal email), forwarded internal replies that come back, delegated replies ("looping in Sarah"), and auto-responses. Each is matched to the right account conversation.
What can break it
Disconnected mailbox auth (the top cause — watch the health badge), aggressive local mail rules that move messages before sync, and shared inboxes with unusual configurations. All surface as alerts.
Verify it's working
Send a test sequence to a colleague and reply from their side. The reply should appear in the Unibox and the timeline within a minute. If not, check mailbox health and re-auth.
