Short answer: use staged retrieval with explicit collections, bounded pages, and source context that survives a vendor switch. For a gaming help center, I would keep tenant filtering and freshness in an application-owned contract, then put the search engine behind that contract.
Why does pagination change retrieval architecture for a multi-tenant SaaS help center?
Pagination is not a UI detail in retrieval-augmented generation. It decides which evidence can enter the answer. A page token that is valid for one index may be meaningless after a reindex, and an offset can drift while articles are edited. The contract should therefore name the retrieval unit, tenant filter, freshness target, and a stable cursor shape before it names a provider.
For each request, I keep four values together: tenant_id , collection , cursor , and as_of . The first two prevent cross-customer leakage. The cursor bounds work. as_of makes a citation explainable when a support article changes halfway through a conversation.…