Skip to main content
Yuzu turns GTM activity into deal signal. A signal is an observed event with enough context to affect a deal, a trigger, or a generated follow-up artifact.

​
Signal sources

Yuzu can collect signal from:
  • Notetaker transcripts and manual transcript uploads
  • Gmail sends, opens, clicks, and replies
  • LinkedIn post reactions and comments
  • Public Yuzu Link views
  • Rendered-video views, completions, and CTA clicks
  • Manual deal events and notes

​
How signal reaches a deal

When a new event lands, Yuzu tries to resolve the workspace, user, deal, contact, and source artifact. If it can attach the event to a deal, the deal activity feed updates and the deal agent can re-evaluate the next actions. Signals are normalized before they reach the deal agent. That keeps the model focused on what happened instead of making it infer event meaning from raw webhook payloads.

​
Triggers

Triggers are recurring patterns or conditions that should change the seller’s behavior. Examples:
  • Buyer asks for a timeline and pricing.
  • A stakeholder engages with a LinkedIn post.
  • A public page is viewed after a period of silence.
  • A video is watched to completion and the CTA is clicked.
  • A contact replies with a concrete objection or request.
Triggers can feed next actions, content suggestions, and agent-generated work. For deal next actions, Yuzu keeps the buyer package stable: TLDR recap plus business-case page. The trigger usually decides the third move, such as drafting a follow-up email, preparing a LinkedIn post, or asking for missing context through an email draft.

​
Deal signal level

Deal pages show signal level and reasoning when the agent has enough context. The current levels are:
  • High: recent multi-party motion, direct engagement, or urgent buyer action.
  • Medium: normal active motion with a clear next step.
  • Low: stalled, silent, or waiting on seller action without strong buyer engagement.

​
Regeneration

Click Regenerate on a deal when you want the deal agent to re-read the current state. Rapid clicks coalesce so a double-click does not create duplicate agent runs. When multiple events arrive close together, Yuzu queues one follow-up agent run instead of dropping the later signal or creating duplicate traces.