Expected Output Acceptance Specs
Layer 3 of the knowledge system — per-tier specs defining exactly what a customer sees at every touchpoint
9 docs tagged with "tier-gating"
View all tagsExpected Output Specification Methodology
How to create per-tier acceptance specs that define exactly what a customer sees at every touchpoint — the missing layer between feature matrices and E2E tests
Pro + Suite Chat — Expected Outputs
What a Pro Chat or Suite Chat customer sees at every touchpoint — discovery through working product. Combined spec; differences called out inline.
Pro Both — Expected Outputs
What a Pro Both (Voice + Chat bundle) customer sees at every touchpoint — discovery through working product
Starter Both — Expected Outputs
What a Starter Both (Voice + Chat bundle) customer sees at every touchpoint — discovery through working product
Starter Chat — Expected Outputs
What a Starter Chat customer sees at every touchpoint — discovery through working product
Starter Voice — Expected Outputs
What a Starter Voice customer sees at every touchpoint — discovery through working product
Suite Both — Expected Outputs
What a Suite Both (Voice + Chat bundle) customer sees at every touchpoint — the top-tier plan
Trial Expired — Expected Outputs
What a customer sees when their chat plan trial expires without payment — dashboard state, emails, re-subscribe flow