Fin remains the support front door. Dubot gives it managed Data connectors for product reads, then takes over approved writes or “show me” flows and returns the verified result.
Fin can close the conversation while your team is still left with the work. Dubot gives Fin four ways to reach the product outcome.
Return approved product data and customer context to Fin.
Run an approved write under product-owned policy.
Navigate, point, type, pause, and report completion.
Finish a focused workflow, then return control to Fin.
Dubot navigates to the right place, highlights the next step, types or points at the field, pauses for customer input, and reports back when the guide finishes.
Fin invokes approved reads and writes. Dubot applies product policy, verifies the result, and hands back the receipt Fin answers with.
A teammate completes the workflow in the live product. Dubot observes the sequence, inputs, and resulting state, then proposes an action contract for review. Your team approves it before an AI agent can use it.
The product decides which actions are read-only, which require confirmation, and which may run in production. The agent asks. Dubot evaluates the request against the rules before anything changes.
Read the security modelAfter execution, Dubot checks the resulting product state and returns a receipt. Fin can continue the conversation knowing what changed, for whom, and whether the expected outcome was verified.
Fin owns the customer conversation. Dubot supplies the governed reads, writes, guides, and specialist agents that let the conversation reach a product outcome.
Fin capabilities vary by setup. The distinction here is ownership: Fin orchestrates the support conversation; Dubot exposes product-owned capabilities and returns the outcome.
Put Dubot before Fin when a narrow workflow can be resolved directly. Put it under Fin when Fin should keep the customer relationship.
Dubot handles a defined product workflow. If the request expands beyond it, Fin takes over with the context.
Fin stays customer-facing. Dubot reads, acts, guides, or runs a specialist workflow, then sends the verified result back.
“AI answers resolve 60% of our support. We’d definitely want AI to create an invoice on someone’s behalf.”Rebecca Pechette · Sr. Mgr. Digital Programs & Operations
Keep your current support stack. Start with a frequent request that ends in a real product change, then show Dubot how the product completes it.
A teammate completes the task once in the live product. Dubot observes the inputs, sequence, and expected result.
Your team checks the inputs, permissions, confirmation rule, and verification test before publishing the action.
Fin invokes the approved action, continues the conversation, and receives a verified outcome it can explain to the customer.
DEMO-VERIFIED
