Microsoft Know Your Customer Agent: Give Sales and Support Teams the Customer Context They Usually Have to Hunt For

Sales and support teams rarely lack customer information.

They lack customer information in one place.

Account history may sit in a CRM. Meeting notes live in Teams. Proposals are in SharePoint. Previous issues are buried in email. Product usage data may be somewhere else entirely.

Before an important customer call, an employee often spends 20 minutes rebuilding the story.

Microsoft’s Know Your Customer agent template is designed to shorten that search.

What Is the Know Your Customer Agent?

Microsoft’s Agent Library includes a prebuilt custom agent called Know Your Customer.

Microsoft describes it as an agent for sales and support teams that surfaces customer insights, relationship history, and account context from organizational data.

The basic idea is simple: give the employee a conversational way to ask what the organization already knows about a customer.

What Could Someone Ask?

Imagine an account manager preparing for a call with a long-term customer.

Instead of opening multiple systems, they might ask:

“What are the biggest issues this customer has raised in the last six months?”

“What did we promise during the last renewal?”

“Who are the main stakeholders on this account?”

“What products are they currently using?”

“What opportunities have we discussed?”

“Summarize our relationship with this customer before my meeting.”

That is a very different use of AI from asking a general chatbot to research the company.

The useful information is often internal. It is the history between your company and that customer.

Customer Context Is Usually Fragmented

A CRM may contain the official account record but still fail to capture much of the actual relationship.

Salespeople discuss customers in Teams. Project managers document issues in project systems. Support teams create tickets. Executives exchange email. Contracts and proposals live in SharePoint. Meeting notes may be stored separately.

No single employee necessarily sees the entire picture.

A customer agent can provide a conversational layer over approved sources so employees do not have to reconstruct that history manually every time.

It Can Help Before a Sales Call

Suppose a salesperson is meeting a customer at 2:00 PM.

Before the meeting, they ask: “Give me a briefing on Acme Manufacturing.”

A well-configured agent might surface recent meetings, open opportunities, important contacts, current services, outstanding support issues, recent commitments, relevant proposals, and major changes since the last conversation.

That could substantially improve meeting preparation.

Instead of spending the first ten minutes asking questions your company should already know the answers to, the salesperson arrives with context.

Support Teams Can Use the Same Information

The use case is not limited to sales.

A support representative receiving a customer escalation might ask: “What issues has this customer already reported?”, “Has this problem happened before?”, “Who owns the account?”, “Are there any special service commitments?”, or “What happened during the last escalation?”

This can reduce one of the most frustrating customer experiences: explaining the same history repeatedly to different people inside the same company.

The customer does not care that your information is distributed across four departments. From their perspective, they are dealing with one organization.

The Agent Is Only as Good as the Customer Records

If your CRM is incomplete, meeting notes are inconsistent, support records have poor descriptions, and important commitments live only inside someone’s inbox, the agent cannot manufacture a reliable customer history.

It can retrieve what exists.

That makes knowledge capture part of the implementation.

Important decisions, commitments, exceptions, and customer history need to become organizational knowledge rather than remaining trapped with individual employees.

The broader Maisy model treats this as institutional knowledge: the information and context necessary for employees to operate consistently should be captured, organized, governed, and made retrievable rather than depending on memory.

Permissions Matter Immediately

Customer information can be sensitive.

Sales employees may need access to commercial history. Support staff may need service information. Finance may have billing data. Executives may have confidential negotiation details.

Not every employee should necessarily see all of it.

That means a customer agent should not be connected to every source using one broad service identity.

The underlying permission model still matters.

Maisy’s security architecture follows the same rule: AI should retrieve only information the user is authorized to access, with permissions enforced through identity, groups, and source systems rather than relying on the agent to hide sensitive information after retrieval.

It Can Be Expanded Beyond Internal Data

Microsoft also provides related customer-insight capabilities that can gather external company information such as industry, products, leadership, competitors, priorities, and market trends.

That suggests a powerful combined model.

Internal information answers, “What is our history with this customer?”

External information answers, “What is happening with this customer as a business?”

Put the two together and an account manager could prepare for a conversation with much stronger context.

The important part is keeping those information types distinguishable.

Public research should not quietly become confused with internal facts or approved account records.

What Microsoft Gives You

Agent Library templates are designed as functional starting points that can be customized with an organization’s own topics, knowledge sources, and components.

The organization still needs to determine which customer systems are authoritative, which sources should be connected, what employees are allowed to access, which account history is reliable, what information should be excluded, how the agent should handle conflicting information, and how answers will be tested.

Why Know Your Customer Is Valuable

Most companies already spend money collecting customer information.

The problem is that employees often cannot retrieve the full context when they need it.

That causes duplicated questions, weak handoffs, missed commitments, and conversations that make the organization look less coordinated than it actually is.

A Know Your Customer agent can help turn scattered account information into usable relationship context.

It does not replace the salesperson.

It makes sure the salesperson doesn’t walk into the meeting blind.