Understand how deal records work in Sanka, including sales pipeline stages, owners, next actions, quotes, orders, support-ticket boundaries, and AI checkpoints.
Last updated: May 29, 2026
The Deal object stores sales opportunities and pipeline work. Use deal records to track a potential sale from early interest through qualification, quoting, order creation, invoicing, and follow-up.This reference explains what a deal should contain, how it connects to customers, contacts, estimates, orders, invoices, tasks, and workflows, and what to check before creating, updating, importing, converting, or troubleshooting deals with AI, actions, workflows, CSV, integrations, or manual entry.Some older labels, redirects, or CSV pages may use the word “case.” In current public docs, treat this object as the Deal object for sales pipeline work. Customer support issues should be handled through your support process and Support Home, not mixed into the sales deal pipeline unless your team intentionally tracks support work there.
Claude/Codex
Review this deal before updating it. Show customer, contact, owner, stage, probability, amount, expected close date, next action, related quote/order/invoice, duplicate risk, stale activity, and missing fields. Do not update the deal yet.
Reviewing dealI reviewed the deal. Please confirm customer, owner, stage, probability, amount, next action, related records, and duplicate risk before updating.
Ask for another deal check...
What a deal record represents
A deal record represents a potential commercial opportunity with a customer. It should help your team answer:
Who is the customer and main contact?
What is the opportunity about?
Who owns the next step?
What stage is the deal in?
How likely is it to close?
What amount, close date, or terms are expected?
What quote, order, invoice, or task is connected to the opportunity?
Common fields include:
Deal ID or record ID
Deal name
Customer company and contacts
Record owner
Stage, status, probability, priority, and expected close date
Amount, currency, products, services, or line items
Next action, due date, notes, and tasks
Related estimates, orders, invoices, subscriptions, contracts, messages, and files
Source details from UI, CSV, integrations, actions, workflows, CRM imports, or AI-assisted creation
Workspace admins can customize deal fields and stages, but sales pipeline, reporting, quoting, and AI-assisted checks should still be able to understand the lifecycle.
Deal, case, and ticket naming
Use these public meanings when reviewing docs or support questions:
Deal: a sales opportunity or commercial pipeline record
Case: an older or legacy name that may still appear in some paths, imports, or settings for the same sales opportunity object
Ticket: a customer support issue or support conversation when your workspace has a ticket/support workflow enabled
If a customer asks about a sales pipeline, quote, order, or opportunity, use deal guidance. If they ask about a bug report, product complaint, support reply, or help request, use support guidance and the relevant product docs before changing deal records.
How deals connect to other records
Deals connect CRM activity to quote-to-cash operations.
Companies and contacts: the customer, decision maker, billing contact, or champion
Estimates: quote drafts or customer-facing proposals created from deal context
Orders: accepted commercial agreements after the deal is won or approved
Invoices and payments: billing and collection after an order or approved handoff
Subscriptions: recurring revenue created from a won deal or order
Tasks and messages: next actions, follow-up, and communication history
Reports and dashboards: pipeline amount, stage, probability, owner performance, and forecast
Workflows and actions: stage updates, quote creation, order creation, owner assignment, and follow-up automation
Creating or updating a deal does not always create estimates, orders, invoices, tasks, or support tickets. Those downstream records depend on the action, workflow, integration, permissions, and team process.
Review deals before changing them
Ask AI to review the evidence before changing stage, probability, owner, amount, or next action.
Sample prompt
/sanka Check this deal before changing it. Compare customer, contact, owner, stage, probability, amount, expected close date, next action, recent activity, related estimates, orders, invoices, duplicate deals, and permissions. Ask for missing context before suggesting updates.
For CRM imports or CSV updates, ask for a mapping and duplicate review first.
Sample prompt
/sanka Review this deal import before running it. Map customer, contact, deal name, owner, stage, probability, amount, close date, source ID, and duplicate key. List rows that need manual review. Do not run the import yet.
Expected behavior
When a deal is created or updated successfully:
It appears in the Deal object list unless it is archived or filtered out by the current view
Customer, contact, owner, stage, probability, amount, close date, source, and next action are saved
Related estimates, orders, invoices, subscriptions, tasks, messages, files, and reports can be associated with it
Stage and probability changes can affect pipeline reports and forecasts
Actions and workflows can create quotes, tasks, orders, or follow-up records when configured
CSV imports, integrations, actions, workflows, and AI-assisted changes still follow required fields, permissions, matching rules, and validation
Deal updates do not bypass approvals, required fields, view filters, duplicate checks, permissions, workflow conditions, or integration mapping. If a downstream record is missing, first check whether the conversion or workflow was configured and completed.
Troubleshooting
A deal is missing from the list
Check the current view, archive state, owner, stage, filters, customer association, permissions, module availability, and whether the deal exists in another workspace or was imported with a different source ID.
A deal is duplicated
Check company/contact matching, CRM source ID, CSV matching key, import mode, integration mapping, and whether both manual and automated creation were used. Confirm which deal has the correct activity and downstream records before archiving duplicates.
Stage or probability looks wrong
Review recent activity, last customer response, quote status, order status, owner notes, workflow updates, and whether probability is manually managed or automated by your team.
A quote, order, or invoice was not created from the deal
Check whether the deal has the required customer, line items, amount, status, approval state, and action/workflow configuration. Also check whether the downstream record already exists.
A support issue was created as a deal
If the record is actually a product question, complaint, or bug report, move the work to your support process. Do not change pipeline reporting just to track a support issue unless your team intentionally uses deals for that workflow.
AI cannot decide whether this is a bug
Ask AI to compare the deal source, customer, owner, stage, probability, required fields, related records, import history, integration mapping, action/workflow history, permissions, and audit trail. Treat it as a possible bug only after confirming the deal setup and source data are correct.
Checkpoints
Before updating stages, changing owners, importing deals, creating quotes/orders, merging duplicates, or replying to a deal support case, check customer, contact, owner, stage, probability, amount, close date, next action, related records, duplicate risk, source, permissions, and audit trail.
Search Sanka...
Review deal lifecycle
Logs
Search logsAll actionsAll dates
ID / ActionDateTarget / ItemChangeActor
3Deal reviewed2026/05/20 10:00Green Salon Group / DealChecked customer, owner, stage, amount, probability, and next actionClaude / Codex
2Quote draft created2026/05/20 11:00Estimate 0042Created quote draft after deal reviewSales user
1Order handoff checked2026/05/22 09:30Order from Estimate 0042Confirmed quote was approved before order draftSales operations
Deal review should separate sales pipeline changes from support issues, and should confirm downstream quote/order/invoice coverage before changing records.
