CRM, Creator, and skills

BoText can work as a lightweight CRM. Visitors become contacts, you invent data models in Creator, and the assistant can fill those records during a chat.

Contacts

Open CRM → Contacts (or Contacts if CRM is not on the plan). Each person the widget talks to can be stored here. You can also click New to add someone by hand.

A contact card has:

• First name (required)
• Last name
• Email
• Phone
• Notes

Email or phone is required — one of the two must be filled. New contacts stay unread until you open them. From the card you can jump into that conversation and see custom records linked to the person. Delete removes the contact from the CRM; chats stay unchanged.

Creator: tables

Plans that include CRM expose CRM → Creator (“Data model creator”). Click New to add a table. Refresh CRM reloads the list after someone else on the team changed a model.

Each table has:

• Name — 3–20 characters. Shown in the dashboard. Names such as Contacts, Members, and Creator are reserved.
• Slug — generated from the name. Used internally in skills. You see it under the name field; you do not type it by hand.
• Position — sort order in the sidebar (0 and up).
• Description — up to 500 characters. Tell the assistant what this model stores and when to use it. This text is sent with the generated skills.

Table switches

• Active — on: the table is in use. Off: it is marked Inactive. Use hide inactive at the bottom of the list to tuck those tables away. Inactive tables do not stay available to the assistant.
• Bot access — on: the assistant may use this table. Off: the table is dashboard-only (badge: “No bot access”), and the three skills for that table are turned off.
• Limited to selected members — off: every member who can open CRM can open this table. On: only the people you tick in the member list. Search members by name or email. Invite people first if the list is empty. Limited tables show a Limited badge.

Save to keep changes. Cancel closes the editor without saving. Draft tables that were never saved disappear on Cancel.

Creator: columns

Select a table, then press + on the Configuration panel. Each column has a name (3–20 characters), an auto slug, a position, a type, and an optional description (up to 500 characters) that tells the assistant how to fill the field.

Types:

• Text — up to 255 characters
• Long text — up to 2,500 characters
• Integer — whole numbers
• Decimal — numbers with a fraction
• Boolean — yes / no
• Date — date only
• Date and time
• Email
• Phone

Column switches

• Required — the assistant must collect this value before it creates a record. It must come from the conversation; the bot is instructed not to invent it.
• Unique — the value must be unique across records. Get skills prefer unique fields when looking a row up.
• Active — off: the column stays in stored data but is hidden from the table UI and from skills. Use hide inactive on the column list to hide those rows.

Three skills for every table

When you save a table that has at least one column and Bot access is on, BoText creates exactly three skills for that table:

1. Get — look up an existing record by its uid (from a previous tool result) or by unique / identifying fields. The assistant never invents a uid.
2. Create — add a new record. Required fields must already be known from the chat. Optional fields can be skipped. link_contact attaches the record to a person already saved or found in this conversation.
3. Update — change an existing record. Needs a valid uid from Get or Create. Send only fields that changed; pass null for the rest. Can also link a contact.

Skills stay in sync when you rename the table, change columns, or toggle Active / Bot access. If Bot access is off, or the table has no columns yet, those three skills exist but are inactive. Display names default to “Get {table}”, “Create {table}”, and “Update {table}”.

Integration → Skills

Open Integration to review every action this bot may use. Custom-table skills appear there after you save a table (Integration must be enabled on the bot). Click a skill to see:

• Display name and Display description — what people see in the dashboard. You can edit these (name at least 3 characters, description up to 500). Saving a table later does not overwrite names you already edited.
• Function name, LLM description, and Parameters — read-only. These are what the model actually calls.
• Badges for Get / Create / Update and Active / Inactive.

If Integration is not enabled yet, the same menu shows a request form: write to Support and describe the CRM, calendar, or other tool you want connected.

Records in a custom table

Each saved table appears under CRM in the sidebar. Open it to list records. New adds a row by hand. Records can link to a contact. Unread rows stay marked until you open them. Delete hides the row from the dashboard and from skill lookups.

During a conversation the assistant asks for the fields you marked, step by step, in natural language. Visitors do not have to fill a long form on the page.