🛠️ How-to guide

<aside> 🧮

WHAT IT DOES

Tables are simple, spreadsheet-style lists of your own data that an agent can look things up in — service categories, permit fees, pickup zones, park hours. You keep the table here, and your agent reads the right row on demand while it's talking to a resident.

</aside>

Why it matters

When a Riverton resident asks "what day is recycling on Elm Street?" or "how much is a fence permit?", the answer lives in your data, not the agent's general knowledge. A table gives the agent an exact, up-to-date source to read from — so answers stay correct even when your fees or schedules change.

The Tables list

Each table shows its key column (the column the agent looks rows up by), how many columns and rows it holds, and a short description. You can search by name, description, key, or column.

The Tables list — each workspace table with its key column, column count, and row count.

The Tables list — each workspace table with its key column, column count, and row count.

How it works

Select New table to start a table from scratch or import a CSV or Excel file.

Select New table to start a table from scratch or import a CSV or Excel file.

  1. Select New table. Start blank, or bring your data in from a CSV or Excel file — the first row becomes your column headers.
  2. Name the table (kebab-case, e.g. service-requests) and, if you like, add a description of what each row represents.
  3. Choose one column as the key — the value the agent searches on, like request_number or permit_type. A table without a key can only be read in full.
  4. Review the columns and their types (text, number, yes/no, or date), then create the table. Open any table later to add, edit, or import more rows.
  5. Connect the table to an agent so it can read it while answering. The agent looks up rows by the key you chose.

Working with your data

Open any table to see its rows. From here you can: