Can I enable tools per assistant?

Yes. Tools are designed to be scoped to specific assistants so you expose only the actions relevant to that visitor journey. A support assistant and a product discovery assistant do not need the same tool set. The operational question is whether tools makes the workflow clearer once real conversations, real ownership, and real edge cases show up. That is the bar teams should use before they expand the rollout across more assistants, more channels, or more teams.

Do tools work with human handoff?

Yes. Tools can collect context, create a record, or route the conversation to a person. That is often the right path when the question is high-value, sensitive, or outside approved answer coverage. The operational question is whether tools makes the workflow clearer once real conversations, real ownership, and real edge cases show up. That is the bar teams should use before they expand the rollout across more assistants, more channels, or more teams.

When should I avoid enabling a tool?

Avoid enabling a tool when the destination team is not ready, the field mapping is unclear, or the visitor intent is too broad. Start with answer quality and source coverage before adding action paths. The operational question is whether tools makes the workflow clearer once real conversations, real ownership, and real edge cases show up. That is the bar teams should use before they expand the rollout across more assistants, more channels, or more teams.

Feature

Turn assistant answers into next steps

Use owned content to answer visitor questions with less friction.

Start for Free

7-day free trial

What this feature covers

Lead CaptureWeb SearchHandoff

Context

Why it matters

The practical reason to use it.

Tools keep the assistant from becoming a dead end after a useful answer.

How it works

A step-by-step look at the workflow.

1

Step 1

Pick the visitor next step the assistant should support, such as lead capture, booking, support request, product lookup, or human handoff.

2

Step 2

Limit the tool to the assistants and pages where that next step makes sense.

3

Step 3

Define the fields, consent language, triggers, and fallback path before collecting or sending information.

4

Step 4

Review tool usage, handoff quality, and visitor outcomes before enabling additional actions.

Coverage

Core job

The main job this feature handles.

Lead capture

Collect contact details and question context when a visitor shows buying, booking, or consultation intent.

Calendar booking

Move interested visitors from answer to scheduled next step without forcing a separate hunt for availability.

Approved lookup

Use controlled search or lookup when the assistant needs current product, source, or operational context.

Support handoff

Request a human, create a ticket, or mark an outcome when the question needs ownership beyond the assistant.

Coverage

Daily use

How teams use it after launch.

Lead capture

Calendar booking

Approved lookup

Source search

YouTube transcript

Zendesk tickets

HubSpot sync

Shopify products

Coverage

Control points

What to keep controlled.

Start with one bounded workflow

Use Tools on the narrowest workflow where the team can measure whether the feature reduces friction, improves clarity, and creates more qualified.

Keep edge cases visible

Review the conversations, prompts, and system actions tied to tools so operators can see where the rollout still depends on manual judgment.

Connect the surrounding systems

Tools is stronger when the feature sits beside the knowledge, integrations, and routing rules that already determine what happens after the first.

Expand after the first proof

Once the first deployment is stable, teams can extend tools into more surfaces and assistants without rebuilding the same control model from.

Outcomes

What you get

The changes teams should notice first.

More qualified leads captured from real visitor questions
Faster booking when interest is already clear
Better support handoff with transcript and context preserved
Cleaner tool governance because actions stay scoped to each assistant

Proof you can check

The facts do the selling

Plan facts, platform capabilities, and worked examples — every claim here is checkable, not a pitch.

White-label included — never a paid add-on. Copyright removal from $98/mo. Full white-label — custom domain, branded portal, your-domain emails — from $198/mo.