TL;DR

The capability retrieves every saved contact (not just search results) and presents them in a sortable, filterable view you can use to audit, edit, export, or delete contacts in bulk. Records are normalized for consistent display and possible duplicates are flagged for your review rather than auto-merged, preserving user control.

Use this full-list retrieval for quarterly hygiene audits, migration prep, permission checks, or compliance reviews—not for quick lookups, where a search suffices.

The Show my saved contacts capability retrieves the complete set of entries you have stored in your contact list and presents them in a sortable, filterable view. Each entry typically includes fields such as name, phone number, email address, organizational affiliation, and any custom tags or notes you have attached. Unlike a simple search that returns only matching records, this function returns the full inventory, enabling you to audit, edit, export, or delete contacts in bulk.

When to use it

Direct answer: You should trigger Show my saved contacts whenever you need a holistic view of your personal or professional network without applying any search constraints. Common scenarios include:

  1. Periodic hygiene audits – Quarterly reviews to identify duplicate entries, outdated phone numbers, or missing email addresses.
  2. Migration preparation – Exporting the full list before moving to a new CRM, device, or backup service.
  3. Permission verification – Confirming that only authorized contacts are present after a role‑change or offboarding event.
  4. Tag‑based organization – Inspecting which contacts have been labeled with specific categories (e.g., “Vendor”, “Conference 2024”) to support targeted outreach.
  5. Legal compliance checks – Verifying adherence to data‑retention policies by confirming that no prohibited contacts (e.g., those flagged for do‑not‑call) remain in the store.

In each case, the ability to see every record at once reduces the risk of oversight that can occur when relying solely on keyword searches.

How it works

Direct answer: When you request your saved contacts, the platform reads your contact records and returns them as a single list that you can then sort or filter in the interface, rather than requiring you to search for individual entries.

At a high level:

  • Retrieval – Your stored contact records are read and assembled into a list.
  • Formatting – Common fields such as phone numbers and email addresses are normalized for consistent display.
  • Duplicate flagging – Records that appear to be duplicates (matching phone or email) may be flagged for your review; the system does not auto‑merge them, so you retain control over what gets combined or deleted.

For very large contact lists, retrieving everything at once can be slower and more bandwidth‑intensive than a targeted search — if you only need a subset, a filtered search is usually the faster option.

FAQ

Q: Can I export the list shown by this function?
A: Yes, you can export your contact list to a file for use elsewhere, such as a spreadsheet or another contact‑management tool.

Q: Are deleted contacts still visible?
A: No. Once a contact is deleted, it no longer appears when you request your saved contacts.

Q: How does the function handle contacts with identical names?
A: Each contact record is tracked internally by a unique identifier, not just by its display name, so records with the same name are still distinguished from one another. It's worth checking phone number or email fields if two entries look identical.

Q: Is there a limit to the number of contacts I can view at once?
A: There is no fixed limit built into the concept of the capability itself, but very large lists can be slower to load and harder to work with in a single view than a filtered search.

Q: What security measures protect my contact data during this operation?
A: Contact data is protected in line with the platform's standard security practices for stored and transmitted data. For specifics on encryption and access controls, refer to nqzai's security documentation rather than assuming any particular implementation detail.

Q: Does the function support contacts stored in external directories (e.g., LDAP, Active Directory)?
A: The capability operates on the platform's own contact store. It does not connect directly to external directory services like LDAP or Active Directory.

Q: What happens if I lose network connectivity while the list is loading?
A: If the connection drops mid‑request, the retrieval will fail and you'll typically need to retry once connectivity is restored.

Takeaway

Direct answer: The Show my saved contacts function provides a straightforward way to inspect the entirety of your address book in one view. It's most useful for hygiene audits, migration prep, and compliance checks where you need to see everything at once rather than search for specific entries. For very large contact lists, a filtered search will generally be faster than retrieving the full list.

Evidence, limits, and reproducible use

Direct answer: Reproducible workflow. Provide the intended audience and campaign context, inspect the proposed records or draft, then explicitly approve any action that changes a campaign or sends email. Keep suppression, consent, and sender-domain decisions outside a generated draft and review them before use.

Limit. This result does not establish identity, consent, legal basis, deliverability, or a right to contact a person. A draft or campaign configuration is a review artifact, not an instruction to send.

For the currently exposed nqzai workflow and connection limits, check the public capabilities inventory before relying on a result.

Primary references

Where nqzai fits

The workflow above is one nqzai runs directly: AI lead sourcing.

How we keep this honest

Every response nqzai's agent generates is automatically graded by an independent AI judge for accuracy and whether it invents information it can't back up. As of September 2026: sampled responses averaged a 82% quality score over the trailing 7 days (n=39), and our nightly regression suite — which re-runs the agent against a fixed set of real scenarios — passed at a ~93% rate over the last 14 nights. This is internal automated QA, not an independently audited or third-party benchmark; we publish it as a transparency signal, not a claim of perfection.