Skip to content

Commit b569310

Browse files
Update facilities-fm-create-ticket.md
1 parent 4b92422 commit b569310

1 file changed

Lines changed: 18 additions & 16 deletions

File tree

copilot/employee-self-service/facilities-fm-create-ticket.md

Lines changed: 18 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -30,15 +30,15 @@ At Microsoft, we extended Employee Self-Service Copilot agent to bring in Real E
3030
- Create a Facilities Ticket (Facilities), for example, "I want to report a water leak"
3131
- Register a Vehicle (Parking), for example, "I want to register my vehicle Tesla Model 3"
3232
- View food stations or counters by cuisine (Dining), for example, "Where can I find Chinese food?"
33-
- Invite a Guest (Lobby), for example "I want to invite my spouse to Building 32"
33+
- Invite a Guest (Lobby), for example, "I want to invite my spouse to Building 32"
3434

3535
The following section shows how a maker in Copilot Studio can extend Employee Self-Service to support these scenarios. Before diving into the maker experience, it's important to understand what real estate and facilities are and how they support employees.
3636

3737
## Real Estate & Facilities
3838

3939
Real Estate and Facilities (RE&F) play a pivotal role in shaping the overall employee experience within an organization. By integrating RE&F services into Employee Self-Service platforms, companies can streamline access to essential workplace amenities and administrative tasks, making daily operations more efficient and user-friendly for employees.
4040

41-
For instance, features like - vehicle registration, facilities tickets for maintenance requests, access to café menus, and streamlined guest invitation processes empower employees to manage their work environment proactively. These capabilities reduce administrative overhead, minimize wait times, and improve satisfaction by giving employees greater control and visibility over their workplace needs.
41+
For instance, features like vehicle registration, facilities tickets for maintenance requests, access to café menus, and streamlined guest invitation processes empower employees to manage their work environment proactively. These capabilities reduce administrative overhead, minimize wait times, and improve satisfaction by giving employees greater control and visibility over their workplace needs.
4242

4343
Moreover, such integrated experiences foster a sense of belonging and engagement, as employees feel supported by systems that anticipate and address their requirements. These integrated experiences not only enhance productivity, but also contribute to a positive organizational culture where employees can focus more on their core responsibilities rather than logistical hassles.
4444

@@ -65,7 +65,7 @@ Extending Employee Self-Service for RE&F experiences requires an understanding o
6565
In Copilot Studio, a topic is defined as a workflow of a conversation. Microsoft 365 Copilot topics are used to:
6666

6767
- Define trigger prompts that determine when the *Invite a guest* topic should be activated based on user’s natural language input.
68-
- Asking questions and capturing necessary input from the employee, such as problem descriptions, building information, and location details, etc.
68+
- Asking questions and capturing necessary input from the employee, such as problem descriptions, building information, and location details, and so on.
6969
- Triggering a Power Automate flow by utilizing the Dynamics connector, which is responsible for creating a facilities ticket using the Case (Incident) entity.
7070
- Interpreting the response from the Facilities Management ticket creation process and returning the relevant outcome to the employee in a conversational format.
7171

@@ -77,19 +77,21 @@ Adaptive cards are platform-agnostic UI snippets authored in JSON. They help cre
7777

7878
In Copilot Studio, Prompts are essential for constructing custom AI actions using natural language. These AI prompts are used to extract and identify information form the user provided prompts.
7979

80-
Some examples where AI prompt can be used is – For creating a facility ticket, identify information like category for the reported problem, and location of the issue being reported from the employee’s natural language input.
80+
Some examples where AI prompt can be used are:
8181

82-
For detailed documentation on AI Prompts, refer to the official Microsoft documentation [Prompt columns in Microsoft Dataverse](/power-apps/maker/data-platform/prompt-column)
82+
- Creating a facility ticket
83+
- Identifying information like a category for a reported problem
84+
- Location of the issue being reported from the employee’s natural language input
85+
86+
For detailed documentation on AI Prompts, refer to the official Microsoft documentation [Prompt columns in Microsoft Dataverse](/power-apps/maker/data-platform/prompt-column).
8387

8488
### Power Automate Flow
8589

86-
Power Automate is a cloud-based automation platform that enables users to create workflowscalled flows to automate repetitive tasks across applications and services without writing code. It's part of the Microsoft Power Platform and integrates seamlessly with Microsoft 365 apps and hundreds of third-party services.
90+
Power Automate is a cloud-based automation platform that enables users to create workflows, called flows, to automate repetitive tasks across applications and services without writing code. It's part of the Microsoft Power Platform and integrates seamlessly with Microsoft 365 apps and hundreds of third-party services.
8791

88-
For supported connectors, see:
89-
[Connector reference overview](/connectors/connector-reference/)
92+
For supported connectors, see: [Connector reference overview](/connectors/connector-reference/)
9093

91-
HTTP request action reference:
92-
[HTTP with Microsoft Entra ID (preauthorized) - Connectors](/connectors/webcontents/)
94+
HTTP request action reference: [HTTP with Microsoft Entra ID (preauthorized) - Connectors](/connectors/webcontents/)
9395

9496
## Example: Create a facilities ticket
9597

@@ -115,7 +117,7 @@ To route facilities issues to the right technician, extract the problem category
115117

