After the sales call: CRM notes and next steps without retyping

Use a recap that another person can act on

A transcript supports the recap but does not replace review. A tentative date should not overwrite a confirmed event date just because the caller mentioned it.

Distinguish a heard statement from an agreed fact

A sales conversation contains corrections, possibilities and questions as well as final decisions. The recap should preserve that difference. If the customer is considering a larger event, store the uncertainty and the action needed to resolve it; do not turn a possibility into a changed order just because it appeared in the transcript.

Cyrano prepares the recap and the person confirms it. A short note that identifies one uncertainty and an owner can be more useful than a confident paragraph that conceals an assumption.

How Cyrano prepares the record

1. Cyrano builds a call list from CRM next steps and shows the current deal context.
2. The person leads the call. The copilot transcribes both sides and suggests a question, response or next step.
3. After the call it proposes a note, learned facts, next action and date.
4. The person edits and confirms each update. Draft follow-up texts follow message approval rules.

The documented setup is Quo web in Chrome, Twenty CRM and English calls; other environments are scoped. Cyrano does not place calls, decide the deal stage or send texts independently. The team must use the recording/transcription process appropriate to the call and its agreed rules.

Review Cyrano’s working setup and decision boundaries.

Worked example: a Stretch Tent layout change

Synthetic conversation and note. No real customer or transcript is reproduced.

Weak note: “Spoke to customer. Bigger tent, next weekend, deposit. Follow up.” Another operator cannot tell which event changed, whether the date was accepted or what the deposit comment means. It also gives no reason for the next contact.

Useful proposed recap: “Discussed the existing wedding opportunity and current dining-layout quote. Customer is considering 80 guests; final number remains open. Asked whether the following weekend is possible. Owner must review date and layout after the customer sends an updated site photo. Customer said a deposit may have been paid; payment status requires a provider check. Owner to reconnect on the date agreed during the call.”

The reviewer replaces any vague scheduling phrase with the actual agreed action/date, checks the opportunity and confirms what should be saved. The tentative larger headcount stays distinguishable from the prior confirmed fact. The payment claim becomes a verification task rather than a financial update.

A resulting follow-up can then have one clear purpose: request the missing photo or confirm the review conversation. Figaro can help prepare that contact from the updated context. The implementation must suppress an old generic nudge where the agreed rules require it.

Reconcile messages received after the call

The record may change between the call and the operator reviewing a proposed update. A customer might text the final headcount, correct the date or send a photo while the recap is waiting. Review against the latest relevant conversation, not just the transcript in isolation. Preserve the evidence for an important correction.

1. Confirm the note belongs to the intended customer and opportunity.
2. Compare proposed facts with the existing record and any newer message.
3. Resolve contradictions explicitly; keep open questions visible when the answer is still uncertain.
4. Confirm one next action and its owner; pause any obsolete plan through the configured process.
5. Review any customer-facing draft separately from saving the internal recap.

For quality control, record what the person changed in a sample of recaps and why. Repeated wrong-event matches, inferred acceptance or missing due dates suggest a workflow problem to fix. Do not optimize only for the percentage of drafts accepted unchanged; the operator’s correction is part of responsible use.

The supported Cyrano environment and human confirmation boundary still apply. This checklist does not enable autonomous CRM writes, a new telephone integration or a change to the deal-stage rules.

Connect the recap to follow-up

Figaro can help prepare the next customer contact from the updated inquiry context. The implementation should prevent the old generic reminder from competing with the callback agreed on the call. That shared stop rule needs configuration and testing; pairing the agents does not automatically establish it.

See Figaro follow-up preparation.

Choose a message for the current quote state.

Check accuracy and operator effort

• Compare the proposed note with the source conversation and the person’s confirmed version.
• Track incorrect matches, changed facts, missing next actions and time spent reviewing.
• Keep a way to correct the record and determine which version drove a later action.

Make the resulting CRM view useful to the team.

Scope the call-to-CRM handoff.

Questions and answers