Case Closed: Should it become a Knowledge Article?
In Dynamics 365 Customer Service, many organizations dictate that every case should become a knowledge article. The thinking is usually well-intentioned: customer service representatives should “document everything” so the organization does not lose valuable knowledge. But over time, that approach can create a different problem. Instead of a helpful knowledge base, the organization ends up […]
The post Case Closed: Should it become a Knowledge Article? appeared first on .
Published on:
Learn moreWe can help you with Case Closed: Should it become a Knowledge Article?
If you want help implementing, troubleshooting, or improving this product, contact us and we’ll point you in the right direction.
Related posts
Beyond Plain Text: New Ways to Display Data in Dynamics 365 Views
Let’s face it, staring at rows and columns of plain text isn’t always the easiest way to understand your data. Sometimes a quick v...
Environment Variables in Power Automate
Environment variables let you store values that may be different in each environment instead of hard coding those values directly inside your ...
Dataverse Formula Column Surprises, and How to Handle Them
Formula columns are one of the best innovations in Dataverse. They user Power Fx, they are easier to build than the old classic column designe...
When a calculated column wins over a formula column
Formula columns have been available in Dataverse for a few years now, and Microsoft has made it clear that they are the preferred option going...
Business Process Flows in Dynamics 365 CE
Let’s look back at an oldie but a goodie in Dynamics 365 CE/CRM: Business Process Flows! These are designed to standardize how records m...