Salesforce Case fields: the standard field reference

The Salesforce Case — a customer support issue or request — carries standard fields for tracking and routing support work. A few of them interlock with queues, status, and escalation in ways worth knowing. This covers those, and the full standard-field reference has the table across the core objects.

The identifier and the summary

• CaseNumber (Auto Number, read-only) — the unique, auto-generated case number. You never set it; Salesforce assigns it on create, and it can't be edited. It's the human-friendly reference customers quote.
• Subject (Text) — a short summary of the issue.

Status, and the read-only close flag

• Status (Picklist) — where the case is in its lifecycle.
• IsClosed (Checkbox, read-only) — system-maintained from the status. When the case is set to a status marked as "Closed," IsClosed flips to true on its own. You move the status; you don't check this box.

Routing: priority, origin, and queues

• Priority (Picklist) — how urgent the case is; drives a lot of SLA and assignment logic.
• Origin (Picklist) — the channel it came in through: email, web, phone, and so on. Web-to-Case and Email-to-Case set this.
• Type (Picklist) and Reason (Picklist) — categorization for reporting and routing.
• OwnerId (Lookup to User or Queue) — like leads, a case's owner can be a queue, not just a user. That's what powers case queues and assignment rules. Automation shouldn't assume the owner is a person.

Relationships and escalation

• ContactId (Lookup to Contact) and AccountId (Lookup to Account) — who reported it and their account. The account is often auto-filled from the contact.
• IsEscalated (Checkbox) — the flag escalation rules act on. If cases are escalating (or not) unexpectedly, this field and the escalation rules are where to look.

The honest catch — this is the standard set, not your support process

Every field above is in every org. What makes your Case object yours is the custom fields your support team added — the product-area picklist, the CSAT score, the fields a channel integration writes — plus your specific status and priority values and how they route. A reference can't describe those.

SchemaForce inventories every field on Case (standard and custom), describes each, and shows usage and field-level security — so your support data model, and who can see what on it, is documented instead of tribal.