How to govern ServiceNow Now Assist
AI summarising tickets, drafting replies and routing work across IT and HR service desks.
ServiceNow · Reviewed when the vendor ships a capability change or a customer declares the tool
How ServiceNow Now Assist is used
We see four common ways businesses use ServiceNow Now Assist, and we govern each one on its own terms. If your team uses it differently, that is fine: you describe the use in your own words and Certrak works out the governance from what it actually does.
General productivity assistance
Consequence to people: LowDrafting, summarising, brainstorming, internal Q&A - day-to-day help with internal work
Customer communications drafting
Consequence to people: MediumDrafting customer emails, support replies, or other outbound communications - reviewed before sending
Customer-facing chatbot or automated support
Consequence to people: HighInteracting with customers directly, without a person reviewing each response
Workflow automation across systems
Consequence to people: MediumAutomating tasks across business systems - triggers, data movement, decisions in workflows
Governing ServiceNow Now Assist in practice
- Name one person who owns ServiceNow Now Assist in your business. Governance starts with a name.
- Write down what ServiceNow Now Assist is used for. Certrak recognises 4 common uses: General productivity assistance, Customer communications drafting, Customer-facing chatbot or automated support and Workflow automation across systems. Yours may differ; write down yours.
- Decide what ServiceNow Now Assist may and may not be given. Personal information is in scope for some uses; write the boundary down before it is needed.
- There is no human review of outputs. Decide whether that is acceptable for each use, and what would make you change it.
- ServiceNow Now Assist can send messages outside the business and create, change, or delete records in another system without a person approving. Record which of these you allow, and who can change that.
- Look at this again every month, and sooner on any of these: industry incidents, vendor model updates, autonomy level changes and data classification changes.