116118
- Create a new prompt in Copilot Studio. Go to [Power Apps](https://make.powerapps.com/) and select AI Hub > Prompts > Build your own prompt.
117119
- Copy the prompt instructions from the Copilot Studio Samples repository: [Extract Problem category](https://github.com/microsoft/CopilotStudioSamples/blob/main/EmployeeSelfServiceAgent/Facilities/EmployeeCreateFacilitiesManagementTicket/Extract%20Problem%20category.md?plain=1), and paste them into the Instructions section. Adjust the instructions as needed for your scenario.
118-
- Add two input text parameters by selecting Add content: Problem Description (next to the Problem Description input) and Categories (next to the Reference Categories Data input), as shown in the screenshot.
120+
- Add two input text parameters by selecting **Add content: Problem Description** (next to the Problem Description input) and **Categories** (next to the Reference Categories Data input), as shown in the screenshot.
119121

120122
:::image type="content" source="media/facilities-fm-create-facilities-ticket-extract-category-prompt.png" alt-text="Power Apps prompt builder showing instructions to extract a problem category, with “Problem Description” and “Categories” input fields.":::
121123

@@ -124,7 +126,7 @@ To route facilities issues to the right technician, extract the problem category
124126
:::image type="content" source="media/facilities-fm-create-facilities-ticket-extract-category-prompt-edit.png" alt-text="Expanded “Categories” field showing an editable, comma-separated list (for example, plumbing, electrical, cleaning).":::
125127

126128
- Test the prompt.
127-
- Enter a sample Problem Description and choose a model. For consistent behavior, use the same model as your Employee Self-Service agent. Select Test to confirm the category returned for your scenarios.
129+
- Enter a sample **Problem Description** and choose a model. For consistent behavior, use the same model as your Employee Self-Service agent. Select **Test** to confirm the category returned for your scenarios.
128130
- Optionally, try other available models and compare results before you standardize on one.
129131

130132
:::image type="content" source="media/facilities-fm-create-facilities-ticket-extract-category-problem-desc.png" alt-text="Prompt test panel with a sample description entered and the model returning the matched category in the output pane.":::
@@ -137,7 +139,7 @@ To dispatch facility services to the right place, extract location details from
137139

138140
- Create a new prompt in Copilot Studio. Go to [Power Apps](https://make.powerapps.com/) and select AI Hub > Prompts > Build your own prompt.
139141
- Copy the prompt instructions from the sample: [Extract Location Information](https://github.com/microsoft/CopilotStudioSamples/blob/main/EmployeeSelfServiceAgent/Facilities/EmployeeCreateFacilitiesManagementTicket/Extract%20Location%20Information.md?plain=1), and paste them into the Instructions section. Adjust the instructions as needed for your scenario.
140-
- Add the input text parameter Facilities Description next to the Facilities Description input by selecting Add content, as shown in the screenshot.
142+
- Add the input text parameter Facilities Description next to the Facilities Description input by selecting **Add content**, as shown in the screenshot.
141143

142144
:::image type="content" source="media/facilities-fm-create-facilities-ticket-extract-location-prompt.png" alt-text="Power Apps prompt builder showing instructions to extract location details, with a “Facilities Description” input field.":::
143145
- Test the prompt and save it as **Extract Location Information**.
@@ -166,11 +168,11 @@ Steps:
166168
- In Copilot Studio, select **Add a topic > From blank**.
167169
- Once inside the topic, select **Open code editor**.
168170
- Copy the topic YAML from the sample repository and paste it into the code editor: [topic.yaml](https://github.com/microsoft/CopilotStudioSamples/blob/main/EmployeeSelfServiceAgent/Facilities/EmployeeCreateFacilitiesManagementTicket/topic.yaml), and close code editor.
169-
- In the topic workflow editor, locate the Prompt Location reference. Select the double-arrow button to open Add a tool, and then choose the Extract Location Information prompt you created earlier.
171+
- In the topic workflow editor, locate the **Prompt Location** reference. Select the double-arrow button to open **Add a tool**, and then choose the **Extract Location Information prompt** you created earlier.
170172

171173
:::image type="content" source="media/facilities-fm-create-facilities-ticket-topic-add-location-prompt.png" alt-text="Copilot Studio topic editor with the “Add a tool” panel open and “Extract Location Information” selected.":::
172174
- Repeat the previous step for the problem category prompt and the action (the flow).
173-
- Resolve any validation errors, and then select Save.
175+
- Resolve any validation errors, and then select **Save**.
174176

175177
- Validate.
176178
- Open the visual representation of the topic and verify the end-to-end flow.
@@ -194,7 +196,7 @@ Steps:
194196

195197
:::image type="content" source="media/facilities-fm-create-facilities-ticket-topic-adaptive-card.png" alt-text="Adaptive Card ticket form in chat with fields for category, location, and description, plus Submit and Cancel buttons.":::
196198

197-
- Confirm the topic branches based on the selected action. For Submit, verify it calls the flow you created earlier (under Create a Power Automate flow) and handles the returned response.
199+
- Confirm the topic branches based on the selected action. For **Submit**, verify it calls the flow you created earlier (under Create a Power Automate flow) and handles the returned response.
198200

199201
## FAQs
200202

0 commit comments

Comments
 (0)