Deals

Deals are Yuzu’s memory layer. A deal groups the calls, TLDR videos, public links, emails, LinkedIn posts, engagement events, next actions, and insights that belong to the same buyer conversation.

​

How deals are created

Yuzu tries to resolve the buyer account when a transcript arrives. The safest signals are provider account IDs, CRM IDs, meeting metadata, and email or domain data from notetakers and integrations. When a transcript includes a buyer email, Yuzu can also create the primary contact for the deal. The goal is to avoid making the seller paste the same buyer name, email, and LinkedIn context again after the meeting has already supplied it. When the source does not provide enough reliable metadata, the call stays visible as an unassigned call. It is not deleted or hidden. You can assign it later. Historical imports are more conservative. Older transcripts are kept searchable and assignable, but Yuzu does not automatically create a fresh deal for every old meeting outside the recent-meeting window. Unassigned calls still open inside Deals. Yuzu creates a temporary call page for the transcript so list view and pipeline view behave the same way. After assignment or merge, the call becomes part of the destination deal thread.

​

What a deal contains

• Calls and transcripts
• TLDR videos
• Public Yuzu Links
• Email threads, replies, draft suggestions, opens, and clicks
• LinkedIn post drafts, published posts, reactions, and comments
• Quotes, objections, next steps, and other insights
• Full-call search moments
• Zu-generated next actions and completed actions
• Manual notes, uploaded files, and pasted transcripts

​

Merge and assignment

Merging deals does not delete source records. It only changes the grouping so the deal thread, search, insights, and future recap context use the combined history. Use merge when:

• A notetaker could not identify the customer.
• Two customer names normalize differently.
• A buyer changed domains or showed up through a different source.
• A manual upload belongs to an existing deal.

Use assignment when a single unassigned call belongs to a known customer. Use merge when two buyer threads are really the same conversation.

​

Pipeline fields

Deals can carry pipeline stage and status so the list can be filtered by in-flight, stalled, closed-won, and lost work. These fields are lightweight Yuzu fields, not a full CRM replacement.

​

Signal and next actions

The deal agent reads the deal thread and writes a signal level, signal reason, next actions, and prior completed actions. Every active deal should keep the standard buyer package visible:

• TLDR recap: the short recap video the buyer can replay or forward.
• Business-case page: the buyer-facing page that packages the recap, summary, CTA, transcript, and product assets.

The remaining action is contextual. It usually becomes an email draft, and can become a LinkedIn post when there is a clear LinkedIn reason. Internal requests and missing-context asks are also routed through email because that is the usable seller surface. Email and LinkedIn actions can be sent immediately after review or scheduled for later. Scheduled assets stay editable while they are still drafts. The buyer-package cards do not mean Yuzu re-renders a TLDR on every event. New TLDR generation runs from transcript intake or an explicit click. The deal page keeps the review/send actions visible so the seller knows what package is ready and what still needs work. Use Regenerate when a deal has changed and you want the agent to re-read the current state. Rapid clicks are coalesced so one double-click does not create duplicate agent runs.

​

Archive and delete

Archive removes a deal from active lists but keeps the direct URL available for review. Delete is a soft-delete path: the deal should disappear from lists and agent search, while direct visits resolve to a safe not-found state instead of a broken page.

​

Member visibility

Admins can triage the full workspace. Members see deal activity that belongs to them. If a teammate has their own calls on the same buyer, Yuzu keeps member-scoped views limited to the records that user is allowed to see.