Turkish content
Name the translator or subject owner, terminology approval, fallback language, dotted and dotless I cases, dates, numbers, addresses, and the screens that require human review.
Departure board / local context
Map this Türkiye operation, not an imagined national average.
The useful discovery questions come from actual customers, staff, channels, vendors, and service promises. Country context guides investigation without claiming every Turkish user or organisation behaves alike.
Audience and access
Identify public visitors, account holders, staff, partners, age or identity questions, accessibility expectations, authentication routes, and what happens when login fails.
Communication channels
Record email, SMS, phone, messaging, notifications, consent choices, sender ownership, service windows, escalation, and whether suppliers can support the planned use.
Hosting and vendors
Trace infrastructure, analytics, customer support, file storage, AI services, communications, identity, payment, and every point where data or availability crosses suppliers.
Mobile and performance
Set real device, browser, network, page-weight, interaction, accessibility, and error-recovery evidence instead of assuming a fast desktop demo represents users.
Support and acceptance
Name the Turkish reviewer, operational owner, decision deadline, release approver, maintenance owner, incident route, and exact proof needed before production.
The client supplies current, truthful information about its operation and appoints qualified reviewers. Faith Forge Labs can research and implement an agreed technical response but does not certify a market, legal position, tax route, or local-language meaning.
Route card
Bring one end-to-end service moment.
Describe what a person tries to do, which systems respond, where information travels, how value moves, and who decides whether it worked.