THE DUBOT PLATFORM

Give your AI the power to act.

Dubot answers, guides, completes, or hands off inside your product. And you get the confidence it worked.

Talk to usSee the full workflow ↓
Dubot
Composing request
Composing requestIn your product

Your support AI can answer well and still leave the customer’s job open.

One request, from customer intent to verified result.

Watch one HoneyBook workflow move from request to verified result.

Answer. Show me. Do it for me. Hand off.

Like asking someone who can do something about it.

Answer
AnswerAnswer it
How do I add a discount to an invoice?
Ask Dubot anything…
Show me
Show meShow me
Where do I change late payment emails?
Ask Dubot anything…
Do it for me
Do it for meDo it for me
Apply a 10% discount to Priya Shah’s invoice.
Ask Dubot anything…
Hand off
Hand offGet me help
Acme says they paid, but I never got the money.
Ask Dubot anything…
HUMAN IN THE LOOP
Real changes ask permission.When Dubot is unsure, a personhuman takes over.Your team decides what requires confirmation.
CONTEXT BEFORE ACTION

Dubot knows what the customer means now.

Dubot checks who is asking, what they can do, where they are, and which actions apply.

“Make the next payment due August 30.”
Before it choosesDubot checks who is asking, what they can do, where they are, and which actions apply.
01WhoSarah Chen · Owner
02Role allowsCreate · Edit · Send
03WhereInvoice #1042
04Approved actionsupdate_payment_date

“Actually, make the next payment due August 30” needs no invoice number or link. Dubot knows which invoice is open.

Current page · Invoice #1042 · Due August 15
ANATOMY OF A RESOLUTION

Every request leaves a record.

Each Run records what Dubot understood, used, attempted, and verified.

  1. 01What the customer asked
  2. 02How Dubot interpreted it
  3. 03The context it used
  4. 04The kind of help it chose
  5. 05What was previewed and confirmed
  6. 06What executed
  7. 07What was verified afterward
  8. 08The outcome, or the handoff and why
  1. 01Understand the request
  2. 02Ground it in product context
  3. 03Preview and execute the approved action
  4. 04Verify the result or explain the handoff
Run #1042 · create_invoice · Acme Corp · Sarah Chen · July 23, 2026
01
Intent14:23:01
“Create a $2,500 draft invoice for Acme Corp due August 15”
02
Action selected14:23:01
create_invoice
client Acme Corpamount $2,500.00due_date 2026-08-15type draft
03
Confirmation14:23:01 → 14:23:04
Preview card shown · customer accepted
Confirmed · 3s
04
Execution14:23:05
POST /invoices · 201 Created · Invoice #1042 returned
05
Verification14:23:05
Fetched invoice #1042 from product
Status: DraftSends now: NoAmount: $2,500.00
Resolved14:23:05 · 4s total
Outcome
Invoice created and verified
Invoice #1042 · Acme Corp · $2,500 · Due Aug 15, 2026 · Draft · Not sent
FULL CONTROL

Dubot can act, but your team sets the limits.

You’ve heard “agentic” before. The difference is receipts: approved actions, confirmation on real changes, and a record of every run.

01

Approved actions only

Dubot can only use capabilities your team has reviewed and approved. Nothing is added without your team’s review.

02

Confirmation policy per action

You set which changes require explicit customer confirmation and what the preview must show.

03

Role permissions

For configured actions, availability can be scoped by role before Dubot offers the action.

04

Verified results

Where an action defines a verification step, Dubot checks the resulting product state rather than treating an API response as success.

05

The safe no

When Dubot cannot proceed safely, it says why and hands off with context.

Dubot acts inside the customer’s authenticated session. Product credentials stay in your app.

Read more about security →
Control
What you control
create_invoice
Action policy
● Live
Requires confirmationCustomer must approve before execution
Verify resultFetch product state after execution
Allowed rolesWho may trigger this action
Owner
What the customer sees
Create this draft invoice?
Review before confirming
Draft invoice
ClientAcme Corp
Amount$2,500.00
Due dateAugust 15, 2026
This creates a draft. Nothing will be sent.

Two surfaces. One governed core.

The Resource Center and Browserbot use the same approved actions, confirmation policies, and run history.

Conversation

Answers, guides, completes, and hands off beside the customer’s work.

answercompletehand off
Dubot core
  • Context
  • Policy
  • Actions
  • Verification
Browserbot

Guides the customer through the live product when the step should belong to them.

guide
THE RESOURCE CENTER

Beside the customer’s work.

Answer, show, do, or hand off without leaving the product.

honeybook.com / invoices / 1042 LIVE
ACME CORP

Draft invoice #1042

Brand strategy project$2,500Due August 15 · Draft · Not sent
+See the Resource Center→
↗
BROWSERBOT

Through the live product.

Point to the real control, wait for the customer, and verify what changed.

honeybook.com / invoices / 1042 LIVE
How do I change the payment date?
Current page understood
INVOICE SETTINGS

Payment schedule

Next payment dateAugust 15
BROWSERBOTHere is the setting.

Choose Edit to change the next payment date.

Waiting on the real control
Automatic remindersOn
+See Browserbot→
Your team sets the rulesThe same approved actions in both surfaces

Real changes still wait for permission.

How Dubot fits your existing support stack.

Dubot resolves work inside your product, then returns the conversation and product context when a person needs to take over.

Dubot is not another help desk. It owns the path from customer intent to in-product outcome.

Working with Intercom and Fin today: Fin can use your approved Dubot actions. When Dubot hands off, the conversation goes to Fin with the context and a note attached. Fin triages; your team steps in when needed. Read the Intercom + Fin guide →

Open by design. Approved actions can also be exposed through MCP and used by supported agents under the same action policies.

GETTING LIVE

Start with the support journey that creates the most work.

Connect the actions it needs, test it in the real product, and review the results before expanding.

01

Engineering connects Dubot

Engineering installs the SDK and exposes the capabilities required for the first journey.

02

CX connects your knowledge

Your CX team connects the approved help-center and public sources for that journey.

03

Map the first journey together

We map the relevant product surfaces, roles, and actions with your CX and product teams.

04

Launch a bounded slice

Test it in the real product, launch to a defined audience, then review the outcomes together.

FAQ

Start with one painfulseamless customer journey.

Pick the job that fills your queue. We’ll map it with you and prove the outcome.

Dubot gets the job done.
Talk to us