Done — with a note that lands on the card

Marking a meeting done asks what happened, and the answer is written into the contact's note stream with the meeting type and time as its heading.

What it is

The note is stored in the same unified note stream everything else uses, sequenced, attributed to the person who wrote it, and recorded in the note revision history. The card's last-action time updates.

Also called: meeting notes · what happened on the call · log the outcome

See it
Done — with a note that lands on the card
Apr
May
Jun
Jul
Sutter Kline — Riding Arena
Framing
Ivy Brubaker — 30×40 Garage
Concrete
Ronan Petsch — Riding Arena
Trim
Delia Yoder — 30×40 Garage
Framing
Sutter Kline — Riding Arena
Concrete
Framing crewConcrete crewTrim crew
The Done dialog's note box, then the resulting note in the contact's stream. agencyAppointmentFlow.ts. Sample data — no customer information appears here.
How it works
  1. 1The outcome is saved on the appointment and, when there is a linked card and a non-empty note, inserted as a note with source 'agency_appointment'.
  2. 2The note's heading is the meeting type and the long-form date and time.
  3. 3A revision row records the creation with its author.
Why we built it

Meeting outcomes that live only on the calendar are invisible to whoever picks the deal up next; routing them into the contact's one note stream means the history reads in one place.

The problem
  • Outcomes trapped on a calendar entry
Sound familiar?
What you get
Call outcomes in the customer's own history
Attribution and revision history for free

See it on your own jobs

Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.

or keep browsing features →