> ## Documentation Index > Fetch the complete documentation index at: https://docs.servicebooked.ca/llms.txt > Use this file to discover all available pages before exploring further. # Working a deal > Day-to-day mechanics — opening, moving, assigning, and closing deals on the pipeline. A **deal** is a specific opportunity tied to a contact. One contact can have many deals over time (each job is its own deal). Deals live on the kanban-style **Pipeline** view, organized into the stages you configured. ## Open a new deal Three ways: ### 1. Manually from the contact Open a contact, click **Add deal**, fill in the title (e.g., "Kitchen remodel"), value (estimated dollar amount), expected close date, and starting stage. ### 2. Auto-opened by a form Forms can be configured to open a deal automatically on every submission. Configure in **Forms → \[form] → Pipeline integration → Open deal**. ### 3. From the Pipeline view On the Pipeline page, click **+ New deal** at the top of any stage column. You'll be prompted to pick a contact (or create one). ## Deal fields * **Title** — short description ("Kitchen remodel", "Annual maintenance") * **Contact** — who it's for * **Stage** — current pipeline column * **Value** — estimated dollar amount (used for revenue forecasting) * **Expected close date** — when you think this'll wrap (drives the "stale deal" warning) * **Assignee** — which teammate owns this deal * **Notes** — anything else ## Move deals between stages Drag and drop. Or click into a deal and change the stage from the dropdown. Both work; drag-and-drop is faster for end-of-day cleanup. Optimistic updates — the card moves instantly, server catches up in the background. ## Assignees Assigning a deal to a teammate gives them a notification and surfaces it in their personal task view. Useful for splitting workload across techs / sales reps. In a solo operation, leave assignees empty (every deal is implicitly yours). ## Stale deals Deals that haven't moved stages in a while turn amber on the kanban (configurable threshold in **Settings → Pipeline → Stale threshold**, default 14 days). This catches deals that fell through the cracks — quoted leads who never followed up, jobs that started but never closed. You can: * **Follow up** — call/text the contact and update the deal. * **Mark Lost / Cancelled** — close it out. * **Push the expected close** — if the timeline shifted legitimately. ## Daily digest If you turn on the **Pipeline digest** in **Settings → Pipeline**, you'll get a daily email summarizing: * Deals you advanced yesterday * Deals that went stale * Deals approaching their expected close date A useful way to keep on top of the pipeline without constantly checking the dashboard. ## Closing a deal When a job wraps: 1. Move the deal to **Completed** (or your configured equivalent). 2. The contact's status updates to match. 3. The reputation feature kicks in — if you have it enabled, a review request schedules automatically (typically 1–3 days post-completion). [More on review requests →](/reputation/sending-review-requests) If you went with a competitor: 1. Move the deal to **Lost**. 2. (Optional) Add a note about why — useful for understanding patterns later. ## Bulk actions On the kanban view, hovering a stage column shows a count + "..." menu with bulk actions for that stage: * Move all stale deals to Lost * Reassign all deals from one teammate to another * Mark all deals in a stage as a specific status Use sparingly — bulk operations on the pipeline can create surprising history if you're not careful. ## Next Conversion rates, time-in-stage, where deals get stuck.