Start with a focused SupportBot pilot.

AIWF is beginning with scoped private-beta pilots rather than publishing one-size-fits-all pricing. Start with one support workflow, approved knowledge, and a human escalation path.

How the pilot works

The exact commercial scope is defined with the business. The product model stays consistent: grounded knowledge, visible evidence, and people in the loop where judgment is required.

01

Choose one workflow

Start with a support area that has clear questions, knowledge, and owners.

02

Approve the knowledge scope

Identify the sources SupportBot is allowed to use for that workflow.

03

Define escalation

Decide what should stop for a person and where those requests should go.

04

Run a focused pilot

Evaluate answer quality, evidence, escalations, and fit before expanding the scope.

Who the first pilots are designed for.

The initial profile is a small or medium business with documentation, a customer-support team, frequent questions, and repetitive workflows.

Initial focus: logistics and documentation-heavy operations · roughly 10–500 employees.

Knowledge exists

Policies, procedures, PDFs, structured records, or approved answers already exist.

Questions repeat

The support team regularly spends time finding and explaining the same operational information.

Escalation matters

Some requests need judgment, approval, or a specialist rather than an automatic answer.

Define the first workflow with us.

Tell us what your customers ask, where the approved answers live, and what should still go to a person. We’ll use that scope to evaluate a SupportBot pilot.