The approval moment.
The single most important screen in an assistant is the one that asks you for a yes. Here is how we design it.
An assistant that can act on your behalf will, sooner or later, be about to do something that matters: pay a bill, book a table, send a message to someone who is not you. Everything we believe about trust comes down to what happens in that moment.
What needs a yes
We keep the rule simple. Anything that spends money, makes a booking or commitment, or messages another person waits for your approval. Reading your own documents, setting reminders, researching options and drafting replies do not, because nothing leaves your hands.
What the approval shows
A good approval is not "Shall I go ahead?". It is the whole decision, small enough to read in a few seconds:
- What exactly. Amma's BP tablets, same brand, thirty days. Not "your order".
- How much, and from where. ₹412, paid by UPI from the account you usually use.
- When and to whom. Delivery by 6 pm to Malleshwaram. A message to Divya and Nithin, with the text you would be sending.
- What happens next. What Gogo will do after the yes, and what it will send back as proof.
If you would need to ask a follow-up question before approving, the approval is not finished.
One tap, and an easy no
Approving should be one tap. Saying no should be just as easy, and "change something" should not mean starting again. Reply "make it 8:30 instead" and Gogo adjusts the proposal and asks again.
Your limits, not ours
Over time, some people will want fewer questions. A standing yes for reordering the same medicine under a set amount, or for booking the usual cab, can make sense, and it is something we are working towards. When it comes, those rules will be yours to set, written down where you can see them, and switched off in one tap. Gogo will never widen them on its own.
The approval moment is where an assistant earns the right to do more. We would rather ask one question too many than make one decision you did not want.