channelsdata tablescontacts
Share a demo link, limit a channel to your customers, and find a record by an encrypted field
Give a prospect a live preview of your agent, restrict a channel to the people in one of your data tables, and choose how an encrypted field can be found — or whether it can be found at all.
New
- Public demo links — from Sandbox, turn on a link you can send to a prospect. It shows your agent floating over their own website next to a short, automatically written explanation of what it does, with editing and expiry included. See public demo links.
- Allow a whole data table on a channel — an allow or deny list entry can now be a row from one of your data tables, or Everyone in this table, instead of only a contact who has messaged before. A whole-table entry is checked live, so adding a customer row lets them message without anyone touching the channel. See access control.
- Open or Restricted — every channel now states which it is, at the top of its Allow List tab. Open admits anyone except the deny list; Restricted admits only the allow list. Both lists stay editable in either mode, so you can build the allow list before switching. See access control.
- Finding this field later — when you create an encrypted field, choose whether it can be found by its complete value, by any single word of it, or not at all. Names match by word by default, so searching "Sufiyan" finds "Mohammad Sufiyan Rahmat". See personal data and encryption.
- Search reaches encrypted fields — the records search box now finds a value stored in an encrypted column instead of skipping it. See finding an encrypted field later.
Fixed
- Searching an encrypted email or phone number missed the record unless the capitalisation and spacing matched what was stored.
- An agent could find records by searching a field its permissions hide. Search now covers only the fields an agent is allowed to read.
- Duplicating a table that had encrypted fields produced a copy whose values could not be read or searched.
- An allow or deny list was not applied on a WhatsApp channel connected through Meta's guided setup, so anyone could message it. If you had a list configured on one of those channels, check it is doing what you expect — it now applies from the next message.
- Picking a contact when sending a WhatsApp template always reported that they had no WhatsApp number on file, leaving the manual number box as the only way through.
- A reply could hang indefinitely if the model provider never answered when the agent started generating it. It now gives up and reports an error.
Changed
- A channel's access mode is now something you set, rather than something inferred from whether the allow list happened to be empty. Existing channels keep the behaviour they had: one with entries on its allow list is now marked Restricted, one without is Open. Nothing to do, but the mode is worth a look next time you open a channel. See access control.