Prepare business records with AI
Describe what should be recorded, then inspect the actual change.
Prepare supported customer records, activity notes and other module actions in ordinary language, with review of target and values before execution.
Proposed record change
A clear description is a starting point, not a saved fact.
After a call, a colleague may need to capture a decision against the right customer. AI can translate that request into a supported action proposal instead of making the person find every field first. The proposal is not the completed record. Review who and what it concerns, distinguish reported facts from assumptions, and confirm only the change the business actually intends to make.
Name the record and supported action clearly.
Identify the customer, contact, activity or other supported module object. Include the date and relevant detail rather than relying on an ambiguous yesterday or this person when several records are plausible. Available actions depend on enabled modules and your authority. The assistant does not become a universal database editor or a specialist vertical system merely because a request can be expressed in natural language.
- Specific targets and supported module operations
Review every proposed value before execution.
Inspect the target record, proposed text, date, status and any linked person. A call note should reflect what happened, not invent an agreement or an owner. Creating a new contact requires checking whether the person already exists. Module validation still applies when the action is confirmed, so missing required information or an invalid transition should be resolved rather than accepted as a successful change.
- Reviewable targets, field values and ordinary module validation
Proposed record change
Check the saved record after execution
Check the outcome in the actual business record.
After confirmation, inspect the action outcome and open the record. A pending, expired or failed proposal is not equivalent to a saved activity. Current permissions are checked at execution as well as during preparation. Undo is available only where a supported operation provides it; do not assume arbitrary history can be erased. Follow the recorded result rather than retrying an uncertain change blindly.
- Explicit confirmation and verified action outcomes
A concrete workflow
Describe
Identify the record and what actually happened.
Inspect proposal
Check target, date, values and required details.
Confirm
Approve only the intended supported change.
Verify record
Open the result and distinguish saved work from a failed proposal.
An illustrative working example
Illustrative scenario: recording a scope discussion
A consultant asks AI to prepare a note about a customer call. The proposal targets a similarly named company, so the consultant corrects it before execution. The note distinguishes a requested addition from an approved change and records the actual discussion date. After confirmation, the consultant opens the customer history and verifies the saved activity. The rollout also tests rejection and a missing-field refusal, so a visible proposal is never mistaken for completed record keeping.
Questions about this topic
Does a proposal already save the record?
No. Review, confirmation and a successful action outcome are separate from preparation.
Can AI change anything in the database?
No. Only supported module operations available under your current permissions can be used.
Can I assume every change is reversible?
No. Undo depends on the specific supported operation. Inspect its outcome and limitations.
What if access changes after drafting?
Execution checks current authority again. A prepared proposal does not preserve old permissions indefinitely.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
HubSpot
Application concept: Review a HubSpot contact match before preparing a customer activity proposal with the correct target.
Salesforce
Application concept: Specify the Salesforce-related company and actual call date before reviewing proposed record values.
Linear
Application concept: Prepare a proposed Linear handover reference while keeping task creation and assignment subject to explicit review.