This post is a part of the AB-620: Designing and Building Integrated AI Agent Solutions in Copilot Studio Exam Prep Hub.
This topic falls under these sections:
Plan and configure agent solutions (30–35%)
   --> Configure topics
      --> Configure agent response formatting

Note that there are 10 practice questions (with answers) at the end of each section to help you solidify your knowledge of the material. Also, there are 4 practice tests with 30 questions each available from the hub's main page below the exam topics section.

Introduction

One of the most important responsibilities of an AI Agent Builder is designing responses that are easy for users to read, understand, and act upon. Even if an agent provides accurate information, poorly formatted responses can confuse users and reduce confidence in the solution.

Microsoft Copilot Studio provides several methods for formatting responses, ranging from simple text to sophisticated interactive experiences using Adaptive Cards. Choosing the correct response format depends on the audience, communication channel, business process, and complexity of the information being presented.

For the AB-620 exam, you should understand not only how to configure response formatting, but also when each formatting option should be used.

Why Response Formatting Matters

Well-designed responses help users:

• Understand information quickly
• Complete tasks efficiently
• Reduce misunderstandings
• Improve user satisfaction
• Increase adoption of AI agents
• Reduce unnecessary follow-up questions

Poorly formatted responses often lead to:

• Long walls of text
• Missing important information
• Difficult navigation
• User frustration
• Increased support requests

Types of Agent Responses

Copilot Studio supports multiple response formats.

Plain Text Responses

The simplest response format.

Example:

Your request has been submitted successfully.

Advantages

• Fast
• Works across all channels
• Universal compatibility

Limitations

• Limited visual appeal
• Difficult to organize large amounts of information
• No interactive elements

Best used for:

• Confirmations
• Greetings
• Short answers
• Status messages

Rich Text Responses

Rich text improves readability by organizing information.

Examples include:

• Headings
• Paragraphs
• Bullets
• Numbered lists
• Hyperlinks
• Basic formatting

Example

Instead of:

Your laptop has shipped. Tracking number 123456. Expected delivery Friday.

Use:

Your Order Has Shipped

Tracking Number:

123456

Expected Delivery:

Friday

Rich text greatly improves the user experience.

Markdown Formatting

Many Copilot Studio responses support Markdown formatting.

Common Markdown elements include:

Bold

**Important**

Result:

Important

Italics

*Reminder*

Result:

Reminder

Lists

• Review your request
• Submit approval
• Wait for confirmation

or

1. Sign in
2. Select your project
3. Submit the request

Links

