What Meetings does
| Surface | Operating use |
|---|---|
| On-device recorder | Captures the call locally first. No cloud upload until you approve. |
| Auto notes | Summary, decisions, owners, follow-ups, and unresolved evidence drafted as the call ends. |
| Trade memory link | Decisions are attached to the account, supplier, lane, or shipment they touched. |
| Searchable later | Ask Ubik what was said, who agreed, what changed, and what still needs action. |
A typical meeting loop
01 · Capture Record the call locally when it may affect price, timing, supplier reliability, customer expectation, or owner accountability.
02 · Review Check the drafted summary, decisions, owners, follow-ups, and sensitive context before attaching it.
03 · Attach Link the notes to the account, supplier, lane, shipment, or project the conversation changed.
04 · Follow through Ask later what was promised, who owns it, and whether the operating queue reflects the commitment.
Local-first by default. Recordings live on the operator’s device unless you attach them to the workspace. Sensitive supplier pricing, margin context, and customer commitments stay under operator control.
Useful prompts after a meeting
| Situation | Ask Ubik |
|---|---|
| Decision recovery | ”What pricing, timing, or recovery commitment did the supplier make in the May 12 review, and what evidence supports it?” |
| Owner check | ”Who owns the FDA-hold follow-up from yesterday’s call, and is it reflected in the task queue?” |
| Follow-up draft | ”Draft the recap email for the freight forwarder sync with commitments, open evidence, and owner names.” |
| Account memory | ”Show every meeting where this buyer’s floor price, substitution tolerance, or delivery-risk concern came up.” |