> For the complete documentation index, see [llms.txt](https://docs.hablla.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hablla.com/hablla-docs-en/mci/customer-conversational-cycle-mapping.md).

# Customer Conversational Cycle Mapping

## 🌀 Customer Conversational Cycle Mapping Template

> This document helps you map the real and cyclical journey of your leads, considering multiple entry points, pauses, re-engagements, and conversion.\
> Fill in each section based on the data and behaviors of your current leads.

***

### 🎯 Mapping Objective

Describe in 1 or 2 sentences the objective of this cycle (e.g.: Inbound leads journey via WhatsApp focusing on consultative diagnosis):

***

### 🔁 Conversational Cycle Points

#### 1. **Entry**

**Where does the lead start the contact?**

* [ ] Ad (Meta, Google, LinkedIn)
* [ ] Landing page form
* [ ] WhatsApp button
* [ ] Referral or partner
* [ ] Other: `__________`

> Note:
>
> ####

#### 2. **Automated Screening (AI)**

**Does AI perform any screening?**

* [ ] Yes
* [ ] No

> If yes, what questions does it ask?

#### 3. **Human Support**

**When does a human take over? What are the handoff criteria?**

#### 4. **Active Follow-up**

**How do you maintain contact if the lead doesn't respond right away?**

* Channels used:
  * [ ] WhatsApp
  * [ ] Email
  * [ ] Phone
  * [ ] Social networks
* Type of message:
  * [ ] Content (case study, article)
  * [ ] Direct proposal
  * [ ] Meeting/CTA

> Example sequence:

#### 5. **Spontaneous Return**

**What does the lead usually do when they come back?**

* [ ] Clicks an old link
* [ ] Replies to a previous email
* [ ] Returns via WhatsApp
* [ ] Other: `__________`

> How do you identify this return?

#### 6. **AI or Human Re-engagement**

**What strategies do you use to re-engage the lead?**

#### 7. **Conversion**

**What marks the moment of closing or advancement?**

* [ ] Proposal accepted
* [ ] Contract signed
* [ ] Onboarding started
* [ ] Other: `__________`

> Average time to this stage:

### 🚧 Common Journey Barriers

List the friction points that usually interrupt the cycle:

* [ ] No response after proposal
* [ ] Difficulty qualifying via AI
* [ ] No-show for meeting
* [ ] Lead without budget at the moment
* [ ] Other: `__________`

> Improvement ideas for each barrier:

### 📊 Final Cycle Diagnosis

**Use emojis, notes, or markings to indicate maturity by point:**

| Stage         | 🟢 Strong | 🟡 Medium | 🔴 Weak | Notes |
| ------------- | :-------: | :-------: | :-----: | ----- |
| Entry         |     ☐     |     ☐     |    ☐    |       |
| AI Screening  |     ☐     |     ☐     |    ☐    |       |
| Human Support |     ☐     |     ☐     |    ☐    |       |
| Follow-up     |     ☐     |     ☐     |    ☐    |       |
| Re-engagement |     ☐     |     ☐     |    ☐    |       |
| Conversion    |     ☐     |     ☐     |    ☐    |       |

### 🧭 Priority Actions

List 2 to 3 actions that will be applied based on this mapping:

***

> Last updated: `{{ fill in the date }}`\
> Created by: `{{ your name or responsible team }}`

***


---

# 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.hablla.com/hablla-docs-en/mci/customer-conversational-cycle-mapping.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.