Streak

Streak carries a box as the opportunity object, and contacts and organizations as separate record types, each with its own page holding contact details and the team's interaction history. A contact is an individual identified by name or email address and an organization is a company identified by its domain, and both are attached to a box through a Contacts and Organizations column, so a box can carry both at once and neither is compulsory. Contacts and organizations sharing a domain are surfaced against one another as related records. Activities exist as tasks, call logs and meeting notes held against the box rather than attached directly to a contact or organization.

Source: https://support.streak.com/en/articles/3623777-contacts-and-organizations, https://support.streak.com/en/articles/2563457-custom-columns, https://support.streak.com/en/articles/2563490-boxes, https://support.streak.com/en/articles/11321068-list-of-contacts-and-organizations

Verification: Verified

A pipeline is an ordered set of stages and a box moves through those stages until the workflow is complete. Stages are configured from the pipeline's stages and columns settings, where they can be added, renamed, deleted, recolored and dragged into a new order. Stage is one of the foundational columns present in every pipeline.

Source: https://support.streak.com/en/articles/2761926-what-is-a-pipeline, https://support.streak.com/en/articles/2562671-customizing-a-pipeline, https://support.streak.com/en/articles/2542963-terminology

Verification: Verified

No enumeration of the properties Streak ships on the box object could be read, so absence cannot be evidenced. What is reachable is the write side and an admin article: the create-a-box endpoint documents name, stageKey, notes and assignedToSharingEntries, the edit-a-box endpoint documents name, notes, stageKey, followerKeys, linkedBoxKeys, assignedToSharingEntries, contacts, organizations and fields, and the support article on adding and deleting pipeline columns names Name, Stage, Assigned To, Contacts and organizations, and Notes as the columns present in every pipeline. A request-body parameter list is not the object's field list - it omits every read-only property - and a column-management article is the same genre of source that missed Pipedrive's shipped deal status attribute. Streak's own object model page enumerates nothing beyond key and boxKey.

Source: https://support.streak.com/en/articles/2542963-terminology, https://support.streak.com/en/articles/3403969-adding-and-deleting-pipeline-columns, https://streak.readme.io/reference/update-a-stage

Searched: Streak API reference at streak.readme.io: get-a-box, create-a-box, edit-a-box, list-all-boxes-in-pipeline, getting-a-specific-pipeline, get-a-stage, create-a-stage and update-a-stage; the guides Basic Object Model, Getting Started, Requests and Responses and Setting up Streak with Postman; and the support articles on terminology and on adding and deleting pipeline columns. Every reference page renders its response section as an unpopulated Try It placeholder, so no box response schema or example payload could be read, and the vendor's OpenAPI index at streak.readme.io/llms.txt and the appended-.md markdown versions of the reference pages were not reachable from this session. No documented complete field list for the box object was obtained.

Verification: Pending vendor verification

Same gap. Streak documents that its sales reports work when a pipeline has a value column and a Won stage, defines close rate as the share of boxes won out of all boxes, and the create-a-stage endpoint takes a name and nothing else, which suggests won and lost are stage names the buyer types. But no reachable source enumerates the box object's properties or the stage object's properties, so the claim that no won, lost or outcome attribute ships cannot be evidenced.

Source: https://support.streak.com/en/articles/2514184-pipeline-reports, https://streak.readme.io/reference/update-a-stage, https://support.streak.com/en/articles/3403969-adding-and-deleting-pipeline-columns

Searched: As status_searched. The create-a-stage endpoint documents a single name parameter and the get-a-stage page renders no response schema, so the stage object's full property set is also unenumerated.

Verification: Pending vendor verification

No amount column ships; value must be added as a custom or magic column.

Source: https://support.streak.com/en/articles/3403969-adding-and-deleting-pipeline-columns, https://support.streak.com/en/articles/2414716-using-contacts-and-organizations

Verification: Verified

A Notes column ships in every pipeline, but it is generic free text, not a scope or line-items facility.

Source: https://support.streak.com/en/articles/3403969-adding-and-deleting-pipeline-columns, https://support.streak.com/en/articles/2414716-using-contacts-and-organizations

Verification: Verified

No date column ships; the buyer creates one.

Source: https://support.streak.com/en/articles/3403969-adding-and-deleting-pipeline-columns, https://support.streak.com/en/articles/2414716-using-contacts-and-organizations

Verification: Verified

No date column ships in a pipeline. Streak's own projected close value report is documented as reading close dates from an expected close date column the buyer adds, and the magic column families on offer cover activity metadata such as the last stage change, email counts and task progress rather than a settled date. Anything holding the date a sale ended has to be created by the buyer. Ruled 30 Aug 2026: the close date must be a native system field. It is the field the conversion rate report counts a closed opportunity by, so a date the buyer has to build is a fail, not a shortfall.

Source: https://support.streak.com/en/articles/2514184-pipeline-reports, https://support.streak.com/en/articles/3403969-adding-and-deleting-pipeline-columns, https://support.streak.com/en/articles/2563465-magic-columns

Verification: Verified

