A request stays connected to its conversation
The controlled build connects Gmail conversations to HubSpot tickets, saved reply drafts and urgent Slack notifications. A human reviews and sends the reply.
Follow-up without losing reviewer work
A connected follow-up reused and reopened the existing ticket. Replay ingested no duplicate request, and a reviewer-edited draft stayed unchanged. The connected evidence records these checks separately from the initial three-case run.
Validation and scope
14 unit tests, 18 PostgreSQL integration tests and type checking passed. Three connected synthetic requests verified ticket associations, unsent thread-matched drafts and the urgent alert. A separate connected follow-up verified ticket reuse, reopening, replay and draft preservation.
- Dedicated support test accounts.
- Initial receipt timing includes manual fixture setup and is not an automated inbox SLA or measured human response time.
- The four-sample provider matrix includes one priority mismatch. It is not evidence of general classification accuracy.
- Draft-only operation. A person remains responsible for review and sending.
Next steps
- Expand the labeled classification sample and investigate the observed priority mismatch.
- Measure a representative scheduled inbox sample separately from manually configured fixture receipt times.
- Add native platform screenshots and an optional narrated walkthrough alongside the animated explanation.
