Current availability: confirm with the owner
[CONFIRM WITH OWNER] A supported native connector, authentication flow, field mapping and synchronisation behaviour have not been verified. This page does not offer setup steps for an unavailable connector or imply that records already flow into another product.
You can still evaluate the website assistant and its own enquiry workspace. If your operation requires a native connector, retain the existing process until a working, authorised connection has been demonstrated.
Specify the workflow you would need
- Identify the source enquiry and the exact destination object or sheet.
- List required fields, consent purpose and the person who controls destination access.
- Define duplicate handling, record ownership and allowed updates.
- Ask how failures, retries and deleted records would be handled.
- Request a demonstration with a test record before approving a production transfer.
Do not treat a spreadsheet or CRM label as an integration
An exported file, a manually copied enquiry and a native authenticated connector are different processes. Avoid presenting manual work as real-time synchronisation. Before transferring records, confirm that the visitor described follow-up is compatible with the destination and that only required fields are included.
Ask the agency to confirm availability through the published contact route. Do not paste destination account passwords or access tokens into a public chatbot. If a third-party service would be needed, include its cost and responsibility in the proposed scope.