Lesson 2 · 15 min
An assistant that only talks helps very little. What changes your day is an assistant that pulls the task out of the meeting, puts it in the right quadrant of the matrix, attaches the document and prepares the action with a button. In this lesson you set up that routine and understand Google's "unverified app" warning.
Start the lesson
Goal: set up the assistant to turn meetings and emails into classified tasks and to act only after your "Confirm".
Tap each step.
Chats with buttons and small pages inside the conversation (like Telegram's mini apps) let you decide with one tap, without leaving the chat.
Four steps.
Choose a messaging app that supports buttons in the conversation. Telegram supports buttons and mini apps; on WhatsApp the features vary by account.
What matters is that it's the channel you already open all day.
Give the assistant the triage prompt below. It reads the input and returns task, quadrant, reason and attachment.
Test it with three real meetings before you trust it.
Partner asked: "review the new partner's contract". → Important, not urgent · reason: affects revenue, no deadline · attachment: contrato.pdf
List the actions the assistant can prepare: buy a recurring item, send an email, schedule a meeting.
Each one ends with Confirm / Cancel. Payment comes from a low-limit card, separate from your main one.
To read Gmail, Drive and your calendar, the assistant uses a Google login (OAuth). If it's only for you or for your company, mark the app as internal or test.
To sell to third parties, see the Google box in the next section before promising a deadline.
The prompt goes in the assistant's instructions. The rule goes with it.
You are my task assistant. When I send a meeting summary, an email or an audio message, do this: 1. List each task that comes out of it, one per line, starting with a verb. 2. For each task, choose ONE quadrant: A = urgent and important · I do it today B = important, not urgent · I schedule it C = urgent, not important · I delegate (agent or person) D = neither · I drop it 3. Write the reason in one line (deadline? does it affect revenue, a client or the law?). 4. Attach the file mentioned, if there is one. 5. If the task involves spending, sending something outside, or changing someone else's calendar, do NOT execute it: prepare it and show me the Confirm button. Output format: [quadrant] task · reason · attachment
ACTIONS THAT NEED CONFIRMATION: - purchase (limit per purchase: R$ <value>, separate card) - email or message to anyone outside the company - meeting invite to another person - any deletion FREE ACTIONS: - create a task for me - find a document and attach it - notify me when a price drops
[B] Review the new partner's contract · affects revenue, no deadline · contrato-parceiro.pdf [C] Order 2 ink cartridges · routine, short deadline · (Confirm button) [A] Reply to the client about the delivery · client waiting today · email from 09:12
Updated with Google's documentation (10/21/2026).
Adding a logo or display name to the consent screen of a published external app requires brand verification, which usually takes from minutes to a few days.
Requesting access to sensitive or restricted data (full Gmail is restricted) requires a separate, longer scope verification.
There's a tip going around that removing the logo makes the warning go away. Removing the logo only avoids brand verification.
If the app reads Gmail, the warning stays until scope verification is done, and the project is capped at 100 users in total.
Personal or internal company use is exempt: mark the app as internal.
To sell, request only the minimum access (read a label, send email) and set aside time for verification before promising a date to the client.
Use real meetings and emails from this week.
Set up the triage prompt in your assistant and send three real inputs: a meeting summary, an email and an audio message.
Done when: you have three answers in the format [quadrant] task · reason · attachment and you agree with at least two.
Copy the button rule and adjust it to your situation, with the per-purchase limit.
Done when: the rule lists at least 4 actions that need Confirm and the limit in reais.
If your assistant uses a Google login, open the project's consent screen and check the user type.
Done when: you can say whether the app is internal, test or external, and which accesses it requests.
The lesson's mechanism explained in about two and a half minutes.
4 questions.
Question 1 of 4
In the meeting, your partner says: "review the new partner's contract when you can." Which quadrant?
Question 2 of 4
Which action can the assistant take without asking for Confirm?
Question 3 of 4
Your app reads your clients' Gmail and shows "unverified app." Does removing the logo from the consent screen fix it?
Question 4 of 4
Why prefer a chat with buttons?
Pick an option. The explanation shows up after you try.