PTENES
Skip to content
MODULE 2.2

🏥 A request isn't a problem

People who ask for an agent usually come with the solution already figured out. Learn to find the pain point behind the request, put a price on it, and design the first small project.

6
Topics
~30
Minutes
Practical
Level
Case study
Type
0 of 60%
1

Separate what’s requested from what’s wanted

Almost no one comes in stating the problem. They come in stating the solution: "I want more customers," "I want to respond faster," "I want to post every day." That's the request.

Behind the request is a desire, almost always to earn more or lose less. “More customers” means “more revenue.” And sometimes the cheapest way to earn more isn’t to bring in new people—it’s to stop losing the ones who are already here.

🆕 New here? What is a “pain point”?

Pain, in this course, is the point in the business where you're currently losing customers, time, or money — and you can measure how much. "I want to grow" isn't a pain point. "I lose nine appointments a month" is.

what you can see what you can’t see REQUEST: "I want more customers" DESIRE: more revenue PAIN: I lose 9 appointments a month (patients who schedule appointments and don't show up) ask "what for?" until you find a number

How to read the diagram: the request is the small tip that shows above the surface. The large, illuminated part is underwater: the desire and, deeper down, the pain you can measure. The blue arrow shows the path—keep asking “what for?” until you reach a number.

🗣️
Request

the solution that arrives ready

💭
Desire

earn more, lose less

🩹
Pain

measurable loss

❓
“For what?”

the question that goes down

2

Study the clinic case

Renata, 44, runs an aesthetics clinic. She wanted an agent to attract more patients through Instagram. Before setting anything up, she opened last month’s schedule.

Noticed something else: patients would book and didn’t appear. Every no-show meant a paid time slot—room, supplies, professional waiting—with no revenue at all.

🗣️ What she asked for

  • ✗“An agent that brings in more patients.”
  • ✗More people joining a schedule that was already losing appointments.
  • ✗Ad spend to fill an appointment schedule full of holes.

💰 What cost money

  • ✓Patients who booked and didn’t show up.
  • ✓No one confirmed the appointment the day before.
  • ✓An empty time slot that didn’t turn into another appointment.
new patients (Instagram) AGENDA 38 appointments/month 9 missed appointments slip through the hole more water in the bucket = more missed appointments, same gap patch the hole first = reminder + confirmation

How to read the diagram: the blue arrows at the top show what the request wanted to increase. The red arrow shows what was already leaking. As long as the hole remains, the more that comes in, the more leaks out—that's why the first agent targets the hole, not the faucet.

📖
Look at the calendar

before turning anything on

🪣
Leaky bucket

input doesn't plug a hole

🚪
Shortfall

paid hours, no revenue

🔧
Patch the hole first

the tap later

3

Calculate how much the pain costs

Without a price, the pain is just an opinion. With a price, it becomes a decision. Here’s a back-of-the-envelope calculation: absences × average amount × weeks.

Renata counted last month’s missed appointments in her paper planner. There were nine, out of thirty-eight scheduled appointments. Each appointment is worth an average of R$ 120.

StepRenata's clinicWhat this shows
1 · How often it happens38 appointments booked this monththe process size
2 · How many go wrong9 missed appointments (≈ 2 per week)almost 1 in 4
3 · How much can be recovered today0 — the time slot stays emptyzero means everything is lost
4 · Monthly cost9 × R$ 120 = R$ 1.080proof that it’s worth making a change
5 · Annual costR$ 1.080 × 12 = R$ 12.960the number that changes the conversation

What to look for in the table: Line 3 is the most important. If you already recover part of the loss today (by fitting in another patient, for example), subtract that. What remains is what the agent can help save.

💡 Practical tip

You don’t need to get the exact cent right. If you don’t know the average amount, use the most common service. If you don’t know how many were missed this month, count the ones from last week and multiply by 4—and write “estimate” beside it. You’ll measure the exact number in Track 5.

🔢
How many times

process size

❌
How many fail

the loss itself

♻️
Recovered

subtract what you already get back

💵
Cost of the pain point

per month and per year

4

Design the first small project

With the pain point and price in hand, the clinic's first agent became clear: appointment reminder and confirmation, with an option to reschedule. No Instagram, no billing.

Small on purpose. It reads the calendar, sends a message, and records the response. Anything that actually changes the calendar—rescheduling, canceling—goes through Renata.

1

2 days before · reminder

“Hello! Your appointment at the clinic is Thursday at 3 p.m. Reply 1 to confirm or 2 to reschedule.”

2

The patient responds

Answer 1: the agent marks “confirmed” in the spreadsheet. Answer 2: it notifies Renata, who reschedules.

3

1 day before · no response

The agent sends a second reminder, just once. If no one responds after that, it puts the person’s name on a list for reception to call.

4

Available time slot · opening

Whoever rescheduled frees up a time slot. Renata decides who from the waitlist can take it—the agent only shows who is on it.

📅 read the calendar 💬 reminder "1 confirms · 2 reschedules" ✓ confirmed → agent logs it in the spreadsheet ↺ reschedule → Renata approves … no response → reception calls the agent only decides on its own on the blue path

How to read the diagram: The lit-up box is the only automatic send. Of the three outcomes, only the top one (animated blue arrow) ends without anyone involved; the other two go back to a person. It’s a small project because the possible mistake is small: at worst, one extra reminder.

🐣
Small

on purpose

📨
Reminder

2 days and 1 day before

🙋‍♀️
Renata approves

reschedule and fit in

🪶
Cheap mistake

one more reminder

5

Apply this to other professions

The clinic is just an example. The pattern repeats in almost every small business: the request points to outside (more customers, more posts), and the pain point is inside (something that already comes in and gets lost).

Marcos, a 52-year-old accountant, asked for “an agent to answer clients faster.” The real pain point was documents arriving late on WhatsApp and turning into tax forms with late fees. His assistant, Júlia, spent her mornings chasing paperwork.

BusinessThe requestThe pain pointFirst small project
💇 Salon"more followers"last-minute cancellation leaves a seat emptyconfirmation the day before + waitlist
🛍️ Store"sell through WhatsApp"budget requested and not answered within 24hdraft response for the owner to approve
📑 Accounting"reply faster"a late document turns into a finelist of what each customer still needs, every Monday
🏥 Clinic"more patients"patient books and doesn't show upreminder + confirmation

What to look for in the table: across all the lines, the first project is small, repetitive, and ends with a person approving it. And none of them handle money.

🗣️ Sounds like a request

  • ✗“I want an agent that sells.”
  • ✗“I want to be on every social network.”
  • ✗“I want to automate customer service.”

🩹 Sounds painful

  • ✓“I lose 3 quotes a week because of delays.”
  • ✓“I pay 2 fines a month for late documents.”
  • ✓“I have 9 no-shows out of 38 appointments.”
↗️
Request

points outward

↘️
Pain

is inside the house

🔢
With a number

otherwise, it's still a request

🙋
Ends with a person

in the first project

6

Write the pain point

Everything in this track fits into one sentence. It’s the first field in the agent profile you’ve been building since module 1.2—and the starting point for track 3.

If the sentence doesn’t add up, something is missing: the number, the cause, or what the agent will do. Go back to the topic that was left blank.

🎯 Goal: leave with a revised statement of your business pain point

Paste into the AI chat you already use (ChatGPT, Claude, Gemini). Replace what's inside < > with what you found in modules 2.1 and 2.2.

Quero escrever a "frase da dor" do meu negócio, neste molde:

"Hoje perdemos <quanto: reais, horas ou clientes por semana/mês>
por <o que acontece: ex.: pacientes que marcam e faltam>
porque <a causa: ex.: ninguém confirma o horário na véspera>;
o primeiro agente vai <uma ação pequena: ex.: mandar lembrete e pedir confirmação>."

Meu negócio: <uma linha>.
Meus números: <o que contei ou estimei>.

Revise a minha frase com estas regras:
1. O "quanto" precisa ser um número. Se eu não dei, pergunte.
2. O "por" precisa ser um fato, não um desejo ("vender mais" não vale).
3. O "porque" precisa ser algo que um agente consegue mudar.
4. O "vai" precisa ser UMA ação pequena, sem mexer em dinheiro e com uma pessoa aprovando o que for mudar agenda, cliente ou envio em massa.
Devolva a frase corrigida e, em uma linha, o que você mudou e por quê.
Não invente números.
How to verify: read the sentence to someone who doesn’t know your business. They should understand, without an explanation, what is lost, how much, why, and what the agent will do. If they ask, "but how much?", the number is missing.

💡 Renata’s sentence

“Today we lose R$ 1.080 per month per patients who book and don't show up because no one confirms the appointment time the day before; the first agent will send a reminder two days ahead and ask for confirmation — and reschedule only with my approval."

Quick test (optional): which of these is a pain statement that closes?

💵
How much

one number

📍
For

one fact

🔍
Because

one cause you can change

🤖
Go

one small action

🎓 Module summary

✓
A request isn't a problem — ask “what for?” until you find a number.
✓
Patch the hole before turning on the tap — more customers won’t fix a leaky schedule.
✓
The pain point has a price — absences × average value × weeks.
✓
First small project — makes cheap mistakes and ends with a person approving.
✓
The pain point sentence — how much, for, because, goes: the first field in the form.

Next track:

T3 — Control the system: once you’ve chosen the pain point, you still need to decide what the agent can access.