Skip to content
API, security & troubleshooting

Plan privacy-conscious knowledge and contact collection

Collect information for a clear purpose and distinguish conversation context from verified identity.

CCorthex product guidesUpdated October 15, 20262 min read
Where to find itAgent contact settings / Workflows / workspace policies

Before you begin

Use a test environment and the smallest necessary access. Keep workspace API keys and signing secrets on your server, outside browser code and public screenshots.

Example workspace · Demo data. Inspect the original message and recognised details before relying on them. Select the image to enlarge it.
Contact context beside an example conversation showing unverified details

Example workspace · Demo data. Inspect the original message and recognised details before relying on them. Select the image to enlarge it.

Step by step

  1. 1

    Define the purpose

    List which details are needed for support and why. Avoid collecting a name or phone number merely because a field exists.

  2. 2

    Choose the collection path

    Use passive discovery for volunteered relevant details and an explicit workflow form when a structured request is useful. Review any external decision-provider approval separately.

  3. 3

    Explain and minimise

    Keep customer-facing wording accurate about the next step. Do not request passwords, payment credentials or unnecessary sensitive information.

  4. 4

    Control staff use

    Review source evidence and verification labels before sharing or acting on contact data. Use your organisation’s approved identity checks.

  5. 5

    Review retention and requests

    Follow your organisation’s privacy process for access, correction and deletion, and inspect what the supported product controls actually remove.

Good to know

This guide explains product behavior and setup considerations. Your organisation’s policy determines lawful purposes, retention and the handling of customer requests.

Check the result

Check the response, relevant delivery history and organisation scope. Use the Public REST API reference in this Help Center for the technical contract.

Questions & troubleshooting

Does a verified-looking email prove order ownership?

No. Syntax, a staff review and a submitted form do not independently establish control of an account.

Was this article helpful?

Rate this guide on this device. Ratings are not sent to Corthex.