Contacts

Round 4, one hand, on the shell that shipped on 2026-08-05. The screen it replaces is a search box followed by five dropdowns in a row, and a second tab called Segments that holds the same people filtered a different way.

The direction this is drawn against — react to this before the pixels

The screen1180 wide · Contacts is one screen, so no panel — 56px of chrome

Contacts

1,284 people
Channel WhatsApp Tag Palm Jumeirah Heard from in the last 30 days
2 people picked
AM Abdulrahman Al Maktoum+971 50 123 4567 WhatsApp Palm JumeirahBuyer 2 hours ago Opted in
SR Sara Rahman+971 55 981 2245 WhatsApp Palm Jumeirah yesterday Opted in
JD Jamal Darwish@jamal.darwish Instagram Off-plan 4 days ago Bot paused
MK Mariam Khoury+971 52 447 1180 WhatsApp DowntownInvestor 6 weeks ago Opted out
TN Tomas Novakvisitor 8f21c4 Website Enquiry 18 minutes ago Not asked
HA Hind Al SuwaidiHind Al Suwaidi Facebook never Not asked
Showing 1 to 6 of 1,284

The people are invented; the shapes are not. Every column here is a field the payload already returns — displayName, channel, waId, tags, consentState, lastInboundAt and the per-contact automation pause. Nothing on this sheet needs an API change.

Two forks for you

1. Does Segments really become a saved view? It is the same trade as the Dashboard's channels: one concept, one surface. The cost is that a segment stops being a thing with its own page and becomes a named filter. If segments are ever going to carry more than a filter — a schedule, an owner, a description — they deserve their own screen and this fork should be struck.

2. "Not asked" or "Unknown" for consent nobody has recorded. The payload calls it unknown. "Not asked" is truer for a website visitor who was never put through an opt-in, but it is a claim about why the value is missing. "Unknown" claims less and reads worse.