OppFlow.ai Docs

Working deals

Activity, calls & email

The timeline on a deal is a union of four sources, not one query — activities, notes, tasks and synced mail, merged and sorted.

Filter pills

All, Emails, Meetings, Calls, Notes and Tasks, each carrying a live count. A kind with nothing in it gets its own empty state and a “show all activity” escape, rather than an empty list you cannot tell apart from a loading failure.

Source pills

Every row states where it came from and, when something went wrong, why:

SALESFORCESynced from the CRM.
PENDING SYNCQueued for write-back. It clears when the CRM accepts it; a write that keeps failing stays pending rather than reporting a reason.
LOCAL ONLYLives in OppFlow by design.
MARVINAuto-captured, with an ask-Marvin follow-up.
SYNC FAILEDNames the reason and offers a retry.

Logging a call

Pick a direction (outbound, inbound, voicemail), then participants — drawn from the deal's relationship map, falling back to the account's contacts. Set when and how long, write a summary, choose an outcome (advanced, held steady, new blocker, needs exec). A follow-up task is checked by default and its title and due date track the outcome you picked. Participants and a summary are required.

Email and meetings

Rows sourced from your mailbox open a thread reader with a per-thread Marvin summary and a reply or draft-with-Marvin action. Meetings open a prep screen with attendees, agenda and Marvin's brief. Attendees on a CRM-logged meeting are reconstructed — a CRM activity has no invitee list — and the rail says so instead of rendering an empty column.

OppFlow.ai docs · by Traversal · v0.1.32