Customers gets a real table, and board filters work on every property

Customers works like a board table

Switch the customer list to Table and you get the grid your boards already use. Drag a header to move a column. Pin the ones you want kept in sight, resize them, and drop a calculation in the footer. Click a row, shift-click another, and act on everything in between. Keyboard navigation works throughout, and a long list stays quick instead of stalling on the first open.

You decide which columns show. Email, Status, Created and Updated come switched on, and every custom field you have added sits one toggle away in Customize view. Save the arrangement onto a view and it opens that way next time, the way filters and sort already did. Widths stay on your own machine, so a teammate rearranging their columns never moves yours.

Two smaller fixes sit on the same screen. Created and Updated report only now, so clicking one stops opening an editor that had nothing to edit. Clicking a customer's name renames it where it sits, and the arrow next to the name opens the customer.

Typing a name finds that customer

Search the customer list for someone's full name and you land on them. Best matches come first: an exact name, then a name that starts with what you typed, then a word inside the name, then an email, then a value in one of your own fields.

Two words narrow the list now. You get back the customers carrying both of them rather than everyone carrying either, which is what used to turn a two-word search into half your customer list. Accents dropped out of the equation in both directions, so joao finds João.

Every board property can be filtered

The filter builder used to offer a short list of property types and quietly refuse everything else. That list is gone. Filter on any property you have, with operators that fit the value: text, links, emails and phone numbers take contains, is, starts with, ends with; numbers and money take equals, greater than, less or equal; dates take is before and is on or after. Covers, files and linked records take is empty and is not empty, which nearly every other type carries as well.

The value box follows the operator instead of the property. Pick one and you get an option list, a text field, a decimal field, a calendar day, or nothing at all where the operator needs no value. The board holds still until you stop typing, and a rule you have not filled in yet matches every card. A half-written filter never blanks your board.

Comparisons are forgiving. Text ignores case and stray spaces. Phone numbers ignore punctuation, so 912345678 matches +351 912 345 678. Dates compare by calendar day.

Customers are open to your automations

An API key or an AI agent can now reach everything a member can record about a customer. Three things were missing and are now there: reading one customer with its status, notes and field values, listing the statuses your organization uses, and replacing a customer's notes.

Status gets picked from that list rather than typed as a label, the same way a card moves by naming its column. Leave it out when you create someone and they land on your default status. What a read hands back is shaped exactly like what a write accepts, so an agent reads a customer, changes one field, sends it back, and nothing needs translating in between. Archiving, restoring and deleting stay in the hub.