Call Directory & IdentityLookup App Store Listing in Simplified Chinese — Spam Blocking, Call Blocking, SMS Filter & Known Spam Numbers zh-Hans Copy for China
Your iOS app already markets Call Directory, IdentityLookup, Spam Blocking, Call Blocking, SMS Filter, Message Filter, Spam Labels, or Known Spam Numbers on the en-US product page — gallery frames show spam-label overlays on incoming calls, known-spam database dashboards, Call Directory extension setup, or Message Filter extension toggles — and buyers understand the benefit in English.
Open the same app on the China storefront and the product page still shows English name, subtitle, keywords, description, and screenshot captions that repeat untranslated spam-blocking jargon.
Shipping Call Directory or IdentityLookup extensions in the binary does not auto-fill a Simplified Chinese (zh-Hans) localization row.
AppLocale writes paste-ready zh-Hans listing copy for those Connect fields — aligned with what your spam-labeling and call-blocking extensions actually deliver, using buyer-facing terms like 来电识别, 骚扰电话, 骚扰拦截, 垃圾短信过滤, 通话拦截, and 号码标记 where accurate.
Call Directory is extension-based spam labels and known-spam databases — not Call Screening reason cards, not Silence Unknown Callers Phone toggle alone, not Live Voicemail transcription, not CallKit VoIP UI.
Operator guidance only — no ranking promise, not legal advice, not investment advice. Seller: Fortune Insight, LLC.
Western indie iOS developers — US, UK, EU, Canada, Australia — who:
Already ship or are launching an app that markets Call Directory, IdentityLookup, Spam Blocking, Call Blocking, SMS Filter, or Message Filter extensions on the en-US product page
Show gallery frames with spam labels on incoming calls, known-spam number databases, blocked-number lists, Message Filter extension setup, or 骚扰电话拦截 / 来电识别 / 垃圾短信过滤 hero art
Help users enable Call Directory or IdentityLookup extensions that label or block known spam numbers — not looking for Call Screening, Silence Unknown Callers, Live Voicemail, or CallKit engineering help here
Enabled the China App Store but the zh-Hans row is empty, machine-translated, or still English on spam-blocking gallery frames
Need paste-ready Connect text — not an engineer to wire IdentityLookup data pipelines, not a designer to re-export every screenshot from scratch
If your lead feature is Call Screening (来电筛选 — ask callers why they are calling before the phone rings) — not Call Directory spam labels — see Call Screening listing copy. If your app markets Silence Unknown Callers (Settings → Phone mute-unknown toggle) — not Call Directory extension lists — see Silence Unknown Callers listing copy. If your app markets Live Voicemail transcription — not spam-database labels — see Live Voicemail listing copy. If your app markets CallKit native incoming-call UI — not IdentityLookup Call Directory extensions — see CallKit listing copy. If you only need generic overlay lines, see App Store screenshot captions in Simplified Chinese.
Call Directory extensions vs zh-Hans listing copy — two different jobs
Teams assume spam-blocking capability in the binary or a Call Directory extension covers storefront language. Xcode, IdentityLookup APIs, and Connect actually separate extension behavior from product-page copy:
Call Directory & IdentityLookup extensions — app extensions that label incoming calls with spam tags, block known spam numbers, or refresh call-blocking data. Controls on-device call identification. Does not generate Chinese listing text.
SMS & Message Filter extensions — optional extensions that filter junk SMS or iMessage spam using on-device or server-side rules. Separate from the zh-Hans description paragraph that explains spam-filter value to buyers.
Known-spam number databases — in-app dashboards, community blocklists, and labeled-number logs your listing may showcase. Building and refreshing that data is engineering work, not Connect metadata.
Pricing and Availability → China — makes the app downloadable on the China App Store. Separate from language rows.
App Store tab → Chinese (Simplified) — independent row for title, subtitle, keywords, description, promotional text, screenshots, and caption lines. Empty or English here means China buyers see English fallback regardless of Call Directory flags in the binary.
Working Call Directory extensions and a localized China listing are both required when you sell on the China storefront — neither replaces the other.
Call Directory listing copy is not Call Screening, Silence Unknown Callers, Live Voicemail, or CallKit
Call-aware apps blur five Phone surfaces indie teams conflate. AppLocale covers listing metadata only — layer 1.
1 — App Store listing metadata (zh-Hans row)
Name, subtitle, keywords, description, plus screenshot overlay captions and App Preview text on the Simplified Chinese localization in App Store Connect. This is what buyers see before install. AppLocale's $79 deliverable is paste-ready copy for these fields — including caption lines on frames that show Call Directory spam labels, known-spam number lists, IdentityLookup extension setup, or Message Filter extension marketing art.
Call Directory extension code, IdentityLookup data refresh pipelines, Message Filter extension logic, and spam-database ingestion come from your app binary and backend. Translating that requires Xcode and server work, not a listing rewrite. We do not edit extension code or carrier integration.
3 — Call Screening (different Phone feature — not this page)
Call Screening (来电筛选) asks unknown callers why they are calling before your phone rings — a separate iOS Phone feature from Call Directory spam labels that appear on the incoming-call screen from IdentityLookup extension data. Listing copy for Call Directory should not describe screening prompts, reason-for-calling forms, or pre-ring caller questionnaires — those belong on the Call Screening listing page, not here.
4 — Silence Unknown Callers (different Phone setting — not this page)
Silence Unknown Callers (静音未知来电) is the Settings → Phone toggle that sends unknown numbers straight to voicemail without ringing — not Call Directory extension lists or spam-database labels. If your gallery leads with that system toggle alone — not extension-based spam labeling — see Silence Unknown Callers listing guide.
5 — Live Voicemail & CallKit (not this page)
Live Voicemail real-time transcription and CallKit CXProvider VoIP incoming-call UI are different buyer stories. AppLocale does not implement voicemail APIs or custom dialers. If your gallery leads with voicemail transcription, see Live Voicemail listing guide. If your gallery leads with native VoIP call screens, see CallKit listing guide.
Twin slugs: AppLocale does not maintain separate pages for spam-blocking, spam-filter, sms-filter, message-filter, or identity-lookup URL slugs. Those search intents fold onto this Call Directory and IdentityLookup-as-lead page.
What China buyers still see when the zh-Hans row is incomplete
When Simplified Chinese metadata is missing or falls back to English, the China storefront product page mirrors your US spam-blocking marketing gaps:
English app name or subtitle — Search results and the product header show Latin script while competitors read native
Untranslated keyword field — wasted 100-character cap; China Search indexes Simplified Chinese characters like 来电识别 and 骚扰拦截, not English "Call Directory" or "Spam Blocking" alone
English description — long body text that never mentions 骚扰电话拦截, 垃圾短信过滤, or how Call Directory spam labels work before install
Spam-blocking screenshot captions still in English — overlay lines like "Spam Blocking", "Call Directory", "Known Spam Numbers", "SMS Filter", or "IdentityLookup" on gallery frames targeting China buyers
Spam blocking overclaimed — description promises universal carrier-wide blocking when your app only ships a Call Directory extension with a community blocklist
Conflated with Call Screening — zh-Hans copy mentions 来电筛选 screening prompts when the product actually markets spam-database labels — confusing buyers who expect a different Phone feature
Conflated with Silence Unknown Callers — 静音未知来电 mute-toggle copy on frames that actually show IdentityLookup spam labels
App Preview voiceover or burned-in English — Connect preview text fields can be zh-Hans even when video assets still carry English; redesigning burned-in video text is outside AppLocale scope
Better zh-Hans listing copy reduces product-page bounce for users who already search in Chinese — it does not auto-enable Call Directory extensions in Settings or translate in-app spam-label strings after install.
Common mistakes on Call Directory and spam-blocking zh-Hans listings
Leaving "Call Directory" or "IdentityLookup" untranslated — China buyers expect 来电识别, 骚扰拦截, or 号码标记 on otherwise Chinese copy; English-only overlay lines look unfinished
Machine-translated "spam blocking" as awkward 垃圾拦截 alone — align with buyer-facing terms like 骚扰电话拦截, 来电识别, 垃圾短信过滤, or 号码标记 depending on your UX
Conflating Call Directory with Call Screening — spam labels from IdentityLookup extensions are not 来电筛选 reason-before-ringing cards — different Phone features, different screenshot stories
Conflating Call Directory with Silence Unknown Callers — extension-based spam labels are not 静音未知来电 mute-unknown toggle marketing
Conflating spam labels with Live Voicemail — Call Directory identification is not voicemail transcription; see Live Voicemail listing guide
Conflating Call Directory with CallKit VoIP UI — native incoming-call screens from CXProvider are CallKit marketing; spam-label overlays from IdentityLookup are Call Directory marketing
Claiming universal carrier spam blocking — metadata must match delivery; do not promise network-wide enforcement unless your extension and data sources support it
Claiming Phone.app or system dialer replacement — Call Directory companion apps should not imply they replace Apple's Phone app or carrier call routing for all users
English-only What's New after a spam-blocking launch — version notes are a separate field; base $79 focuses on evergreen listing fields unless you bundle What's New in intake
Assuming IdentityLookup APIs localize the store page — engineering and App Store metadata are independent workstreams
What good zh-Hans Call Directory and spam-blocking listing copy looks like
Align tone with your en-US listing and name the spam-labeling surfaces buyers actually see:
Name & subtitle (30 chars each) — lead with the outcome (来电识别, 骚扰拦截, 垃圾短信过滤) not SDK jargon alone
Keywords (100 chars) — Simplified Chinese queries for Call Directory, spam blocking, SMS filter, known spam numbers — weave 来电识别, 骚扰电话, 骚扰拦截, 垃圾短信过滤, 通话拦截, and 号码标记 naturally; not English API names stuffed into the hidden field
Description — one clear paragraph on where spam labeling appears (Call Directory extension setup, labeled incoming-call screen, known-spam database dashboard, Message Filter toggle) and what the buyer gets — fewer spam calls, labeled unknown numbers, filtered junk SMS
Screenshot captions — one line per frame naming the on-screen state: "开启来电识别，骚扰号码一眼可见" not "Call Directory" alone
Honest scope — if blocking requires specific OS versions, extension enablement in Settings → Phone → Call Blocking & Identification, or supported regions, say so in plain zh-Hans without dialer-replacement or universal-spam-blocking language
Call Directory and spam-blocking screenshot captions Chinese buyers expect
Privacy, utility, and business-phone apps often dedicate one or two gallery frames to the spam-labeling story — Call Directory extension toggles, labeled incoming-call screens, known-spam database dashboards, or Message Filter extension marketing art. Overlay lines on those frames should name the feature in plain zh-Hans:
Spam label on incoming call frame — describe the identification outcome: "骚扰电话实时标记，来电一眼识别" instead of "Spam Blocking" alone
Known-spam database frame — name the data honestly: "百万骚扰号码库，自动更新拦截" vs vague "Stop all spam" when a community blocklist is the actual deliverable
Call Directory extension setup frame — explain the guided benefit: "几步开启来电识别扩展" — not English-only "Enable Call Directory"
SMS Filter extension frame — state the junk-message benefit only when shipped: "垃圾短信过滤，重要信息不错过" when art shows Message Filter settings
Match caption to capture — if the screenshot shows a business call-center spam dashboard, the overlay should describe 商务骚扰电话拦截 not consumer Phone.app UI unless art shows that context
AppLocale includes Call Directory and spam-blocking overlay lines in the screenshot caption deliverable when your gallery uses them. We do not redesign or re-export PNG assets — you paste overlay text into Connect or your design tool.
Connect checklist before you order Call Directory listing copy
Open App Store → Chinese (Simplified) — confirm the zh-Hans localization row exists; adding China under Pricing and Availability alone does not fill it
Audit five text fields — name, subtitle, keywords, description, promotional text (if used) saved in zh-Hans, not placeholder English
List screenshot frames that show spam-blocking UI — note which gallery images show Call Directory spam labels, known-spam lists, IdentityLookup setup, Message Filter toggles, or 骚扰电话拦截 art so caption lines match frame order
Export current English captions — overlay text from Connect or your design spreadsheet, including any "Call Directory", "IdentityLookup", "Spam Blocking", "Known Spam Numbers", "SMS Filter", or "Message Filter" boilerplate
Confirm feature scope honestly — note Call Directory extension vs Message Filter extension vs companion dashboard so zh-Hans copy does not overclaim carrier or Phone.app replacement; confirm you are marketing spam labels — not Call Screening or Silence Unknown Callers alone
Confirm in-app UI language separately — plan Xcode string localization if spam-label strings are still English after install
Skip engineering tasks here — IdentityLookup data pipelines, Message Filter extension code, carrier integration, and spam-database QA stay with your dev team
Paste-ready Simplified Chinese listing metadata rewritten from your English App Store copy, with Call Directory and spam-blocking-aware phrasing:
App name — up to 30 characters on the zh-Hans row
Subtitle — up to 30 characters; visible under the name in Search
Keywords — up to 100 characters in the hidden keyword field
Description — long listing body explaining Call Directory spam labels, known-spam databases, and SMS or Message Filter value for China buyers
Screenshot caption lines — overlay text for frames showcasing Call Directory spam labels, known-spam number lists, IdentityLookup setup, or Message Filter extension marketing art (send frame count and current English lines)
Listing alignment — voice consistent with your en-US page; we note both sides when English also needs tightening on spam-blocking or labeling claims
24-hour turnaround — delivered to the email on your Stripe receipt after checkout and intake
Human rewrite — not a machine translation dump. Character counts verified before delivery.
What AppLocale does not do
Does not implement Call Directory, IdentityLookup, Message Filter, or CallKit extensions
Does not build spam-number databases, carrier PSTN integration, or call-blocking-as-a-service retainers
Does not write Call Screening (来电筛选) listing copy — a different Phone feature with a different buyer story
Does not write Silence Unknown Callers (静音未知来电) listing copy — a different Phone setting with a different buyer story
Does not write Live Voicemail transcription or CallKit VoIP listing copy when those lead the page
Does not maintain separate twin pages for spam-blocking, spam-filter, sms-filter, message-filter, or identity-lookup URL slugs
Does not localize in-app spam-label strings, extension setup wizard text, or runtime caller-ID strings
Does not design or re-export screenshots — only Connect caption text you paste or hand to a designer
Does not edit App Preview video files or burn new subtitles into video assets
Does not manage Apple Search Ads, Custom Product Pages, or ad campaigns
Does not write App Review replies or ongoing ASO retainers
Does not guarantee App Store ranking, spam-blocking accuracy, or download growth in China or elsewhere
Is not QuantRadar, not paid ads management, and not investment or legal advice
Does not invent reviews, ratings, or traffic numbers
How it works
Confirm scope — zh-Hans listing fields plus Call Directory and spam-blocking screenshot captions; extension engineering stays on your side
Send intake — reply from the email on your Stripe receipt with your App Store listing URL, current English name/subtitle/keywords/description, screenshot caption lines (note which frames show Call Directory spam labels, known-spam databases, or Message Filter UI), feature scope (Call Directory extension vs Message Filter extension), and target locale (zh-Hans)
Receive files — within 24 hours, paste-ready zh-Hans fields arrive at your Stripe receipt email
Paste in Connect — App Store → Chinese (Simplified) → save → submit with your next version if needed
Does localizing my listing enable Call Directory or IdentityLookup extensions?
No. AppLocale rewrites App Store Connect metadata — name, subtitle, keywords, description, and screenshot caption lines on your zh-Hans product page. Call Directory extension code, IdentityLookup data refresh, Message Filter extension logic, and carrier call-blocking behavior are system or binary work outside AppLocale scope.
How is Call Directory listing copy different from Call Screening, Silence Unknown Callers, Live Voicemail, or CallKit guides?
Call Directory listing copy markets IdentityLookup extension spam labels, known-spam number databases, and call-blocking extension lists — not Call Screening (which asks callers why they are calling before the phone rings), not Silence Unknown Callers (Settings → Phone mute-unknown toggle), not Live Voicemail transcription, and not CallKit CXProvider VoIP engineering. Screenshot captions should name 来电识别 or 骚扰拦截 benefits rather than 来电筛选 screening flows, 静音未知来电 mute toggles, voicemail transcription overlays, or VoIP answer screens.
What character limits apply to zh-Hans Call Directory listing fields?
App name and subtitle are each up to 30 characters on the zh-Hans row. The keyword field allows up to 100 characters. Description and screenshot caption lines have longer limits but should stay concise — especially subtitle and overlay lines that must fit on-device mockups showing spam labels or Call Directory extension setup UI.
Should I claim my app replaces the Phone app or blocks every spam caller in China?
No. Listing copy should describe the Call Directory extension, IdentityLookup spam labels, Message Filter extension, or known-spam database coverage your app actually ships — without promising universal spam blocking, carrier-wide enforcement, or that you are the system Phone app. AppLocale rewrites from your English source claims; we do not invent blocking coverage your binary does not support.
What do I send after AppLocale payment?
Your live App Store listing URL, current English (or partial zh-Hans) name, subtitle, keywords, description, screenshot overlay lines with frame order noted, which frames show Call Directory spam labels or Message Filter UI, and feature scope (Call Directory extension vs Message Filter extension). Reply from the email address on your Stripe receipt — we deliver to that Stripe email within 24 hours.
Does AppLocale implement Call Directory, IdentityLookup, or Message Filter extensions?
No. We rewrite Connect listing copy only. Call Directory extension configuration, IdentityLookup data pipelines, Message Filter extension logic, CallKit provider setup, and carrier PSTN integration are engineering tasks we do not perform.
Will zh-Hans copy mentioning Call Directory or spam blocking improve China rankings?
We do not guarantee ranking, browse placement, or download lift. Complete zh-Hans metadata helps users who already find your page understand spam-labeling value in their language — it is not a placement hack.
How much does AppLocale cost?
$79 one-time via Stripe checkout. No subscription. Seller is Fortune Insight, LLC.
What is AppLocale not?
Not Call Directory or IdentityLookup engineering, not Call Screening or 来电筛选 listing copy, not Silence Unknown Callers or 静音未知来电 listing copy, not CallKit or CXProvider engineering, not Live Voicemail transcription marketing, not separate spam-blocking, spam-filter, sms-filter, message-filter, or identity-lookup twin listing pages, not carrier or PSTN integration, not Phone.app replacement claims, not screenshot image design, not in-app string localization, not Apple Search Ads management, not ranking guarantees, not QuantRadar, and not investment or legal advice. We do not invent reviews, ratings, or traffic numbers.
Delivered within 24 hours after Stripe payment. After checkout, reply from your Stripe receipt email with your App Store URL and English listing copy. No ranking guarantees. Sold by Fortune Insight, LLC.