[Employee Portal](https://contoso.com)

Depending on the channel, links may appear as clickable hyperlinks.

Code Blocks

Useful when returning:

• JSON
• XML
• PowerShell
• SQL
• REST requests

Example

{
   "status":"Complete"
}

Although primarily useful for IT scenarios, formatted code blocks improve readability significantly.

Using Variables in Responses

Most responses contain dynamic information.

Instead of static text:

Hello Customer

Use variables:

Hello {User.Name}

Examples include:

• Customer name
• Order number
• Case ID
• Ticket status
• Product information
• Appointment time

Dynamic responses create personalized conversations.

Example:

Instead of

Your appointment has been confirmed.

Return

Hello John,
Your appointment for Tuesday at 2:00 PM has been confirmed.

Formatting Dynamic Data

When displaying variables, consider formatting.

Examples include:

Dates

Instead of:

2026-07-03T18:30:00Z

Display

July 3, 2026
6:30 PM

Currency

Instead of:

1249.95

Display

$1,249.95

Percentages

Instead of

0.82

Display

82%

Proper formatting improves professionalism and reduces confusion.

Structuring Long Responses

Avoid overwhelming users with lengthy paragraphs.

Instead:

Break responses into logical sections.

Example:

Support Ticket Created

Ticket Number:

87421

Priority:

High

Estimated Response:

2 Hours

Next Steps

• Monitor your email

• Reply if additional information is requested

• Close the ticket after resolution

This structure is much easier to scan.

Using Adaptive Cards

Adaptive Cards provide rich interactive user experiences.

Instead of displaying only text, an Adaptive Card can include:

• Images
• Buttons
• Forms
• Multiple columns
• Input fields
• Choice selections
• Action buttons
• Hyperlinks

Example use cases:

• Expense approval
• Vacation requests
• IT support forms
• Purchase approvals
• Customer surveys
• Product recommendations

Adaptive Cards are especially valuable when users need to make decisions directly inside the conversation.

Benefits of Adaptive Cards

Advantages include:

• Interactive experiences
• Improved usability
• Reduced typing
• Consistent design
• Mobile-friendly layouts
• Better user engagement

Rather than asking:

Would you like Option A or Option B?

An Adaptive Card can present two buttons the user simply clicks.

Adaptive Card Components

Common elements include:

Text Blocks

Display formatted text.

Example:

Vacation Request

Images

Useful for:

• Employee photos
• Product images
• Maps
• Company logos

Fact Sets

Display key-value information.

Example

Employee:

John Smith

Department:

Finance

Status:

Pending

Input Controls

Examples include:

• Text boxes
• Date pickers
• Toggle switches
• Dropdown lists
• Rating controls

Action Buttons

Examples:

Approve

Reject

View Details

Submit

Cancel

Buttons simplify user interaction.

Images in Responses

Images improve engagement when used appropriately.

Common examples include:

• Product photos
• Company logos
• Equipment diagrams
• Employee pictures
• Charts

Avoid using decorative images that do not add business value.

Hyperlinks

Responses often direct users to other systems.

Examples:

• Knowledge articles
• HR portal
• SharePoint
• Microsoft Teams
• ServiceNow
• Dynamics 365
• Internal documentation

Rather than displaying long URLs, use descriptive text.

Good example:

Open the Employee Benefits Portal

Poor example:

https://contoso.sharepoint.com/sites/hr/benefits/documents...

Tables

Some channels support table formatting.

Tables work well for:

• Pricing
• Inventory
• Order summaries
• Project status
• Performance metrics

Example

Tables improve readability compared to long sentences.

Lists

Bulleted lists are excellent for:

• Instructions
• Requirements
• Features
• Benefits
• Action items

Example

Before submitting:

• Verify your information
• Upload required documents
• Review your answers
• Click Submit

Response Tone

Formatting is not only visual—it also influences communication style.

Agents should be:

Professional

Friendly

Clear

Concise

Helpful

Avoid:

• Excessive technical jargon
• Large blocks of text
• Ambiguous wording
• Robotic language
• Unnecessary repetition

AI-Generated Responses vs Authored Responses

Copilot Studio supports both authored and AI-generated responses.

Authored Responses

Created manually by the designer.

Advantages:

• Predictable
• Consistent
• Easier compliance
• Controlled wording

Best for:

• Policies
• Compliance
• Legal information
• HR guidance

AI-Generated Responses

Generated using enterprise knowledge sources and generative AI.

Advantages:

• Dynamic
• Flexible
• Natural conversations
• Less maintenance

Best for:

• FAQs
• Large knowledge bases
• Documentation
• Internal support

Designers should ensure AI-generated responses still follow organizational formatting guidelines.

Channel Considerations

Different deployment channels render responses differently.

Examples include:

• Microsoft Teams
• Web chat
• Mobile applications
• Custom websites
• Power Apps
• Omnichannel Customer Service

Not every channel supports every formatting feature.

Adaptive Cards, images, buttons, and Markdown may behave differently depending on the target platform.

Before deployment, always validate that responses render correctly on every supported channel.

Accessibility Considerations

Well-formatted responses should also be accessible.

Best practices include:

• Use descriptive button labels.
• Avoid relying solely on color to convey meaning.
• Keep language simple and readable.
• Organize information with headings and lists.
• Provide alternative text for images where supported.
• Ensure sufficient spacing between sections.
• Keep interactive cards uncluttered.

Accessibility improves usability for all users and supports inclusive design principles.

Performance Considerations

Overly complex responses can affect user experience.

Recommendations include:

• Avoid unnecessarily large Adaptive Cards.
• Limit excessive images.
• Keep responses concise.
• Return only relevant information.
• Avoid deeply nested card layouts.
• Use buttons instead of requiring users to type common responses.

Simple, focused responses generally provide the best user experience.

Common Design Mistakes

Candidates should recognize poor response design.

Common mistakes include:

• Returning paragraphs instead of structured content.
• Showing raw JSON or API output to users.
• Displaying poorly formatted dates and currencies.
• Using inconsistent terminology.
• Creating overly large Adaptive Cards.
• Mixing multiple unrelated tasks into one response.
• Ignoring channel limitations.
• Forgetting to test rendering across deployment targets.

Best Practices

When configuring agent responses:

• Choose the simplest format that satisfies the business requirement.
• Use Markdown to improve readability.
• Personalize responses with variables.
• Display business data in user-friendly formats.
• Use Adaptive Cards for interactive experiences.
• Maintain consistent formatting across topics.
• Design for accessibility.
• Test responses on every deployment channel.
• Keep messages concise and action-oriented.
• Use buttons and structured layouts to reduce user effort.

AB-620 Exam Tips

For the exam, remember the following:

• Understand the differences between plain text, Markdown, rich text, and Adaptive Cards.
• Know when Adaptive Cards provide value over standard text responses.
• Be familiar with using variables to personalize responses.
• Understand how channel capabilities influence formatting choices.
• Recognize when authored responses are preferable to AI-generated responses.
• Know how formatting improves usability, accessibility, and user satisfaction.
• Expect scenario-based questions requiring you to choose the most appropriate response format for a given business requirement.

This topic is frequently tested through scenarios in which you must balance user experience, maintainability, accessibility, and channel compatibility. A strong understanding of response formatting principles will help you design professional, effective AI agents in Microsoft Copilot Studio.

Practice Exam Questions

Question 1

A company is building a Copilot Studio agent that helps employees submit vacation requests. Users should be able to review the request details and either approve or cancel the submission without typing additional text.

Which response format should you use?

A. Plain text response

B. Adaptive Card with action buttons

C. Markdown with bullet lists

D. AI-generated response

Correct Answer: B

Explanation:

Adaptive Cards support interactive controls such as buttons, input fields, and forms. Since users need to take immediate action by selecting Approve or Cancel, an Adaptive Card provides the best user experience. Plain text and Markdown can display information but cannot provide rich interactive controls.

Question 2

An agent returns the following response:

Order Number: 84562
Status: Shipped
Expected Delivery: July 8

The designer wants the response to be easier to scan while maintaining compatibility across nearly all deployment channels.

Which approach should be used?

A. Convert the response into an Adaptive Card

B. Replace the response with AI-generated text

C. Format the response using Markdown headings and spacing

D. Display the information as raw JSON

Correct Answer: C

Explanation:

Markdown formatting improves readability while remaining compatible with most supported channels. An Adaptive Card could also work, but it introduces unnecessary complexity when only simple formatting is required.

Question 3

A Copilot Studio agent retrieves a customer’s first name from Microsoft Dataverse before responding.

How should the response be personalized?

A. Hard-code the customer’s name into every response.

B. Ask the customer to type their name every time.

C. Insert a variable that contains the customer’s name.

D. Return the customer ID instead.

Correct Answer: C

Explanation:

Variables allow responses to dynamically personalize information using data retrieved during the conversation. This reduces user effort and improves the conversational experience.

Question 4

A developer wants an agent to return troubleshooting instructions that include several PowerShell commands.

Which formatting option provides the clearest presentation?

A. Store the commands in a Fact Set.

B. Display the commands inside an image.

C. Place the commands inside an Adaptive Card button.

D. Format the commands using a code block.

Correct Answer: D

Explanation:

Code blocks preserve formatting and spacing, making PowerShell commands easier to read and copy. Images prevent copying, and buttons are intended for actions rather than displaying scripts.

Question 5

An HR agent returns employee handbook information that rarely changes and must always match company policy exactly.

Which response type is most appropriate?

A. Authored response

B. AI-generated response

C. Adaptive Card

D. Markdown-generated summary

Correct Answer: A

Explanation:

Policy and compliance information should use authored responses because administrators maintain complete control over wording and consistency. AI-generated responses may paraphrase information, which is undesirable for official policy.

Question 6

A product catalog agent must display several products with images, prices, descriptions, and “View Details” buttons.

Which response format is most appropriate?

A. Plain text

B. Markdown bullet list

C. Adaptive Card

D. Code block

Correct Answer: C

Explanation:

Adaptive Cards are designed for structured, interactive presentations that include images, buttons, and organized information, making them ideal for product catalogs.

Question 7

A support agent currently returns the following response:

Ticket created. Number 87321. Priority High. Assigned to Network Team. Estimated completion 2 hours.

What is the best improvement?

A. Replace the response with a hyperlink.

B. Separate the information into headings and labeled sections.

C. Convert the information into XML.

D. Remove the priority information.

Correct Answer: B

Explanation:

Organizing related information into labeled sections makes responses easier to scan and understand. The content remains the same while improving readability.

Question 8

An organization deploys the same agent to Microsoft Teams, a company website, and a mobile application.

Why should response formatting be tested on every deployment channel?

A. Every channel supports identical formatting capabilities.

B. Adaptive Cards only work on websites.

C. AI-generated responses cannot be used on Teams.

D. Different channels may render formatting and interactive components differently.

Correct Answer: D

Explanation:

Channel capabilities vary. Some channels support full Adaptive Cards and Markdown, while others may partially support or render features differently. Testing ensures a consistent user experience.

Question 9

An agent retrieves the following value from a database:

2026-08-14T13:30:00Z

What is the best way to present this information?

A. Display the raw timestamp.

B. Convert it to binary.

C. Format it into a user-friendly date and time.

D. Replace it with the database record ID.

Correct Answer: C

Explanation:

Users should see dates and times in an understandable format rather than technical timestamp values. Proper formatting improves usability and professionalism.

Question 10

A designer wants to improve accessibility for all users interacting with a Copilot Studio agent.

Which design choice best supports this goal?

A. Use descriptive button labels and well-structured responses.

B. Rely only on color to indicate status.

C. Replace text with images whenever possible.

D. Display all information in a single paragraph.

Correct Answer: A

Explanation:

Accessibility best practices include meaningful button labels, organized layouts, headings, and clear language. Relying solely on color or replacing text with images reduces accessibility, while large blocks of text make responses harder to understand.

Exam Readiness Checklist

Before taking the AB-620 exam, ensure you can:

• ✔ Differentiate between plain text, Markdown, rich text, and Adaptive Cards.
• ✔ Identify when to use authored versus AI-generated responses.
• ✔ Configure dynamic responses using variables.
• ✔ Select the most appropriate formatting for business scenarios.
• ✔ Design responses that improve readability and usability.
• ✔ Understand how deployment channels affect response rendering.
• ✔ Apply accessibility best practices to agent responses.
• ✔ Format dates, currencies, percentages, and other dynamic values appropriately.
• ✔ Recognize when interactive controls improve the user experience.
• ✔ Evaluate response formatting decisions based on business requirements, user experience, and maintainability.

These scenario-based questions reflect the style of the AB-620 certification exam, where selecting the most appropriate design choice is often more important than simply knowing a feature exists.

Go to the AB-620 Exam Prep Hub main page