Notes

Notes are rich-text records your team adds in FunnelStory—or that arrive from an imported Note model—and attach to one or more accounts. Use them when you want durable, human-written context (QBR prep, escalation history, meeting recap) alongside synced system data.

How notes work

Each note has a title, body, note type (General or Meeting in the composer), an event date (defaults to today; you can backdate), and one or more associated accounts. You can add labels (multi-select under Select labels), @mention workspace users in the body (they can get email when mentioned), and save. Notes created in the product are editable; imported notes (rows from a Note model refresh) show as read-only in the UI—Edit is disabled for imported notes.

Imported notes carry stable note_id values from the source; FunnelStory upserts on refresh so the same external row updates in place.

Where you see and manage notes

Notes on an account

Open an account, then the Notes tab (alongside Properties, Meetings, and Tasks). You can browse notes for that account, open the editor, and create new ones in context.

All notes

Use the workspace Notes page (path /notes) for a cross-account list. The toolbar supports time range filtering, narrowing to one account, My accounts (assignee filter for the signed-in user), pagination, and New note to open the composer without starting from a single account.

Tasks

When creating or editing a task, use Add/Remove notes to link existing notes to the task as associations so the task carries the same narrative context.

Comments on tasks

The task detail Comments thread is separate from account-level Notes; use comments for short discussion on the task itself, and Notes when the write-up should live on the account and be reusable elsewhere.

Slack, conversations, and imported rows

Slack content can surface in FunnelStory in different ways:

• Slack connection → conversations — Adding a Slack connection indexes channel messages and threads for conversation-style features tied to accounts. That path uses the Conversation model (a Conversation model may be created for you after you connect—see the Slack connection page). It is oriented around threaded chat intelligence, not the same pipeline as manually authored Notes.

• Rows in the Notes list — The in-app Notes surface is fed by notes your users create plus rows ingested through the Note model. There is no direct “Slack → Note” control in the product. To land Slack-derived (or Slack-exported) content as first-class notes—with note_id, title, body, timestamps, and optional author email—typically model it in a queryable source (warehouse, CRM, etc.) and map it through the Note data model. Imported notes stay read-only in the UI; change them at the source and refresh the Note model.

For timestamp vs created_at on imports, see the Note model field reference.

Labels and default templates

Labels help teams categorize notes; pick them in Select labels when creating or editing. The composer loads labels configured for your workspace—if you need new label values, work with your FunnelStory admin (label maintenance is not a self-serve settings screen in the app today).

On the workspace Notes page, combine time and account filters with label chips to narrow large histories.

Your workspace can store default templates per note type (general and meeting) that pre-fill title, body, type, and labels when someone starts a note. Placeholders in template text:

Placeholder	Replaced with
{{ACCOUNT_NAME}}	The active account name when opening the composer from an account.
{{DATE}}	Today’s date in the workspace display format when the composer loads.

Audit trail

Creating, updating, or deleting a note generates audit log entries your admins can review. See Audit log.

Related

• Note model — importing notes from CRM or warehouse queries.
• Accounts — notes attach to account records from your Accounts model.