English rendering of a commercial proposal delivered to the client in Spanish, April 2026. Product copy is shown in its original language, with translation.
Commercial proposal · 2026

Intelligent automation
for Emanuel Cocina

Your restaurant already takes orders on WhatsApp. We make that process run on its own, without errors and without losing a single sale.

Client
Emanuel Cocina
Engagement
Pilot
Start
April 2026
View proposal

The problem

What happens in your restaurant today

Every day Emanuel handles dozens of orders by hand over WhatsApp. That means time lost, orders taken wrong, customers who get tired of waiting, and sales that disappear without anyone seeing them.

01
Orders taken by hand
Every order needs direct attention. A misread message, a wrong quantity or an incomplete address creates problems in the kitchen and with the customer.
02
A daily menu with no system
The menu gets posted manually every morning. If a dish sells out, the customer finds out after ordering it. That creates friction and avoidable delays.
03
No customer data
There is no record of who orders, how often, which dishes they prefer or how much they spend. Without data there is no loyalty program and no strategy.
04
Inconsistent charges
Delivery cost, packaging and the final total get calculated in the moment. One slip produces a wrong charge and a complaint that damages the experience.

The solution

A system that works while you cook

We connect the official WhatsApp API directly and build a conversational flow designed so your customers feel like they are talking to a person, not a robot.

"
"We automate your WhatsApp with the same technology large companies use, and we design the flows so your customers feel like they are talking to a person, not a robot."
Real-time menu from Treinta. Dishes update automatically every 3 minutes. If something sells out it disappears from the menu instantly. No manual messages, no surprises.
Full ordering flow inside WhatsApp. The customer picks dishes, chooses delivery, pickup or reservation, and confirms with the exact total before closing. All in under 2 minutes.
Automatic, correct charges. Delivery: +$3.000 shipping +$2.500 packaging. Pickup: +$2.500 packaging. Reservation: no extra charges. The system calculates and shows the total before confirming.
Daily sides captured over WhatsApp. Every morning the bot asks Emanuel for the sides, the juice and the dessert. That information appears automatically in the customer greeting.
Clean human handoff. If the customer needs to talk to someone, the bot transfers without friction. Emanuel gets an alert on his personal number and replies from WhatsApp Business Manager.
Treinta form integration. When a customer arrives from Treinta with their details pre-filled, the bot detects it and jumps straight to confirmation. The order takes 30 seconds.

How it looks in WhatsApp

This is the flow a customer of Emanuel Cocina goes through today, rebuilt component by component: native WhatsApp list, quoted reply, free-text quantity and embedded form. The bot speaks Spanish because its users do.

1
Welcome with a menu link. The bot greets and shares the Treinta catalog with photos and prices. Ordering happens inside the conversation, not on another page.
2
Selection from a native list. Active dishes come from Treinta. Sold-out items never render. The customer's answer stays quoted above the original message.
3
Quantity and an open cart. The bot asks how many by the dish's exact name and lets the customer add more before closing. The cart does not force one decision.
4
Form and response summary. A single form captures modality, details and payment method. The customer reviews what they submitted before the order reaches the kitchen.
🍽
Emanuel Cocina
online
Ver menú del día

Four strings and why they read that way

Original on the left, translation on the right. In a conversational product the copy is the interface, so most of the design decisions live here rather than in a layout.

Welcome · ES
¡Hola! Bienvenido a Emanuel Cocina. En el link puedes ver el menú de hoy con fotos y precios, cuando estés listo hacemos tu pedido directamente por aquí.
EN
Hi! Welcome to Emanuel Cocina. In the link you can see today's menu with photos and prices. When you're ready we take your order right here.
Why. The link is where you browse, the chat is where you buy. Saying that in the first message stops customers from trying to order on the catalog page and coming back confused. It also sets the expectation that nobody is going to make them leave WhatsApp.
Quantity prompt · ES
¡Buena elección! ¿Cuántos Churrasco de Pollo Chipotle quieres?
EN
Good choice! How many Churrasco de Pollo Chipotle do you want?
Why. The dish name is interpolated instead of using "how many units." On WhatsApp the customer scrolls away, gets distracted and comes back, so the message has to carry its own context. Repeating the name is also the cheapest confirmation that the system read the right item.
Cart state · ES
¡Listo! ya tenemos tu pedido. ¿Agregamos algo más?
EN
Done! We have your order. Shall we add anything else?
Why. "Agregamos" is first person plural, so the restaurant is doing this with you rather than processing you. The question is open on purpose: a closing prompt here would cut order size, and this is the only moment where adding is one tap away.
Field label · ES
Dirección u hora
EN
Address or time
Why. One field serves three modalities. Delivery needs an address, pickup and reservation need a time. Splitting it into three conditional fields would have been cleaner in a spec and worse in practice, because WhatsApp Flows re-render on every change and the customer sees the form flicker.

Why TRIUM

What separates us from any competitor

We are not a platform that inserts itself in the middle, and we are not an agency that wires up a bot without thinking about the experience. These are the two product decisions that define how we deliver value.

01
Direct WhatsApp API, no middleman
We connect the official WhatsApp API directly for your business. The number is yours. If you decide to leave, you take it with you. No extra licenses, no platform in between, no additional points of failure.
02
Conversational flows designed by a UX designer
We have a UX designer on the founding team. Every flow is designed around how the end customer experiences it, not only around whether it technically works. A badly designed flow loses sales. A well designed one converts them.

Investment

What the pilot includes

Monthly pilot · Emanuel Cocina
$70.000
COP / month · introductory pilot rate
Full WhatsApp Business API setup Included
Conversational flow with 2 entry points (direct + Treinta) Included
Menu integration and scraping from Treinta Included
WhatsApp Flow order form (3 modalities) Included
Daily opening flow with sides New
Order dashboard and customer history New
Support and adjustments during the pilot period Included

Plan of work

4 weeks to launch

Everything is defined. The critical path is Meta's approval of the production number. With that active, launch can happen in under a week.

1
Week 1
Onboarding and setup
Business number activation in Meta, WhatsApp API configuration, message template approval and collection of restaurant assets.
2
Week 2
Integration and flow
Connecting the Treinta scraping to the real number, enabling data_exchange mode in the Flow, and testing the full conversational flow across both entry points.
3
Week 3
Testing and adjustments
3 end-to-end test orders, validation of the daily opening flow, tone and message adjustments with Emanuel, and training on WhatsApp Business Manager.
4
Week 4
Launch
Production activation, communication to frequent customers, first-day monitoring and real-time adjustments. The system runs on its own from the first order.