Support and access

A reader looking for help needs a usable contact channel, the languages it supports and its stated hours. The proposed catalogue also has room for supported website and app access information. These details help readers judge whether a service fits their circumstances.

Advertised support

A source may list live chat, email or another contact channel, with language and availability conditions. Those conditions belong together. "English support" does not imply that every channel operates in English around the clock.

For an illustrative example, chat could be advertised as available all day while email has a different response policy. The profile should preserve that difference rather than place one opening-hours label above both.

Tested response is a different claim

An advertised service promise differs from a timed test. A useful measurement needs its date, method and context. A response time from a handful of test chats cannot silently become a guarantee for all future contacts.

Design examples include test-based chat and email response figures and an "Online now" indicator. Who owns those observations, how they are measured and how current such an indicator must be remain open product choices.

Website, app and unfamiliar features

The wider catalogue proposal allows sourced platform and app availability, stated access conditions and explanations of unfamiliar features. Being able to retrieve a web page does not prove that a player in a particular market can use the service.

An editor can publish a supported, reviewed description before a dedicated comparison field exists. That description does not automatically become a search filter. Markets and languages explains applicability; the catalogue model and catalogue review brief cover the proposed field selection and remaining choices.