How the engines work together
Every engine does one job. All of them stand on the same foundation, so they share data instead of syncing it, and you switch on only the ones a workspace needs.
14-day free trial, no credit card. Or book 30 minutes with us.
- Dashboard
- Driver app
- Tracking page
- Chat widget
- Phone line
- API and MCP
- Contacts
- One calendar
- Roles and permissions
- Governance
- Connectors and Drive
- Audit log
Agents
AI agents with tools from every engine you run, on chat, on your website and on the phone, with a person approving the actions that matter.
- Tools that read and write your real records
- Realtime voice agents on your phone numbers
- Embeddable chat widget for your website
- Approval before sending, browsing or running a flow
- Answers calls and drafts inbox replies.
- Looks up routes, stops and vehicles.
- Works deals, contacts and outreach.
- Starts a flow, with approval.
- Browses, searches and researches.
- Creates and assigns jobs.
Three layers
- 01
Surfaces
Where people meet the platform: the dashboard, the driver app, the customer tracking page, the chat widget, your phone line, the API and MCP.
- Dashboard
- Driver app
- Tracking page
- Chat widget
- Phone line
- API and MCP
- 02
Engines
The work itself: planning routes, answering calls, running flows, finding leads, dispatching jobs, keeping stock. Switched on per workspace.
- 03
Foundation
What every engine shares: contacts, one calendar, roles and permissions, governance, connectors and Drive, the audit log.
Follow one customer from lead to report
No exports, no sync jobs, no duplicate contacts. The same record moves on.
A lead is found
The lead finder returns a company and a contact person. Import and clean checks the email and removes the duplicate you already had. The person becomes a contact, once.
- Marketing & Sales
- Contacts
Outreach becomes a deal
A sequence connects on LinkedIn, waits for the invite to be accepted, and sends a message written for this person. They reply; you win the deal.
- Marketing & Sales
- Agents
The deal becomes an invoice
The won deal becomes an invoice for the same contact, paid through the provider you connected.
- Invoicing
Their order becomes a stop
An order arrives by webhook. A flow finds the contact, adds a stop to tomorrow's route and has an agent write the confirmation.
- Flows
- Fleet
- Agents
They call, the agent answers
On delivery day the customer calls. The phone agent reads the live route and tells them how many stops are ahead. The driver closes the stop with a photo and a signature.
- Comms
- Agents
- Fleet
It all shows up in one report
Trips per day, calls and invoices come from the records the engines already wrote. Nothing to collect.
- Reporting
What every engine shares
Contacts
One record per person and company. The stop, the lead, the caller and the invoice address are the same contact.
One calendar
Routes, jobs, agent runs, flow triggers, reports and meetings on one calendar, from one scheduler.
Roles and permissions
Each engine declares its own permissions, and one role model grants them across the workspace.
Governance
Approvals, redaction of personal data and an AI inventory for the EU AI Act, applied to every agent.
Connectors and Drive
Credentials stored once in an encrypted vault and used by every engine; files in one Drive.
Audit log
Who did what, in which engine, including what an agent did on someone's behalf.
Engines are switched on per workspace
- Each workspace picks its engines in settings
- Permissions come with the engine and are granted by role
- Unreleased engines are never sold as available
Every engine, in one place
What each one does, and what it exchanges with the others.
Fleet
Plan a day of stops, split it across drivers, send it to the driver app and follow every vehicle live, up to proof of delivery.
- Route solver with time windows, capacity and a multi-driver split
- Driver app for Android and iOS that keeps working offline
- Proof of delivery: photo, signature, QR or barcode scan
- Customer tracking page that hides the driver until they are close
Exchanges data with: Field service, Agents, Comms, Flows, Reporting, Spatial and visionOpen pageField service
Work orders with a customer, a place, an appointment window and a technician, dispatched through the same planner the fleet uses.
- Jobs on a board and a schedule
- Appointment windows the planner respects
- Dispatch as a real route to the technician
- Proof of completion from the field
Exchanges data with: Fleet, Flows, Agents, ReportingOpen pageInventory
Products and stock, picking in waves, expiry-first handling, purchase and sales orders with available-to-promise.
- Stock levels per location
- Picking waves and putaway
- Expiry-first (FEFO) handling
- Purchase and sales orders
Exchanges data with: ReportingOpen pageSpatial and vision
Sites, buildings and floor plans, geofences and yard plans, and cameras with live detection and zones.
- Sites and floor plans
- Geofences and yard plans
- Camera detection and zones
Exchanges data with: Fleet, RoboticsOpen pageAgents
AI agents with tools from every engine you run, on chat, on your website and on the phone, with a person approving the actions that matter.
- Tools that read and write your real records
- Realtime voice agents on your phone numbers
- Embeddable chat widget for your website
- Approval before sending, browsing or running a flow
Exchanges data with: Comms, Fleet, Marketing & Sales, Flows, Web research, Field serviceOpen pageFlows
Automations on a canvas, started by a webhook, a schedule or a device, with steps that belong to the engines themselves.
- Canvas builder with templates
- Webhook, schedule and device triggers
- Engine steps: contacts, routes, jobs, messages
- Connectors to the tools you already use
Exchanges data with: Agents, Marketing & Sales, Fleet, Field service, CommsOpen pageComms
One inbox for email, chat, WhatsApp and text, plus phone numbers, call routing and IVR, where agents and people work side by side.
- Shared inbox across channels
- Phone numbers, call center and IVR
- Voice agents on live calls
- Meeting recorder for Meet, Zoom and Teams
Exchanges data with: Agents, Fleet, FlowsOpen pageWeb research
Agents that browse, search and research the web, and crawl sites into knowledge, on infrastructure we run ourselves.
- Browsing with clean page extraction
- Web search and deep research
- Crawl a site into agent knowledge
Exchanges data with: AgentsOpen pageMarketing & Sales
Deals and pipelines, lead finding, and outreach on LinkedIn and email that paces itself like a person and writes to each person on their own.
- Pipelines with drag and drop deals
- Lead finder across several data providers
- Sequences with daily limits and connection-aware steps
- Import and clean old company lists
Exchanges data with: Invoicing, Agents, FlowsOpen pageInvoicing
Quotes and invoices created from deals, payments collected through the provider you connect, and reminders on overdue invoices.
- Quotes and invoices
- Payments through your own provider keys
- Reminders on overdue invoices
Exchanges data with: Marketing & Sales, ReportingReporting
Reports and dashboards over what the platform already records, delivered on a schedule as PDF or spreadsheet.
- Visual query builder with charts
- Templates such as trips per day
- Scheduled delivery by email or chat
Exchanges data with: Fleet, Field service, Inventory, Invoicing, Comms, FlowsRobotics
Robots as part of the fleet: status, positions and vision-language perception today; mapping, navigation and manipulation are in development.
- Robot status and positions
- Vision-language perception
- Navigation and mapping in development
Exchanges data with: Spatial and visionOpen pageService desk
Coming soonInternal tasks, bugs and incidents on a list, a board and queues, linked to the customer conversations they came from.
Everything you click, you can call
The same engines are reachable from your own code. API keys are scoped per capability and can be limited to named agents, flows or tools.
- Public REST APIAgents, flows, executions, knowledge search and models under /v1.
- Webhooks inSigned webhook endpoints that start a flow.
- MCP serverExpose the tools a key allows to any MCP client.
- Flows as glueCall any HTTP API from a flow step when there is no connector.
# Ask an agent from your own systemcurl -X POST "$API_URL/v1/agents/$AGENT_ID/chat" \ -H "X-API-Key: $API_KEY" \ -H "Content-Type: application/json" \ -d '{ "message": "Which stops are still open on route B?" }'Questions about the platform
A product area with its own screens, data, tools for agents, flow steps and permissions, such as Fleet or Marketing & Sales. Engines are switched on per workspace and all stand on the same foundation.
Contacts and companies, the calendar and scheduler, roles and permissions, governance (approvals, redaction, AI inventory), connectors with their stored credentials, Drive and the audit log.
No. A route stop, a lead and a caller are the same contact record, and engines call each other directly: a work order is dispatched by the route solver, a won deal becomes an invoice, an agent reads routes as a tool.
Yes. Many workspaces start with one engine and add others later; what is already in the foundation, like contacts, is there when you do.
Yes. There is a public REST API with scoped keys, signed webhooks that start flows, and an MCP server that exposes the tools a key allows.
Start with the engine you need today
Switch on one engine, bring your contacts, and add the next when the work calls for it.