Question 1

Is Glove an agent builder?

Accepted Answer

No. In Glove you design business processes, not agents. The agent is assembled at runtime from your process definition and current business state. Same engine, infinite configurations.

Question 2

What is an ephemeral agent?

Accepted Answer

A conventional AI agent is a standing configuration: a prompt, a set of tools, a memory of its own conversation. It exists before the work arrives and it persists after. An ephemeral agent does not exist until a turn needs to be handled. Glove assembles it at that moment from the process you designed and the state the business holds right now — the rules that apply, the data already known, the step the process sits in — and it is gone once the turn is done. The state stays; the agent does not. That is why nothing drifts as a conversation grows, why two people never get two different behaviours from the same process, and why the same engine can serve a chat, a call and a form: they are all reading the same state.

Question 3

How is this different from n8n or Make?

Accepted Answer

n8n and Make connect tools. Glove maintains shared state across all actors — AI, humans, and software. The difference is that every actor always works from the same business context, not from a message passed down a pipeline.

Question 4

We already have a CRM with AI. Why Glove?

Accepted Answer

CRMs store state but don't orchestrate it. Your CRM knows what happened — but it can't coordinate what happens next across AI, humans, and other tools in real time. That's the gap Glove fills.

Question 5

How is Glove different from omnichannel platforms like Respond.io or Intercom?

Accepted Answer

Those platforms manage your inbox. Glove manages your process. The difference: in Respond.io, a human reads the conversation and decides what to do. In Glove, the state engine already knows where the process is, what the next action is, and whether AI or a human should handle it — and guides whoever steps in. Glove also handles voice with its own pipeline, not just text and chat. And every channel shares the same state — so a conversation started on WhatsApp continues on voice without losing context.

Question 6

Deterministic sounds rigid. Can Glove handle complex, unpredictable conversations?

Accepted Answer

Deterministic means every decision follows a rule you defined — not that the rules are simple. Glove evaluates intent on every turn. If intent shifts mid-conversation, the active flow pauses and the new intent triggers its own process. When that resolves, the original flow resumes where it left off. Rules respond to real variables: deal value, outcomes, customer history, conversation context. The same flow behaves differently depending on what's true right now.

Question 7

What about token costs at scale?

Accepted Answer

Token consumption per turn is O(1) — bounded by state complexity, not conversation length. At turn 10,000 the cost is the same as at turn 1.

Question 8

How does Glove's pricing work?

Accepted Answer

Glove is priced by execution — you pay for the processes you run, not per message or per token. Because cost doesn't grow with the length of a conversation, the price of a flow is tied to the process you designed rather than to how much your customers talk. Pricing is shared on a call, tailored to your processes and volume.

Question 9

Is voice priced the same way?

Accepted Answer

No. Voice is a separate, metered module billed by talk-time, the way voice infrastructure is priced across the category — because minutes of live conversation are inherently variable and can't be fixed in advance. Glove fixes the price of what's deterministic (the process) and meters what's physical (the minutes).

Question 10

What about third-party costs?

Accepted Answer

Fees tied to your own channels — such as WhatsApp Business conversation fees billed by Meta — are billed by those providers at their rates. You bring the stack; its providers bill their part.

Question 11

Is it compliant with EU AI Act?

Accepted Answer

Glove is auditable by architecture. Every state transition is logged. Every human intervention is recorded. Every decision is traceable. Not because we patched it in, but because that is how the engine works.

Question 12

How long does setup take?

Accepted Answer

No-code setup — your operations team deploys the first process without an engineering sprint, and keeps editing it afterwards.

Question 13

What channels does Glove support?

Accepted Answer

Text (WhatsApp, LinkedIn, webchat), email, and voice. Same state engine underneath all of them. SDK for vision and physical events coming soon.

Question 14

What is Dualdrive?

Accepted Answer

Dualdrive is the layer where humans and AI share the same context. When a human enters a Glove process, the system guides them in real time with the next best action, scored against what has worked before — and executes the configured actions for them. The customer never notices the handoff.

Question 15

What is Tandem?

Accepted Answer

Tandem is the single workspace over every process, channel and actor. It shows what is running, the state each conversation sits in, and where a human is needed — plus the audit trail behind all of it.

Question 16

Do you offer a partner program?

Accepted Answer

Yes. If you're a consultancy or integrator, we have a commission model that makes Glove your most profitable product line — 20–30% recurring on client MRR while the client is active.

Questions worth
a straight answer.

It's not a smarter inbox. It's the coordination layer underneath.

Still deciding? See it on your process.

Questions wortha straight answer.

It's not a smarter inbox. It's the coordination layer underneath.

Still deciding? See it on your process.

Questions worth
a straight answer.