Rules-based workflow
Best when the input and next step are predictable: when status A occurs, create task B and notify its owner.
Custom AI agents
A custom business agent can interpret changing information, use permitted tools, prepare a result, and send uncertain or sensitive cases to a person. The job, inputs, permissions, and review rules are agreed before it acts.
This is a demonstration of how an agent could be scoped, not a delivered customer result.
The useful output is concise and traceable to its source. A reviewer can correct it before anything reaches the customer.
Review task: account question
Request: customer asks whether an order can arrive Friday.
Record found: order 1048. The available record has no confirmed delivery date.
Prepared reply: “I found your order, but the current record does not confirm a Friday delivery. I have asked the order owner to review it before we give you a date.”
Required action: order owner reviews the record and approves or replaces the reply.
Best when the input and next step are predictable: when status A occurs, create task B and notify its owner.
Useful when the input varies and the system must interpret it within a narrow job, permission set, and review policy.
Useful for a person-led conversation. It answers a prompt but does not automatically need access to business tools or actions.
Read the custom business agent guide for the fuller decision comparison and preparation questions.
No. A general chatbot waits for a question. A business agent has a defined job, approved information, tools, permissions, and rules for when a person must take over.
No. An agent should receive only the information required for its job. Broad access is a risk, not a feature.
Only if the business approves that mode for a specific, well-tested workflow. Many agents begin by preparing messages for review.
Low-confidence or unusual cases should pause and escalate. Guessing is not an acceptable default.
Often yes. LI B2B first looks at the tools already in use and connects only what the workflow needs.
Before commissioning the work, review how scope, testing, handover, and support are agreed.
Start with one defined job, approved information, and a clear rule for when a person takes over.