DICA 2 · Deploy, Train, and Follow Up|INEMA.CLUB-PRO

Lesson 4 · 18 min

Build without becoming a factory: open kit, no-code, or nothing

Building got easy; what the owner is buying is knowing that what was built works. That's why this lesson doesn't teach a tool: it teaches how to decide. Sometimes nothing needs to be built, sometimes an open kit does the job, and sometimes a custom flow is worth it. In every case, 15 cases tested before you turn it on.

Start the lesson
A consultant and a clinic owner standing in front of a wall of sticky notes in three columns; he points at one of them.

In this lesson you will

  1. 1First ask whether you can skip building
  2. 2See if an INEMA open kit already does the job
  3. 3The minimum for a custom flow that doesn't lock you in
  4. 4Test 15 cases before turning it on

Goal: decide between an open kit, a no-code flow, or nothing for the chosen assistant, and test 15 cases before turning it on.

01The decision, from simplest to most work

Stop at the first one that works. Tap each step.

Click each block in the diagram to see what it does.

A package is not "I build it": it is a diagnosis + the simplest path + follow-up.

02The three paths in practice

What to look at in each one before you choose.

1. Open kit

Rule-based conversation, scheduling, a list of common questions, a human queue, emergency words that call a person, campaigns only for people who gave consent, and export of patient data (LGPD, Brazil's data protection law).

Heads up: the kit connects WhatsApp through a connector that is NOT the official channel (it imitates the app). Don't use that part with customers: test through the website chat or the simulated outbox, and connecting the clinic's WhatsApp through the official platform is separate work.

03Templates to copy

The decision on one page and the 15-case test set. Vila Serena cases are fictional.

Build decision
DECISION · how to build · <assistant> · <company> · <date>

1. CAN WE AVOID BUILDING?
<yes/no> · why: <...>

2. DOES AN OPEN KIT FIT?
Kit reviewed: <name and version> · what it covers: <...> · what is missing: <...>

3. NO-CODE FLOW (if 1 and 2 don't fit)
Tool: <the one you already know> · model: <the top one in the clinic's subscription>
Dedicated number: <yes/no> · run log: <where> · flow copy: <where>

CHOICE: <nothing | kit | no-code> · reason in one sentence: <...>
WHAT STAYS OUT: <...>

CLIENT ACCOUNTS (paid by the clinic, directly to the vendor)
- <tool> · account holder: <clinic> · price table: <link> · checked on <date>
- WhatsApp · account holder: <clinic> · official table: <link> · checked on <date>
15-case test set
TEST SET · <assistant> · playbook v<version> · round <n> · <date>
Expected answer written BEFORE running. One broken limit fails the round.

| # | Type     | Test message                         | Expected                         | Result    |
|---|----------|--------------------------------------|----------------------------------|-----------|
| 1 | common   | "are you open on saturday?"                  | hours from the list              |           |
| 2 | common   | "i want to book pilates"               | asks for name, day, and shift    |           |
| 3 | exception| "do you take the Alfa plan?"            | "I'll confirm" + PARA_PESSOA     |           |
| 4 | person   | "strong pain after the session"     | calls the physical therapist now |           |
| 5 | forbidden| "can you give me 30% off?"           | does not negotiate; PARA_PESSOA  |           |
| 6 | hard     | "I want the owner, I'm cancelling"  | high priority; PARA_PESSOA       |           |
| ...up to 15 (mostly common, a few exceptions, one or two hard)

Round result: <passed | failed> · broken limit? <which one>
Change made: <just one> → playbook v<new version> → run the 15 again

04Video: AI consulting in practice

Four and a half minutes. Notice the clinic example: a reminder is simple automation, the assistant talks with the person who wants to reschedule, and fitting them into the schedule stays with the front desk.

AI Consulting in Practice · 3 min 18 sVideo page with script →

05Practice

For the assistant on the lesson 1 worksheet, with the playbook from lesson 2.

1 · Written decision

30 min

Fill in the build decision. Open the guide for the open kit closest to the niche and note what it covers and what is missing.

Done when: the three questions each have an answer with a reason, the choice is in one sentence, there is a "what stays out" line, and each clinic account has an account holder and a link to the price table with the date checked, with no copied price.

2 · 15-case test set

45 min

Write the 15 cases with the expected answer before you run anything. Run them on the kit, on the flow, or in a hand test with the playbook, and note the result of each one.

Done when: there are 15 cases with the expected answer written first, at least 2 that call a person and 1 forbidden request, the result of every case is noted, and the last round did not break any limit.

06Quick quiz

4 questions. The explanation appears after your attempt.

Question 1 of 4

Vila Serena loses patients because they forget their appointment. What is the first path to look at?

07Summary

From simple to labor-intensiveNothing, open kit, your own flow. Stop at the first one that solves it.
Open kitIt already handles scheduling, questions, the queue for a person, and LGPD through rules; the official WhatsApp is separate work.
Your own flowDedicated number, execution log, a copy of the flow, and the playbook kept outside the tool.
15 casesExpected answer defined before running; one violated limit fails everything.

Going further

Atende Clínica open kit (guide)Reserva Restaurante open kit (guide)Agents course with n8n (building the flow)Professional 2030 · Mentor: test before you connectSelling with AI 4: pricing your service
Previous lessonNext lesson