Zdieľať cez

Getting started

  • Článok

As you get started using Copilot Studio, it's important to understand how project goals, use cases, and pricing affect the success of your Copilot Studio project.

Set goals

We recommend customers separate the project goals into three distinct areas: core delivery, business metrics, and governance. If copilots are brand-new to your organization, then the examples in this article are a good starting point. Once you go live, you quickly learn what's important, how your customers behave, and where you would like to improve.

Project goals

Here's an example of the goals a customer defines at project inception.

  1. Delivery goals - Minimum Viable Project (MVP)

    1. Go-live with a copilot on a target date fewer than three months.

    2. The copilot can answer your target use cases, using a script of test phrases.

  2. Business goals after you go live

    1. Resolved session percentage: the project team aims to increase this number over time. This figure is often referred to as the deflection amount.

    2. Escalated session percentage: the project team aims to reduce this number over time.

    3. Abandoned session percentage.

    4. Deflection or Resolution: the business value per session.

    5. Monthly Active Users (MAU).

  3. Establish copilot governance and management model

    1. The Application Lifecycle process and automation setup.

    2. The copilot author onboarding process.

    3. The reporting and review cadence.

Build use cases

Creating inspiring use cases is a key part of beginning your copilot building journey.

The program includes:

  1. Interested employees participate in a Copilot Studio in a Day training, where they learn the fundamentals of conversational copilot building.

  2. Once attendees have experience building copilots, split the training group into small teams of two to three people.

  3. Allow teams to identify moments in the use case they could solve using a copilot.

  4. Each team should establish milestones over a four-week period that includes activities for each team member. This practice is similar to a project plan.

  5. After two weeks, each team of the training group presents their copilot, demonstrates their progress, and identifies any challenges or gaps.

  6. After four weeks, each team of the training group reveals their final product to the rest of the group and leaders from the respective business areas.

  7. When possible, provide some level of reward to the participants of this initiative. Incentives can vary from recognition to monetary rewards.

  8. Include a path to production period to ensure all copilots are finalized into production.

  9. Share success with the rest of the organization, and inspire others to do more.

  10. Rinse and repeat. Now you have a program that can run on a regular cycle to promote copilot development within your organization.

Tip

Hackathons encourage organizations to learn and apply what they’ve learnt in real-world use cases to develop copilots.

Pricing

You can subscribe to plans for Copilot Studio and for Microsoft 365 Copilot. Which plan you should choose depends on you or your organization's needs. To find more information or to purchase a plan, go to Pricing information for Copilot Studio or contact your Microsoft account team.

Building a team