Impact and Risk Analysis for Replacing the Contact field with a Custom Table user in the Case form

suresh91
Kilo Sage

Hi All,

I have a requirement to replace the standard Contact field with a custom table–based user reference on the Case form only. Before proceeding, I would like to understand the potential challenges and risks involved. I have listed a few based on my current knowledge.
Please review and let me know if there are any additional points to consider.

  • SLA behavior depends on the caller’s time zone. If the correct contact information is not maintained, SLAs may not function as expected and could breach.
  • Inbound and outbound email notifications may fail, because case updates sent via email rely on matching the sender with a valid Contact/User record.
  • Workspace-level reports and dashboards (e.g., “Tickets assigned to me”) will not work correctly without proper contact/user associations.
  • CSM Portal widgets such as My Cases and Create Case rely on accurate contact-case relationships and may not function properly.
  • New ACLs must be created to accommodate the updated data model.
  • Existing ACL logic and all case‑related scripts,flows using fields like current.contact, current.account, or current.contact.account will need to be rewritten.
  • Integrations that depend on contact‑case or account‑case mapping must be reworked.
  • Any upgrade enhancements related to the contact–case relationship will no longer apply.
  • Contact → Account auto‑population will break, affecting how cases are linked to accounts.
  • The case form will require re‑customization, including logic such as Contact → Email auto-fill.


Thanks
Suresh

2 REPLIES 2

sanjaygupta
Tera Guru
 

I would recommend keeping the standard Contact field unchanged. In CSM, the Contact field references customer_contact, which maintains important relationships with Accounts, Cases and other customer records.

Replacing it with a custom table reference can affect several out-of-the-box functionalities.

A few additional points to consider:

  • SLA calculations may be affected if they depend on the Contact's time zone.

  • Inbound email processing and outbound notifications may need updated sender and recipient mapping.

  • Workspace reports and dashboards using the standard Contact field may require changes.

  • CSM Portal features such as My Cases and Create Case need to be validated.

  • Existing ACLs, Business Rules, Client Scripts, Flows and Script Includes referencing current.contact may need updates.

  • Contact-to-Account and Contact-to-Email auto-population logic will need to be recreated.

  • Integrations and REST APIs relying on the standard Contact reference may require mapping changes.

  • Account, entitlement and case visibility relationships must be tested.

  • Customizing the out-of-the-box field can introduce upgrade and maintenance challenges.

I would suggest keeping the standard Contact field and adding a separate custom reference field instead. You can then build the required mapping without disrupting existing CSM functionality.

Also, check whether your custom table extends sys_user or is completely independent, as this will influence the implementation.

For reference: ServiceNow Community – Use the Contact and User Table to Create a Case.

 
Hope you find this helpful.

Sharath Chandra
ServiceNow Employee

What is the use case you are trying to address? Account and Contact are core fields to customer service management which drive the whole "Customer service management" capabilities.