Design-partner pilots
A useful pilot begins with one recurring customer problem, one or two evidence sources, the people who review product decisions, and a measurable outcome. Include your current workflow, the tools involved, and the part that consumes the most manual effort.
- [email protected]
- Suggested subject
- CloseSpan design-partner pilot
- Helpful context
- Team size, feedback sources, workflow owner, and a representative problem
Product and connector questions
If you need a connector that is not listed, describe the system, authentication method, records you need imported, and whether CloseSpan would read data or perform an approved write. Connector authorization and data synchronization are separate capabilities, so please identify both needs.
Security and privacy reports
For a suspected vulnerability or privacy concern, include the affected URL, observed behavior, reproduction steps, and potential impact. Do not send access tokens, passwords, private customer content, or destructive proof of concept material by email.
CloseSpan does not currently publish a guaranteed response or remediation time. Reports are reviewed directly and handled according to severity and available evidence.