Use the API you already have.
Map one workflow to your existing API or MCP tools. The initial service is hands-on integration, with a reusable connection kit planned.
Your app. A new way in.
Connect your app to your customer’s dot.
Your customers talk;
their dots operate your app.
Less translation. More intention.
From “could you…”
to something you can review.
One Venue example. A brief, a bounded action, and a record in the app your customer already uses.
The manual path
The idea is clear.
The work is scattered.
A new venue means moving the same brief through forms, space records, and a final check.
- Open the venue formRe-enter the brief
- Create each spaceRepeat the details
- Save, reopen, inspectCheck what actually stuck
Your customer’s intention
Add Juniper House as a venue, with a garden and a dining room. Keep it private while I check the details.
Illustrative spoken brief
Only the selected context
Fictional venue notes: garden, dining room, private draft.
This walkthrough uses preset text. It does not record audio, call an agent, or save to Venue.
- 1 Understand
- 2 Authorize
- 3 Review
A bounded plan
One venue.
Two spaces. Your review.
The dot would prepare the venue and its spaces, keeping the result in your private workspace.
- Destination
- Venue / private workspace
- Change
- Create one venue + two spaces
- Publication
- Not requested
Start with the plan. You decide what happens next.
Your app keeps the record.Emma carries selected context and coordination.
A new way in.
The same source of truth.
Start with one useful workflow in your existing app. Keep its records, rules, and ownership where they belong.
Your customerIntent + selected context
Emma connectionScope. Approval. Receipt.
Memory and task coordination stay distinct from your business records.
Your existing appRecords + business rulesSource of truth
Proposed architecture, not a live connection.
Make permission part of the flow.
Define what can be read or changed, whose account it belongs to, and where the owner must approve.
Give the task a shared place.
The intended shared task room brings the brief, approvals, and action receipts together, so people can inspect what happened.
Evidence before promises
A real starting point.
A clear line around it.
Capability status as of October 6, 2026. The simulation above shows the intended experience, not a deployed Dot integration.
Browser-assisted work
in a live private app.
Private workspace, property, and experience workflows have been created or edited, saved, reloaded, and checked in a private preview.
Create / edit→Save→Reload→Private preview
A bounded browser-assisted proof. No private client content is shown here.
The reusable connection
is still being built.
- Reusable app MCP exposed to actual Dots
- Complete create, read, update, and delete coverage
- Native wake-ups between Dots
- A hosted cloud vault for private memories
A public pitch page is not proof that these capabilities are connected.
Start with one useful thing
Bring the workflow
your customers repeat.
We’ll start with a hands-on integration conversation: the task, the app, the permission boundary, and what a successful result looks like.
The direction: an open-source connection kit, with optional managed hosting. Neither is offered as a ready-to-use product today.
A good first conversation
- What should a customer be able to ask?
- Which existing API or MCP tools can do it?
- What needs approval, and what proves it worked?
Use your existing conversation with the Emma team to discuss a pilot. No booking or signup service is connected to this page.