one suite · one login
The work runs itself.
A product for every part of the business that repeats. One login. Subscribe to what you need.
Phone
Incoming · Sarah Kim
Logged to the lead automatically.
Draft ready
Thanks for the note. I have attached the revised schedule and flagged the two dates that moved.
Window closes in 2h
One login, one customer record
Voicemail detected, next call dialing
The 24-hour window, enforced in the composer
Answers that cite the record they came from
The suite
Every product. One dashboard.
Subscribe to one. Subscribe to all of them. They share a login, a customer record, and the same agents.
Talk
Every channel your customers reach you on, in one inbox.
Run
The records and the people the business runs on.
Think
What the numbers mean, and agents that act on them.
Agents
An agent in every product.
Agents are not a module you buy separately. They are already inside the products you use, doing the volume your team should not be doing.
It drafts.
Email replies written from a one-line instruction, in your own thread.
It routes.
Every lead assigned the moment it lands, by country, city, source or campaign.
It answers.
Ask about your own records. The answer arrives with its sources attached.
Product by product
What each one actually does.
No roadmap language. These are the capabilities running today, with anything still in beta labelled as such.
Vague Phone
Calls that log themselves.
A softphone in the browser with a Power Dialer that detects voicemails, drops your message, and files every call on the lead.
- Dial any lead from the row you are reading
- Power Dialer detects the machine and dials the next human
- One-tap Voicemail Drop, so you never say it twice
- Every call and recording filed on the lead
Vague Email
Replies that draft themselves.
A shared inbox threaded on the customer. Type one line of instruction, get a full draft in the thread. Nothing sends without a person.
- One line of instruction in, a full draft out
- Broadcasts count mailable and suppressed before you send
- Bounces and opt-outs suppressed with the reason recorded
- Templates render with the lead's real details
Vague WhatsApp
The 24-hour window, handled.
Meta gives you 24 hours to reply free-form. The composer counts down every conversation and swaps in an approved template the second the window shuts.
- A live countdown on every conversation
- Templates built, previewed and submitted to Meta in one screen
- Quality scores and rejection reasons in plain sight
- Campaign funnels down to the single message
Vague Data
A pipeline that fills itself.
A lead lands, a rule fires, a person owns it. Duplicates are caught at the door, and every deal carries its own documents and payments.
- Round-robin routing by country, city, source or campaign
- Duplicates caught across typed, imported and form intake
- Deals carry stage, documents and payment schedule
- Overdue payments flag themselves
Vague HR
The paperwork that files itself.
Clock-ins with a location pin, leave requests that arrive carrying the balance, onboarding with a visible finish line.
- Clock in from a phone, confirmed on the map
- A month of attendance in one matrix
- Leave requests arrive with the balance attached
- Payroll day counts exported in one click
Vague Intelligence
Numbers that explain themselves.
Dashboards over every product, and a faster route: ask the question in plain language and get the answer with the records it came from.
- Charts by response, country, city and campaign
- Ask in plain language, get answers with citations
- A revenue leaderboard with rank movement
- Filtered reports, exported for whoever asked
Vague Studio
Agents that run your work.
An agent on your own records. It watches, proposes the next action, and waits for a person to say yes.
- Every action proposed, never fired blind
- Answers cite the record they came from
- MCP keys let your other agents in, on your permissions
- Built on the eve runtime
The platform
The suite is the product.
Every product writes to one customer record, and each is switched on per person. How that works has a page of its own.
Agents used to arrive as a project with an end date. Now they arrive as products you subscribe to.
The volume moves to the agent. The judgment stays with your people. That is the whole trade.
Questions
The things teams ask first.
Yes. Every product stands alone. Most teams start with WhatsApp or Data, and add the next one once the first is paying for itself.
They share a customer record. A call in Phone, a thread in Email and a conversation in WhatsApp all land on the same lead, so nobody rebuilds context by hand.
It writes the first draft of the reply, assigns the lead the minute it lands, watches the 24-hour WhatsApp window, and answers questions about your own records with citations attached. It proposes. Your team approves.
Intelligence and Studio. Dashboards and the agent both work today, but the report builder and the agent builder are not finished, so we label them rather than oversell them.
No. Phone is a softphone that runs in the browser. There is no hardware to buy and nothing to rip out.
Yes. Templates are submitted to Meta from inside the product, and approval status, quality score and rejection reasons all surface where your team works.
Pick the piece of your business you want running itself.
We will show you the product that fits, on your data, in thirty minutes.