How can we help?

The information Polyosync can access through a CRM integration depends on the external provider, the integration's supported operations, and the authorization granted by the connected account. CRM platforms may contain different types of business information, and not every integration provides access to every record or field. Common CRM information categories Depending on the provider and supported integration functionality, CRM systems may expose information such as: 1. Leads and prospects. 2. Customer and contact records. 3. Companies and organizations. 4. Sales opportunities and deals. 5. Pipeline stages. 6. Customer interactions and activity records. 7. Notes and other permitted record details. 8. Custom fields supported by the CRM. These categories describe common CRM data structures. Their availability in Polyosync must be verified for each supported integration. Does connecting a CRM give Polyosync access to every record? Not necessarily. Access may be limited by the external account's permissions, provider-specific restrictions, available API operations, and integration configuration. Can Polyosync retrieve customer information? A supported integration may provide read access to authorized customer information when the relevant operation is implemented and configured. Can Polyosync modify CRM records? Write operations require specific support and authorization. A connection that can read information should not be assumed to support creating, updating, or deleting records. Does Polyosync automatically copy my entire CRM database? A successful connection does not, by itself, establish that a complete database import or continuous synchronization takes place. The information accessed depends on the actions performed through the integration. What about custom CRM fields? Custom field support depends on the provider and the operations implemented by the integration. If your workflow depends on a particular custom field, verify that it is accessible before relying on it. How should I prepare CRM data for AI-powered operations? Step 1: Identify the records required for the business process. Step 2: Determine which fields are essential. Step 3: Confirm that the external account can access those fields. Step 4: Verify that the integration supports the required operations. Step 5: Test the behavior using representative records. Step 6: Validate the results before expanding the workflow. What if expected information is missing? Check the CRM account permissions, record ownership, field visibility, and integration configuration. The absence of a field or record does not necessarily indicate that the entire connection has failed. Data protection considerations CRM systems often contain personal information and commercially sensitive data. Only access information that is necessary for the intended business purpose. Ensure that your organization's CRM integration practices comply with applicable privacy requirements and internal policies. Recommended approach Begin with a limited set of records and clearly defined operations. Confirm what information can be accessed and how it will be used before incorporating the integration into broader business workflows.