Turn customer communication into traceable plans, business opportunity judgments and customer knowledge.
Automatically organize pre-meeting data around customer communication events, generate post-meeting action packages, accumulate customer knowledge, and allow the sales team to update the sales records on this site in an auditable and confirmable manner.
- 01Data storageEnter customers, business opportunities, contacts, meeting text, email excerpts, document or video transcripts, and generate searchable knowledge entries.
- 02Preparation before meetingGenerate meeting preparation information pages for upcoming client communications.
- 03Post-meeting processingSubmit customer communication content and generate meeting minutes, stage suggestions, forecast instructions and next communication suggestions.
- 04Manual reviewThe sales manager reviews the opportunity stage change suggestions and key forecast descriptions in this site.
- 05Knowledge queryTeams ask questions around the customer knowledge base and get answers with referenced customer information.
Sales relationship workflow
Results, sources, failures, approvals, and rollbacks are saved by project.
No business results yet
There is not enough information to generate pre-meeting preparations. Please add customer information, email excerpts, meeting minutes or documents first.
Data use boundary
Client names, opportunity names, amounts, meeting transcripts, email excerpts, document and video transcripts may contain client trade secrets, personal information and contract information. Please confirm that you have obtained legal authorization before uploading; the system is only used in the current workspace for pre-meeting preparation, post-meeting processing and knowledge base query, and is accessed through customer_id isolation. Current 10 role review supplements: Mark owner_name as personal information; mark sales_cycle, default_stage_set, current_stage, opportunity_amount, customer_name, opportunity_name, source_materials as personal information or commercially sensitive related fields. ; Before uploading information, you must be reminded to only upload authorized information that is directly related to the current customer/business opportunity, and try to delete irrelevant personal information, third-party secrets, and out-of-scope attachments. ; After deletion, only a minimal audit summary can be retained, such as hash, time, operator, object type, deletion event, source identification; original text, excerpts, index text, or sensitive rollback snapshots must not continue to be displayed or have restoreable access. ; Export reports must indicate that they may contain customer trade secrets and personal information; deleted materials can only display minimal audit references. ; OpenAI Responses API belongs to the external AI processing service boundary and should be distinguished from the CRM/email/calendar/conference system integration boundary; keys or log plain text sensitive content must not be exposed on the front end.
Data retention
By default, customer information, production records, approval logs and source references in this site are retained for 180 days; the workspace administrator can delete the information in advance. After deletion, the relevant AI results will retain minimal audit records but will no longer display the original content.
Human responsibility and rollback
The meeting minutes, business opportunity stage suggestions, order forecasts and customer knowledge answers generated by this product are auxiliary information based on the materials provided by the user, and may contain omissions, misunderstandings or insufficient quotations. When it comes to business opportunity stages, forecast caliber, customer commitments and follow-up communication arrangements, the original source must be checked by the salesperson or manager before use.
Rollback only means undoing or restoring reports, approval status, opportunity stage recommendations and workflow status within this site; this product is not connected to external CRM, calendar, mailbox, conferencing or other production systems by default, so rollback does not mean or claim to have reversed any changes in the external production system.