Skip to main content
Back

Claim schema

Configure the dynamic fields your bot collects during calls: text, email, phone, date/time, and more.

WHAT IS THE CLAIM SCHEMA?

The claim schema defines the structured information your bot must collect during a phone conversation. These fields are dynamic and fully customisable to your activity.

For example, for a museum, the schema might include: the visitor's name, number of tickets, visit time slot, and ticket type. For a gallery: the client's name, desired date, and type of visit (free or guided).

AVAILABLE FIELD TYPES

Each schema field is defined by a type that determines how the bot collects and validates the information:

  • text: Free text field (name, address, description, order, etc.)
  • email: Email address with automatic format validation
  • phone_number: Phone number with format validation
  • datetime: Date and/or time (appointment, delivery slot, etc.)

CONFIGURING YOUR SCHEMA

Go to 'Bot configuration > Claim schema' to define your fields. For each field, you must specify:

A unique identifier (e.g. 'visitor_name', 'visit_date'), a display label (e.g. 'Visitor name', 'Visit date'), the field type, and whether the field is required or optional.

The bot will naturally ask the necessary questions to fill in each required field during the conversation.

EXAMPLES BY SECTOR

Museum / Gallery (MuseumPlugin): Visitor name (text), Email (email), Number of tickets (text), Visit time slot (datetime), Ticket type (text), Guided tour (text)

Theatre / Performance venue: Audience member name (text), Email (email), Phone (phone_number), Desired show (text), Number of seats (text), Desired date (datetime)

Frequently asked questions

HOW MANY FIELDS CAN I ADD TO THE SCHEMA?

There is no strict limit, but we recommend sticking to 5-10 essential fields to avoid excessively lengthening phone conversations. Each field description is limited to 200 characters.

DOES THE BOT ASK QUESTIONS IN THE ORDER OF THE SCHEMA?

The bot collects information naturally throughout the conversation, not necessarily in schema order. It adapts to the flow of the discussion and fills in fields as the client provides information.

IS THE COLLECTED DATA AUTOMATICALLY ARCHIVED?

Yes, the claim schema fields filled in during the call are automatically saved to your database at the end of the conversation. You can view them from your dashboard.