Assigned To is one of the columns present in every pipeline.

Source: https://support.streak.com/en/articles/3403969-adding-and-deleting-pipeline-columns, https://support.streak.com/en/articles/2414716-using-contacts-and-organizations

Verification: Verified

Contacts and Organizations is a default column linking a box to people as well as companies.

Source: https://support.streak.com/en/articles/3403969-adding-and-deleting-pipeline-columns, https://support.streak.com/en/articles/2414716-using-contacts-and-organizations

Verification: Verified

A box that reaches a closing stage stays in its pipeline and keeps counting. Close rate is calculated as the percentage of boxes won out of all boxes and close rate in value as the percentage of value moved to the Won stage, and funnel reports count how many boxes made it from one stage to the next, so settled work remains part of the product's own reporting.

Source: https://support.streak.com/en/articles/2514184-pipeline-reports, https://support.streak.com/en/articles/6843564-funnel-reports

Verification: Verified

Streak documents no lost reason concept anywhere. What it documents is a general dropdown column type offering a single selection from a predefined list, which can be added to any pipeline and reported on through the Boxes by Column report, which breaks boxes down by the values held in a chosen column. A structured, reportable lost reason is therefore achievable and reportable, but it is a field the buyer defines rather than one the product supplies or names.

Source: https://support.streak.com/en/articles/2563457-custom-columns, https://support.streak.com/en/articles/2514184-pipeline-reports

Verification: Verified

Streak runs inside Gmail, so mail is composed, sent and received in the same client the CRM lives in, and an email can be attached to a box from the inbox, from the inbox view, from the compose window or from an existing thread. Automatic email sharing can be switched on per contact and per organization so that correspondence with that person or company is added to the box without manual action, and a teammate's shared mail is pulled into the same box timeline. There is no separate mailbox to reconcile, and no BCC dropbox is required. The capability is tied to Gmail and Google Workspace accounts.

Source: https://support.streak.com/en/articles/4300110-overview-automatic-email-sharing, https://support.streak.com/en/articles/2563490-boxes, https://www.streak.com/

Verification: Verified

A task carrying a due date is automatically created as an event in the user's Google Calendar, and changing the due date in Streak updates that event; clicking the event opens the associated box. Vendor documentation describes the flow only in that direction and does not describe an event created in the external calendar becoming a Streak task or activity, and no Google Calendar or Outlook calendar integration article appears in the integrations collection. The sync is therefore one-way from the activity object outward.

Source: https://support.streak.com/en/articles/2563556-follow-up-tasks, https://support.streak.com/en/collections/1398578-integrations

Verification: Verified

Tasks are created from inside a box, from the Gmail sidebar or from the global upcoming list, and carry a free-text title, a due date set by picker or natural language, and an assignee, so future work of any description can be scheduled without leaving the CRM. The dimension fails on type. A task has no type attribute, and the only other activity records are call logs and meeting notes, two fixed record types that document a conversation after the fact and cannot be scheduled forward. A naming convention in the task title cannot substitute, because nothing in the product reads that text: the only documented narrowing control on the task list is a pipeline picker, the command palette searches boxes, pipelines, saved views, contacts and organizations rather than tasks, and the API's read-tasks endpoint takes no text parameter. Task data does reach reporting, but only in aggregate and never as text - the task magic columns are counts, percentages, dates and assignee sets, with no column carrying the task title, and the pipeline reports run on boxes and their columns.

Source: https://support.streak.com/en/articles/2563556-follow-up-tasks, https://support.streak.com/en/articles/2569566-call-logs-meeting-notes, https://support.streak.com/en/articles/2563465-magic-columns, https://support.streak.com/en/articles/2466406-filter-sort-and-group-boxes-using-saved-views, https://streak.readme.io/reference/read-tasks-on-a-box

Verification: Verified

One of the three exists, and the rule requires two. Reports are widgets on an in-app dashboard reached from the pipeline menu, distinct from Streak's pipeline export. Close Rate calculates the percentage of boxes won out of all boxes, with a value-weighted variant, and that is a stated rate. The other two fail. A stage-to-stage conversion rate is not documented: the funnel report shows where boxes drop off and how many made it from one stage to the next, which is a count, and Stage Flow, Stage Entrances and Exits and Time in Stage report movement, volume and duration rather than a percentage; a vendor blog article does describe a percentage converted from each previous stage, but that claim appears in no knowledge base article. The forecast fails on the underlying data rather than on the report: Projected Close Value projects revenue from close dates held in a pipeline column, but the only columns present in every pipeline are Name, Stage, Assigned To, Contacts and Organizations, and Notes, so the expected close date column is created by the buyer and there is no first-class expected close date field. The value column and the Won stage are buyer-created on the same footing, and no lost status exists.

Source: https://support.streak.com/en/articles/2514184-pipeline-reports, https://support.streak.com/en/articles/6843564-funnel-reports, https://support.streak.com/en/articles/6871687-advanced-reporting, https://support.streak.com/en/articles/2563457-custom-columns, https://support.streak.com/en/articles/2514616-export-a-pipeline

Verification: Verified