***

title: Scoping with Mockups
excerpt: ''
deprecated: false
hidden: false
metadata:
title: ''
description: ''
robots: index
next:
description: ''
---------------

# How to Purple Chat Scope

[Purple Chat](https://developer.moveworks.com/creator-studio/developer-tools/purple-chat) Scoping allows you to align business & technology teams on the requirements of a use case without getting too far ahead of yourself. Without a clear picture of what you're building, you won't be able to make it to production.

<Callout intent="note">
  Get [Purple Chat Certified in Moveworks Academy](https://academy.moveworks.com/catalog/courses/3867845)
</Callout>

### 1. Understand the request with [Purple Chat](https://developer.moveworks.com/creator-studio/developer-tools/purple-chat)

<div>
  <iframe src="https://www.loom.com/embed/d5e4aa66756d44e3ac96e5fb3e9e8cb2" frameBorder="0" allowFullScreen />
</div>

### 2. Add API Annotations

<div>
  <iframe src="https://www.loom.com/embed/d5e4aa66756d44e3ac96e5fb3e9e8cb2" frameBorder="0" allowFullScreen />
</div>

# Example

Our [best-in-class example](https://developer.moveworks.com/creator-studio/developer-tools/purple-chat?conversation=%7B%22startTimestamp%22%3A%2211%3A43+AM%22%2C%22messages%22%3A%5B%7B%22role%22%3A%22user%22%2C%22parts%22%3A%5B%7B%22richText%22%3A%22Can+you+explain+what+%3Cb%3EPLS%3C%2Fb%3E+means.%22%7D%5D%7D%2C%7B%22role%22%3A%22assistant%22%2C%22parts%22%3A%5B%7B%22reasoningSteps%22%3A%5B%7B%22status%22%3A%22success%22%2C%22richText%22%3A%22%3Cp%3ELooking+up+%3Cstrong%3E%5C%22PLS%5C%22%3C%2Fstrong%3E+in+our+%3Cstrong%3EInternal+Dictionary%3C%2Fstrong%3E%3C%2Fp%3E%22%7D%5D%7D%2C%7B%22apiBlock%22%3A%7B%22title%22%3A%22GET+%2Fsheets%3Fcol1%3D%5C%22PLS%5C%22%22%2C%22connectorName%22%3A%22google-drive%22%2C%22code%22%3A%22%7B%5Cn%5Ct%5C%22Acronym%5C%22%3A+%5C%22PLS%5C%22%2C+%5Cn%5Ct%5C%22Word%5C%22%3A+%5C%22Product+Led+Sales%5C%22%2C+%5Cn%5Ct%5C%22Meaning%5C%22%3A+%5C%22A+sales+approach+where+the+product+itself+drives+customer+acquisition+and+expansion.%5C%22%5Cn%7D%22%2C%22caption%22%3A%22%5BMock+API%5D+filters+the+data+in+the+sheet+where+%5C%22Acronym%5C%22+column+matches+%5C%22id%5C%22+of+the+request+%22%7D%7D%2C%7B%22richText%22%3A%22%3Cp%3E%3Cstrong%3EPLS+%3C%2Fstrong%3Estands+for+%5C%22%3Cstrong%3EProduct-Led+Sales%5C%22%3C%2Fstrong%3E%3C%2Fp%3E%5Cn%3Cp%3E%3Cbr%3E%3C%2Fp%3E%5Cn%3Cp%3EIt%27s+a+sales+approach+where+the+product+itself+drives+customer+acquisition+and+expansion.%3C%2Fp%3E%22%7D%2C%7B%22citations%22%3A%5B%7B%22connectorName%22%3A%22google-drive%22%2C%22citationTitle%22%3A%22PLS%22%7D%5D%7D%5D%7D%5D%7D) is shown below:

![](https://files.readme.io/a65c610eff35b3c3b5234de11366c8f7207acd597179c660411b4af7162d4cf7-CleanShot_2025-03-08_at_11.31.302x.png)

A few things to note:

1. Every bot message has an annotation indicating any data-sources that are supposed to drive the bot message.
2. Every system interaction (annotation) specifies the INBOUND and OUTBOUND data contract.
3. Every system interaction (annotation) has a procedural pseudocode defining what happens in that interaction (systems, aggregations, etc.)