> For the complete documentation index, see [llms.txt](https://docs.talentmap.com/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.talentmap.com/knowledge-base/managers-and-leaders/take-action/action-planning-in-compass/action-plan-template-library/action-planning-library-preview/customer-focus.md).

# Customer Focus

Preview the action plans available for Customer Focus survey questions. Each question offers a behavior plan and a structure plan. Full plans open inside Compass Action Planning.

{% hint style="info" %}
**Module required.** Your organization needs the Action Planning module enabled in Compass to open these plans.
{% endhint %}

***

### This organization shows employees the difference we make for our external customers

| Plan                                                       | Approach  | Focus                                                                                               |
| ---------------------------------------------------------- | --------- | --------------------------------------------------------------------------------------------------- |
| **Connecting Your Team's Work to Real Customer Impact**    | Behavior  | Makes the link between daily work and customer outcomes visible and routine.                        |
| **Building a Customer Feedback Loop Into Team Operations** | Structure | Creates a repeatable system that routes customer impact data back to the people who need to see it. |

***

### External customers value what we provide

| Plan                                                              | Approach  | Focus                                                                                                         |
| ----------------------------------------------------------------- | --------- | ------------------------------------------------------------------------------------------------------------- |
| **Helping Your Team See the Value Customers Actually Experience** | Behavior  | Translates abstract customer satisfaction into concrete evidence the team can internalize.                    |
| **Embedding Customer Value Evidence Into Team Workflows**         | Structure | Builds customer value signals into existing team processes so visibility doesn't depend on individual effort. |

***

### Customer comments and recommendations often lead to improvements

| Plan                                                     | Approach  | Focus                                                                                                        |
| -------------------------------------------------------- | --------- | ------------------------------------------------------------------------------------------------------------ |
| **Turning Customer Feedback Into Visible Team Action**   | Behavior  | Creates a habit of acting on customer input and showing the team the connection between feedback and change. |
| **Building a Customer-to-Action Pipeline for Your Team** | Structure | Creates a structured process for routing customer feedback into team improvement cycles.                     |

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.talentmap.com/knowledge-base/managers-and-leaders/take-action/action-planning-in-compass/action-plan-template-library/action-planning-library-preview/customer-focus.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.