FAQ

Answer the team concerns before launch.

Xrisp is designed around operator control: who can reply, when to take over, and how boundaries stay visible.

  • Does not replace Crisp
  • Handoff is per conversation
  • Boundaries stay visible
01

Does Xrisp replace Crisp?

No. Xrisp works beside Crisp and sends AI or operator replies back to the original customer conversation.

02

Can one conversation be paused?

Yes. Handoff is saved per conversation, so one risky thread can move to a human without stopping other automation.

03

Does the team need a complete knowledge base first?

No. Start with a small set of frequent questions, then expand with answers the team has approved.

04

Will customers see internal state?

No. Customers see clean replies. The team sees handoff, limits, and delivery state internally.

Principle

Customers see answers. Teams see boundaries.

Those two surfaces stay separate. Xrisp does not expose internal operating state to customers.

Ready?

Try one real scenario first.

Validate reply boundaries with one set of common questions, then decide whether to expand automation coverage.